I've got a dual Athlon 1900 MP system and previously it was running FC1 with no problems at all. Last week I wiped it totally and installed FC2. At the weekend it kernel paniced. I rebooted it on monday and it died again that evening. I was able to get the log entries for the first crash but there's nothing for the second. Could someone have a look and give me a clue as to what might be happening? News has been filtering through of the long awaited results of the extended reach trials currently being carried out by BT. Aug 7 14:28:16 onizuka kernel: Unable to handle kernel NULL pointer dereference at virtual address 0000000a Aug 7 14:28:16 onizuka kernel: printing eip: Aug 7 14:28:16 onizuka kernel: fffeb1a8 Aug 7 14:28:16 onizuka kernel: *pde = 00003001 Aug 7 14:28:16 onizuka kernel: Oops: 0000 [#1] Aug 7 14:28:16 onizuka kernel: SMP Aug 7 14:28:16 onizuka kernel: Modules linked in: loop ipv6 parport_pc lp parport autofs4 sunrpc e100 mii ipt_LOG ipt_state iptable_nat ip_conntrack iptable_filter ip_tables floppy sg scsi_mod dm_mod ohci_hcd button battery asus_acpi ac ext3 jbd Aug 7 14:28:16 onizuka kernel: CPU: 0 Aug 7 14:28:16 onizuka kernel: EIP: 0060:[<fffeb1a8>] Not tainted Aug 7 14:28:16 onizuka kernel: EFLAGS: 00010202 (2.6.6-1.435.2.3smp) Aug 7 14:28:16 onizuka kernel: EIP is at 0xfffeb1a8 Aug 7 14:28:16 onizuka kernel: eax: 000000c5 ebx: 0000000a ecx: fef6f414 edx: 00615ffc Aug 7 14:28:16 onizuka kernel: esi: fef6f414 edi: 00000003 ebp: fef6f480 esp: 41fa1fe0 Aug 7 14:28:16 onizuka kernel: ds: 007b es: 007b ss: 0068 Aug 7 14:28:16 onizuka kernel: Process init (pid: 1, threadinfo=41fa1000 task=39fff6b0) Aug 7 14:28:16 onizuka kernel: Stack: 0000007b 0000007b 000000c5 00cb0402 00000073 00000202 fef6f404 0000007b Aug 7 14:28:16 onizuka kernel: Call Trace: Aug 7 14:28:16 onizuka kernel: Aug 7 14:28:16 onizuka kernel: Code: 50 55 57 56 52 51 53 ba 7b 00 00 00 8e da 8e c2 81 fc 00 00 Aug 7 14:28:16 onizuka kernel: <0>Kernel panic: Attempted to kill init!
