I am still having occasional kernel panics and don't know why. Today an Oops happened some hours before the panic (when I did 'make zImage'). The Oops left the kswaps daemon as zombie and I had to reboot the system. Following is the output of the Oops. I would really appreciate if somebody could give me any hint what could be wrong with my Debian system. I can't analyze the data with ksymoops because I couldn't compile ksymoops and I probably would experience another crash if I would try it.
############################################################################## Jan 28 16:28:43 quod kernel: Unable to handle kernel paging request at virtual address 858994b4 Jan 28 16:28:43 quod kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Jan 28 16:28:43 quod kernel: *pde = 00000000 Jan 28 16:28:43 quod kernel: Oops: 0000 Jan 28 16:28:43 quod kernel: CPU: 0 Jan 28 16:28:43 quod kernel: EIP: 0010:[<c0124962>] Jan 28 16:28:43 quod kernel: EFLAGS: 00010287 Jan 28 16:28:43 quod kernel: eax: 858994a0 ebx: c02dc6b0 ecx: 00000006 edx: 0000ffe0 Jan 28 16:28:43 quod kernel: esi: 858994a0 edi: c5899500 ebp: c02dc6b0 esp: c000dfa8 Jan 28 16:28:43 quod kernel: ds: 0018 es: 0018 ss: 0018 Jan 28 16:28:43 quod kernel: Process kswapd (pid: 4, process nr: 4, stackpage=c000d000) Jan 28 16:28:43 quod kernel: Stack: 00000030 c000c000 c0119fd2 c02dc6b0 0000000d 00000006 c011ed13 00000006 Jan 28 16:28:43 quod kernel: 00000030 00000000 c01a9078 c000c1c1 c011edbf 00000030 00000f00 c0003fb4 Jan 28 16:28:43 quod kernel: c0106000 00009000 c0106513 00000000 00000f00 c01d5fd8 Jan 28 16:28:43 quod kernel: Call Trace: [<c0119fd2>] [<c011ed13>] [<c01a9078>] [<c011edbf>] [<c0106000>] [<c0106513>] Jan 28 16:28:43 quod kernel: Code: 8b 76 14 83 78 20 00 75 06 f6 40 18 46 74 13 6a 00 e8 4c 01 ############################################################################## I am running a kernel 2.2.10 with Hamm and the newer stuff needed for this kernel. I am guessing my problem is hardware dependend and I am going to exchange my quodry modules if I can't find any other cause for this troubles. I am having this kernel panics since my hosting provider had a power interruption. What kind of PC HW could get damaged by a power interruption resulting in such a behaviour I described? TIA, Werner
