I myself suspect bad memory (which I took out for now to be sure) but
could someone (Linus?) look at the oops and see if it looks like a
hardware glitch (bit-flip or so) or could it be a real problem with the
kernel?
I wrote the oops down by hand. I can't give you disassembly lists as
vmlinux was lost with everything else in /usr.
CPU: 0
EIP: 0010:[<00125e24>]
EFLAGS: 000100006
eax: 00000000 ebx: 0292f518 ecx: 0292f518 edx: 6420646e
esi: 002bec58 edi: 0000002c ebp: 002bec00 esp: 001d07c4
ds: 0018 es: 0018 fs: 002b gs: 0018 ss: 0018
Process swapper (pid: 0, process nr. 0, stackpage = 001ce96c)
Stack: 001a4901 0292f518 00000001 000002c4 002bec00 00000078 00000000 001a4ddd
002bec00 00000001 00000078 00000000 002bec00 000007cf 00000000 002bec00
0000003c 002b6000 00000001 00000078 00000078 00000000 0019bce8 002bec00
Call Trace: [<001a4901>] [<001a4ddd>] [<0019bce8>] [<0019fd1d>] [<0019fd42>] [<0
019fda7>] [<001a0c71>]
[<001a368a>] [<0010caee>] [<0010c1e1>] [<001096b4>] [<0010a725>] [<001093
a8>] [<00109235>]
Code: f6 42 14 01 74 31 8b 52 10 85 d2 74 04 39 ca 75 ef 8b 41 24
Aiee, killing interrupt handler
kfree of non-kmalloced memory: 001d09b4, next=00000000, order=0
kfree of non-kmalloced memory: 001d09a4, next=00000000, order=0
kfree of non-kmalloced memory: 001d0eb8, next=00000000, order=0
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep
idle task may not sleep
Using `temp/boot/System.map-2.0.34-pre2' to map addresses to symbols.
>>EIP: 125e24 <mark_buffer_uptodate+14/4c>
Trace: 1a4901 <end_scsi_request+81/144>
Trace: 1a4ddd <rw_intr+245/514>
Trace: 19bce8 <scsi_done+678/684>
Trace: 19fd1d <ncr_complete+58d/5c0>
Trace: 19fd42 <ncr_complete+5b2/5c0>
Code: 125e24 <mark_buffer_uptodate+14/4c>
-- Samuli Kaski, samkaski@cs.helsinki.fi Department of Computer Science, University of Helsinki, Finland.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu