Moin,

,----[ aus /var/log/messages ] | May 11 06:00:10 fw-berlin modify_resolvconf: Service ipppd modified /etc/resolv.conf. See info block in this file | May 11 06:00:10 fw-berlin kernel: invalid operand: 0000 | May 11 06:00:11 fw-berlin kernel: CPU: 0 | May 11 06:00:11 fw-berlin kernel: EIP: 0010:[write_inode_now+93/444] Not tainted | May 11 06:00:11 fw-berlin kernel: EFLAGS: 00010283 | May 11 06:00:11 fw-berlin kernel: eax: c048e8d8 ebx: c048e8c0 ecx: c04be040 edx: c02ad0c8 | May 11 06:00:11 fw-berlin kernel: esi: c048e8d8 edi: c00272e0 ebp: c04bed60 esp: c078bf44 | May 11 06:00:11 fw-berlin kernel: ds: 0018 es: 0018 ss: 0018 | May 11 06:00:11 fw-berlin kernel: Process modify_resolvco (pid: 6024, stackpage=c078b000) | May 11 06:00:11 fw-berlin kernel: Stack: c03e58a0 c003e9c0 c012cbd7 c04bed60 c03e58a0 00000000 c0853880 00000001 | May 11 06:00:11 fw-berlin kernel: c012bc2c c03e58a0 c0853880 00000000 c03e58a0 00000000 0000007f 00000000 | May 11 06:00:11 fw-berlin kernel: c0114a18 c03e58a0 c0853880 c027dd00 c078a000 00000000 bffffc5c c08539a0 | May 11 06:00:11 fw-berlin kernel: Call Trace: [__block_prepare_write+679/680] [invalidate_bdev+20/280] [ksoftirqd+128/164] [test_perm+67/80] [do_sysctl_strate | May 11 06:00:11 fw-berlin kernel: [tracesys+11/35] | May 11 06:00:11 fw-berlin kernel: | May 11 06:00:11 fw-berlin kernel: Code: 0f 0b 8b 43 4c 85 c0 74 11 8b 40 0c 85 c0 74 0a 53 ff d0 83 `----

In welcher Richtung sollte ich den Fehler suchen?

Hardwareschaden, an was? - CPU - RAM - Pladde

Andreas