general protection: 0000
CPU: 0
EIP: 0010:[<00126794>]
EFLAGS: 00010246
eax: 7d100044 ebx: 00000000 ecx: 0000dc72 edx: 0000147b
esi: 00000002 edi: 00000800 ebp: 00000800 esp: 013f9cf0
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process dd (pid: 255, process nr: 24, stackpage=013f9000)
Stack: 00000030 00000800 00000400 00000000 00000800 00128df0 00000800 013f9f74
00000400 0172a9f0 00100000 01742c30 0800b002 00000400 00000000 000f0400
00000000 00000400 00000000 00000800 013f9f74 00010000 00000800 013f9e74
Call Trace: [<00128df0>] [<00121da8>] [<00121c8c>] [<0010a4b9>]
Code: 39 08 75 38 66 39 78 04 75 32 8b 54 24 20 39 50 1c 74 49 8b
>>EIP: 126794 <generate_cluster+54/160>
Trace: 128df0 <block_read+3c0/680>
Trace: 121da8 <sys_write+f8/110>
Trace: 121c8c <sys_read+8c/b0>
Trace: 10a4b9 <system_call+59/a0>
I'm running 1.3.64 with the BSD NCR driver version 1.4. I set commands/LUN
to 4.
I get the feeling that this is resulting from some rather freaky stack
corruption, but I'm not too sure. I think this all ties into the "kernel
stack torture" thread. Does anyone have any brilliant ideas on how to
track this down?
Jason Duerstock
jduersto@kendall.mdcc.edu