panic with 2.0.28

Simon Karpen (slk@linux1.acm.rpi.edu)
Fri, 28 Feb 1997 15:40:10 -0500 (EST)


just saw a panic on a machine running 2.0.28

hardware:
430HX (triton II) motherboard
Pentium 166
128MB EDO RAM
AHA2940 w/ 2 quantum 2.1G drives
21041 (tulip) based ethernet card
Trident PCI video

the panic itself is:

general protection: 0000
CPU: 0
EIP: 0010:[<0012d4c4>]
EFLAGS: 00010286
eax: f00058a0 ebx: 00e54018 ecx: 00000000 edx: 007d7164
esi: 00000000 edi: f00058a0 ebp: 01709018 esp: 02e56e88
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process httpd (pid: 15882, process nr: 64, stackpage=02e56000)
Stack: 00000001 001213d7 00e54018 00000000 00000001 00000036 00000002 001159a2
00000000 0000002b 00000014 02e57000 02e56f08 0010aba3 0000000b 001bc426
00000000 00000001 000081a4 02e56f8c 000000ff 09000000 08800000 00c50018
Call Trace: [<001213d7>] [<001159a2>] [<0010aba3>] [<09000000>] [<08800000>] [<0010afb8>] [<0010af90>]
[<0010a780>] [<0012aef7>] [<00121189>] [<0012130f>] [<0010a5f5>]
Code: 8b 50 4c 85 d2 74 22 f6 42 1c 01 74 0f 53 83 c0 4c 50 e8 15

and the output from ksymoops translates it to:

Using `/boot/System.map' to map addresses to symbols.

>>EIP: 12d4c4 <dcache_lookup+d0/164>
Trace: 1213d7 <clear_inode+ab/104>
Trace: 1159a2 <sys_getitimer+32/64>
Trace: 10aba3 <die_if_kernel+1d7/2ac>
Trace: 9000000
Trace: 8800000
Trace: 10afb8 <do_general_protection+4/54>
Trace: 10af90 <do_alignment_check+34/44>
Trace: 10a780 <ret_from_sys_call+70/90>
Trace: 12aef7 <do_rename+1d3/234>
Trace: 121189 <sys_readv+19/54>
Trace: 12130f <inode_init+3/20>
Trace: 10a5f5 <do_signal+269/274>

Code: 12d4c4 <dcache_lookup+d0/164> movl 0x4c(%eax),%edx
Code: 12d4c7 <dcache_lookup+d3/164> testl %edx,%edx
Code: 12d4c9 <dcache_lookup+d5/164> je 12d4ed <dcache_lookup+f9/164>
Code: 12d4cb <dcache_lookup+d7/164> testb $0x1,0x1c(%edx)
Code: 12d4cf <dcache_lookup+db/164> je 12d4e0 <dcache_lookup+ec/164>
Code: 12d4d1 <dcache_lookup+dd/164> pushl %ebx
Code: 12d4d2 <dcache_lookup+de/164> addl $0x4c,%eax
Code: 12d4d5 <dcache_lookup+e1/164> pushl %eax
Code: 12d4d6 <dcache_lookup+e2/164> call 9090002c <_EIP+9090002c>
Code: 12d4db <dcache_lookup+e7/164> nop

The machine had previously been having some problems that
appeared to be related to the adaptec SCSI card, but no panics.
Does this look like an adaptec problem, or bad RAM?

Simon Karpen
karpes@rpi.edu, slk@acm.rpi.edu, slk@karpes.stu.rpi.edu
"Down, not Across"