The question is, does this look like possible faulty ram or something
worse? (I made it a blows 95 machine, since it was gonna crash hard
anyways. ;-)
Dec 15 02:58:59 news kernel: Oops: 0002
Dec 15 02:58:59 news kernel: CPU: 0
Dec 15 02:58:59 news kernel: EIP: 0010:[<00110f2a>]
Dec 15 02:58:59 news kernel: EFLAGS: 00010002
Dec 15 02:58:59 news kernel: eax: 20202020 ebx: 00000202 ecx: 00080f98 edx
: 20202020
Dec 15 02:58:59 news kernel: esi: 001ecc1c edi: 001ecc1c ebp: 00080f78 esp
: 00080f74
Dec 15 02:58:59 news kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 001
8
Dec 15 02:58:59 news kernel: Corrupted stack page
Dec 15 02:58:59 news kernel: Process init (pid: 1, process nr: 1, stackpage=0008
0000)
Dec 15 02:58:59 news kernel: Stack: 00081018 00080fac 00110ab9 00080f98 7270642d
2d20200a 2d202c62 6361622d
Dec 15 02:58:59 news kernel: 2070756b 20202020 20202020 20202020 20202020
656b616d 63616220 2070756b
Dec 15 02:58:59 news kernel: 6f666562 72206572 766f6d65 200a6c61 2c642d20
6e2d2d20 65642d6f 65666572
Dec 15 02:58:59 news kernel: Call Trace: [<00110ab9>]
Dec 15 02:58:59 news kernel: Code: 89 42 04 89 10 c7 41 04 00 00 00 00 c7 01 00
00 00 00 b8 01
The corrupted stack page is why I think it was a memory error. BTW Sorry
this isn't decoded... I didn't have the newer klogd on that machine.
EIP is
00110f10 T del_timer
and Call Trace is
00110830 T schedule
--Dan