A recently ran into a GPF under Linux 2.0.30. This happened while I was
compiling a kernel and running "mke2fs -c" on my new SyQuest SyJet. I have
tried to reproduce the crash for a few hours to no effect. The system
has been in use for well over a year (except for the SyJet) and I believe
it to be solid hardware (RAM passes memcheck86 OK).
After the GPF Linux kept on running OK (I rebooted anyways). The "wait
queue is bad" message may also give a clue (or may not).
I have had problems with 2.0.27 with 2940 stack corrution, but this seems
different (but perhaps not).
Micron P-133 (Micronics M54Hi-P motherboard)
64MB RAM, Diamond Stealth 64 VRAM, SB Vibra16
Triton IDE drives with Quantum LT720 and WD 1.6GB (root and home on
/dev/hdb)
Adaptec 2940 SCSI controller (SyJet, Toshiba 3501 4xCDROM)
kernel: general protection: 0000
kernel: CPU: 0
kernel: EIP: 0010:[do_sd_request+123/376]
kernel: EFLAGS: 00010002
kernel: eax: 00000037 ebx: 4c05ff02 ecx: 001736d0 edx: 00002518
kernel: esi: 03dffc98 edi: 00000046 ebp: 00000000 esp: 021e3d00
kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
kernel: Process badblocks (pid: 2840, process nr: 48, stackpage=021e3000)
kernel: Stack: 00000206 03dffc98 021e3d30 00000000 001736f5 00000000 00123c6c
0020d49c 00000030 021e3ec4 021e3ec4 00000000 02848018 03dffcc8
00128086 03dffc98 03ff4900 00000000 00004000 03238ccc 00000400
00000000 00001400 00000000
kernel: Call Trace: [unplug_device+37/44] [__wait_on_buffer+96/184]
[block_read+958/1468] [handle_bottom_half+11/24]
[sys_read+138/176] [system_call+85/124]
kernel: Code: f6 43 4b 40 74 2f f6 43 4a 02 74 25 83 3d 84 d1 1d 00 00 75
kernel: wait_queue is bad (eip = 0012565f)
kernel: q = 03dffccc
kernel: *q = 021e3d30
I will gladly supply any additional information.
Take it easy,
Ken Jordan