[lkml]   [2001]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectscsi_io_completion oops on 2.4.10-pre5
The below oops is easily reproducable for me under 2.4.10-pre5. About 60 
seconds of heavy disk activity brings it about reliably. I've run almost
every -ac kernel up to and including 2.4.9-ac4 with no problem. This is the
first Linus kernel in 2.4 I've tried. After the oops,
the machine is totally dead, no NUMLOCK response, no pings, etc. Reset button
is the only way out. No modules were loaded when the below oops was recorded.

Interesting bits of my config:

Let me know if I can provide any other info. I can try earlier Linus kernels
if necessary but would appreciate guidance as to where to start since I've
not run any of them.


ksymoops 2.4.2 on i686 2.4.10-pre5. Options used
-v /usr/src/linux-2.4.10-pre5/vmlinux (specified)
-k /proc/ksyms (default)
-L (specified)
-O (specified)
-m /boot/ (specified)

Unable to handle kernel paging request at virtual address 46454c22
*pde = 00000000
Oops: 0000
CPU: 1
EIP: 0010:[<c020c444>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010202
eax: 47494c41 ebx: c9ff5a00 ecx: 11d25310 edx: c0344008
esi: 46454c22 edi: 560a2254 ebp: c0344000 esp: c664fef4
ds: 0018 es: 0018 ss: 0018
Process dnetc (pid: 1210, stackpage=c664f000)
Stack: 00000001 c9ff5a00 00000010 c9ff5a00 c0344004 c0344008 00000000
00000010 00000000 c0229922 c9ff5a00 00000010 00000001 c1359800
00000020 c0206b69 c9ff5a00 c9ff5a00 00000000 00000020 c037f4a0
Call Trace: [<c0229922>] [<c0206b69>] [<c0206a26>] [<c0119e70>] [<c0119d4a>]
[<c0119ad3>] [<c0108785>] [<c0106e2c>]
Code: f3 a5 a8 02 74 02 66 a5 a8 01 74 01 a4 8b 54 24 14 8b 02 50

>>EIP; c020c444 <scsi_io_completion+88/370> <=====
Trace; c0229922 <rw_intr+152/15c>
Trace; c0206b68 <scsi_finish_command+a4/b0>
Trace; c0206a26 <scsi_bottom_half_handler+ce/e4>
Trace; c0119e70 <bh_action+4c/8c>
Trace; c0119d4a <tasklet_hi_action+6e/9c>
Trace; c0119ad2 <do_softirq+82/e0>
Trace; c0108784 <do_IRQ+d4/e4>
Trace; c0106e2c <ret_from_intr+0/6>
Code; c020c444 <scsi_io_completion+88/370>
00000000 <_EIP>:
Code; c020c444 <scsi_io_completion+88/370> <=====
0: f3 a5 repz movsl %ds:(%esi),%es:(%edi) <=====
Code; c020c446 <scsi_io_completion+8a/370>
2: a8 02 test $0x2,%al
Code; c020c448 <scsi_io_completion+8c/370>
4: 74 02 je 8 <_EIP+0x8> c020c44c
Code; c020c44a <scsi_io_completion+8e/370>
6: 66 a5 movsw %ds:(%esi),%es:(%edi)
Code; c020c44c <scsi_io_completion+90/370>
8: a8 01 test $0x1,%al
Code; c020c44e <scsi_io_completion+92/370>
a: 74 01 je d <_EIP+0xd> c020c450
Code; c020c450 <scsi_io_completion+94/370>
c: a4 movsb %ds:(%esi),%es:(%edi)
Code; c020c450 <scsi_io_completion+94/370>
d: 8b 54 24 14 mov 0x14(%esp,1),%edx
Code; c020c454 <scsi_io_completion+98/370>
11: 8b 02 mov (%edx),%eax
Code; c020c456 <scsi_io_completion+9a/370>
13: 50 push %eax

Kernel panic: Aiee, killing interrupt handler!
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.027 / U:0.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site