Last night, I did something else than watching my computer for 5 secs,
and guess what - kernel crash.
Well, It's the first nonprovoked kernel crash for me in years, so its
not that bad after all!! ;)
Heres what I got: (bear in mind that this is a hand translated error mesg,
as the system crashed rather seriously). If you want me to do anything to
make things clearer (debug some things) in my system, then please let me
know!
Well, It could be a hardware bug, but it could just as well be some
obscure bug deep inside the kernel, who knows (I don't, cause, I'm not a
kernel hacker - haven't got the time for it)
BTW. The kernel in question is a rather "old" development kernel, namely
2.1.88
Unable to handle kernel NULL pointer dereference at virtual adress 0000049c
current->tss.cr3 = 026e4000, %cr3 = 026e4000
*pde = 00000000
Oops: 0000
Cpu = 0
Eip 0010:[<c0113a8f>]
EFLAGS 00010207
eax 0000003c ebx c26a4000 ecx 00000000 edx c26a4000
esi x26a4000 edi 00000000 ebp c26a5f04 esp c26a5ed4
ds 0018 es 0018 ss 0018
process icewm (pid 94, process nr 20, stackpage c26a5000)
stack
c2540000 00000000 00000004 00000000 0000003c 0046e941 00000001 00000003
c014e8c9 c2c9d380 c26a5f2c c0133048 00000000 c01330d1 c2540280 00000004
c2540290 c2540000 c014e8a8 c26a4000 c000cd94 00000000 00000001 c2576000
Call trace:
c014e8c9 c0133048 c01330d1 c014e8a8 c0133465 c014e73e c010faea c0109f6a
c010002b
Code 83 b9 c 04 00 00 00 75 3c 83 b9 f4 00 00 00 00 74 0f 8b 81
Yours Thomas
Thomas S. Iversen
zensonic@diku.dk
Dept. of computer science - copenhagen, denmark.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu