Yo All!
Help! See below for my kernel oops. I have not been able to use any
kernel after 2.4.0-test5 due to this problem. It happens shortly
after booting the kernel and is very repeatable.
This is a dual PII system with PIIX4 ide, 53c875 scsi and Raid 1.
It is not a production system so I am open to any patches or
tests.
The system would not even stay up long enough to run ksymoops so
I had to copy the data and run it under 2.2.17.
Any ideas out there?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 20340 Empire Ave, Suite E-3, Bend, OR 97701
gem@rellim.com Tel:+1(541)382-8588 Fax: +1(541)382-8676
ksymoops 2.3.4 on i686 2.2.17pre10-RAID. Options used
-V (default)
-k ./ksyms (specified)
-l ./modules (specified)
-o /lib/modules/2.4.0-test10 (specified)
-m /usr/src/linux/System.map (default)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is ./modules a valid lsmod file?
NMI Watchdog detected LOCKUP on CPU0, registers:
CPU: 0
EIP: 0010:[<c0272362>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00000082
eax: c01cb154 ebx: c122bdc0 ecx: 00000000 edx: 00000000
esi: c12b9d60 edi: 00000282 ebp: 0000000e esp: c37fbe44
ds: 0018 es: 0018 ss: 0018
Process cc1 (pid: 1484, stackpage=c37fb000)
Stack: c122bdc0 04000001 00000000 0000000e c01df362 c010cab1 0000000e c12b9d60
c37fbea8 c036e6c0 c034b9c0 0000000e c37fbea0 c010cc98 0000000e c37fbea8
c122bdc0 c1384800 00000000 c1384c78 00000000 00000000 c122bdc0 c2722500
Call Trace: [<c01df362>] [<c010cab1>] [<c010cc98>] [<c010b370>] [<c02215d3>] [<c022167a>] [<c01927c9>]
[<c01c99a8>] [<c01cdadb>] [<c01cb27e>] [<c01cda30>] [<c010cab1>] [<c010cc98>] [<c010b370>]
Code: f3 90 7e f5 e9 f7 8d f5 ff 80 3d 64 39 2f c0 00 f3 90 7e f5
>>EIP; c0272362 <stext_lock+4ba2/a820> <=====
Trace; c01df362 <scsi_dispatch_cmd+1c6/26c>
Trace; c010cab1 <handle_IRQ_event+59/84>
Trace; c010cc98 <do_IRQ+a8/fc>
Trace; c010b370 <ret_from_intr+0/20>
Trace; c02215d3 <raid1_end_bh_io+13b/148>
Trace; c022167a <raid1_end_request+9a/a4>
Trace; c01927c9 <end_that_request_first+65/c4>
Trace; c01c99a8 <ide_end_request+34/88>
Trace; c01cdadb <write_intr+ab/128>
Trace; c01cb27e <ide_intr+12a/194>
Trace; c01cda30 <write_intr+0/128>
Trace; c010cab1 <handle_IRQ_event+59/84>
Trace; c010cc98 <do_IRQ+a8/fc>
Trace; c010b370 <ret_from_intr+0/20>
Code; c0272362 <stext_lock+4ba2/a820>
00000000 <_EIP>:
Code; c0272362 <stext_lock+4ba2/a820> <=====
0: f3 90 repz nop <=====
Code; c0272364 <stext_lock+4ba4/a820>
2: 7e f5 jle fffffff9 <_EIP+0xfffffff9> c027235b <stext_lock+4b9b/a820>
Code; c0272366 <stext_lock+4ba6/a820>
4: e9 f7 8d f5 ff jmp fff58e00 <_EIP+0xfff58e00> c01cb162 <ide_intr+e/194>
Code; c027236b <stext_lock+4bab/a820>
9: 80 3d 64 39 2f c0 00 cmpb $0x0,0xc02f3964
Code; c0272372 <stext_lock+4bb2/a820>
10: f3 90 repz nop
Code; c0272374 <stext_lock+4bb4/a820>
12: 7e f5 jle 9 <_EIP+0x9> c027236b <stext_lock+4bab/a820>
1 warning issued. Results may not be reliable.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Mon Oct 23 2000 - 21:00:12 EST