Solid kernel panic on Dell OptiPlex GMT5100 (100 MHz Pentium w/ 64MB RAM; 2 2.1 GB IDE disks; NEC SCSI CD-ROM on Adaptec controller; D-Link DFE- 530TX NIC) on which RedHat 5.2, Mandrake 6.0 and RedHat 6.1 ran great. This is a fresh 7.0 install with all applicable updates (as of 11/17/00) installed. When system is in use, all appears to be fine; when it sits idle, however, it crashes after varying amounts of time. Crash data from console is: Unable to handle kernel paging request at virtual address 40039c12 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = 00000000 Oops: 0002 CPU: 0 EIP: 0010:[<c0112146>] EFLAGS: 00010006 eax: 40039c02 ebx: 40039c32 ecx: 00000047 edx: c382d74c esi: 40039c42 edi: 40039c12 ebp: c0235f4c esp: c0235f30 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, process nr: 0, stackpage=c0235000) Stack: 0003fffc 40039c12 00000001 c010adb9 00000000 00000000 00000000 c0235f60 c01188c5 00000000 c0234000 c010b10f 00000000 c010addc 00000000 c0234000 00000000 c0234000 0003fffc 00000000 00000000 00000018 00000018 ffffff00 Call Trace: [<c010adb9>] [<c01188c5>] [<c010b10f>] [<c010addc>] [c01087e1>] [<c0106000>] [<c0108804>] [<c0109f58>] [<c0106000>] [<c010607b>] [<c0106000>] [<c0100175>] Code: 89 07 85 c0 74 03 89 78 04 c7 42 04 00 00 00 00 c7 02 00 00 Aiee, killing interrupt handler Kernel panic: Attempted to kill the idle task! In swapper task - not syncing
Created attachment 5564 [details] Crash data from console
So what's the deal here. Does this bug stay NEW forever? Is this the "ignore it and maybe it'll go away" philosophy?
I am receiving a similar kernel panic with RedHat 6.2 kernel 2.2.16-3. We are running a cluster of Linux machines with MPI. At least once a weak one machine will lock up and I receive the following error: Code: 8b 4a 04 85 c9 74 26 8b 5a 18 8b 02 89 01 8b 09 85 c9 74 0c Aiee, killing interrupt handler Kernel Panic: Attempted to kill the idle task! In interrupt: handler not syncing.
Without running this oops through ksymoops _on your machine_, this information is useless to us. You can do that by doing cat <file with the panic> | ksymoops or if the system survived the oops: dmesg | ksymoops
I upgraded to RedHat 7.1 and this problem has disappeared, therefore please close this record. BTW, RH 7.1 seems VERY solid (a VERY welcome improvement over RH 7.0 which was flaky at best)