2.4.20pre5aa1 oops - megaraid?

From: Ville Herva (vherva@niksula.hut.fi)
Date: Sat Sep 14 2002 - 05:20:44 EST


A 600PIII UP server (Compaq 1850R) got killed twice with a similar oops
after I upgraded to 2.4.20pre5aa1. It ran very stablely on 2.4.13ac2 for
about a year.

I had compaq health modules loaded once after the boot, but they had been
unloaded before the oops. Hence the "tainted" tag.

Andrea Arcangeli also suspected the ipchains compability module, but I have
found it stable on 2.4.13ac2 and 2.4.18ac3. To me this looks more like a
megaraid thing.

Below is the oops. There was at least one oops before it, but the visible
part of that oops was identical to this one. I really hope this tells
something.

(Written down by hand, so please excuse typos...)

-- v --

v@iki.fi

Unable to handle kernel paging request at virtual address fffffff8
printing eip: c0115be2

kjournald pid 300, stackpage c2125000

stack c21254ec 00000000 00000056 cffe5fc8 00000001 c02973e8 c2125524
c0116342 cffe4000 00000000 00000086 00000003 c02973e8 00000001 c029ccc4
0000005d 00000000 c0124961 00000002 00000001 c01a447a c029ccc4 c01af06e
5d00000e

EIP: 0010:[<c0115be2>]
eflags 0010007
eax 00000073

ksymoops 2.4.6 on i686 2.4.20-pre5aa1. Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.20-pre5aa1/ (default)
     -m /usr/src/linux/System.map (default)

Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.

Adhoc c0116342 <__wake_up+42/80>
Adhoc c0124961 <schedule_task+51/60>
Adhoc c01a447a <schedule_console_callback+a/10>
Adhoc c01af06e <handle_scancode+28e/2a0>
Adhoc c01b0027 <handle_kbd_event+137/190>
Adhoc c01a9274 <poke_blanked_console+64/70>
Adhoc c01b008f <keyboard_interrupt+f/20>
Adhoc c0109e8e <handle_IRQ_event+3e/70>
Adhoc c010a008 <do_IRQ+68/b0>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0110018 <pcibios_setup+58/240>
Adhoc c01b078a <panic_blink+a/80>
Adhoc c0118ba5 <panic+f5/110>
Adhoc c011bcad <do_exit+2d/230>
Adhoc c0240018 <packet_ioctl+298/370>
Adhoc c0240018 <packet_ioctl+298/370>
Adhoc c0109065 <die+65/70>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0115267 <do_page_fault+3e7/560>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0108b04 <error_code+34/3c>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0116342 <__wake_up+42/80>
Adhoc c0139f20 <end_buffer_io_sync+20/30>
Adhoc c01d3945 <__scsi_end_request+85/140>
Adhoc c01d37c7 <scsi_queue_next_request+7/100>
Adhoc c01e2c01 <megadev_ioctl+8d1/940>
Adhoc c01d2fd7 <scsi_old_done+627/640>
Adhoc c01ded5b <callDone+b/10>
Adhoc c01def3a <mega_rundoneq+2a/50>
Adhoc c01dfca9 <megaraid_isr+2a9/2d0>
Adhoc c020a6be <dev_queue_xmit+fe/260>
Adhoc c021a760 <ip_finish_output2+0/d0>
Adhoc c021a7e3 <ip_finish_output2+83/d0>
Adhoc c02104fb <nf_hook_slow+ab/140>
Adhoc c0210532 <nf_hook_slow+e2/140>
Adhoc c0109e8e <handle_IRQ_event+3e/70>
Adhoc c010a008 <do_IRQ+68/b0>
Adhoc c01d0018 <print_opcode+28/60>
Adhoc c01aa0ea <serial_in+2a/30>
Adhoc c01aeb43 <serial_console_write+23/1e0>
Adhoc c0118ff6 <__call_console_drivers+46/60>
Adhoc c011916b <call_console_drivers+eb/100>
Adhoc c011937a <release_console_sem+3a/90>
Adhoc c01192f0 <printk+100/110>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c01151da <do_page_fault+35a/560>
Adhoc c01d2fd7 <scsi_old_done+627/640>
Adhoc c01ded5b <callDone+b/10>
Adhoc c01dfcb4 <megaraid_isr+2b4/2d0>
Adhoc c0207646 <__kfree_skb+106/110>
Adhoc c022693a <tcp_rcv_synsent_state_process+33a/510>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0108b04 <error_code+34/3c>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0120680 <process_timeout+0/10>
Adhoc c0115c1b <wake_up_process+b/10>
Adhoc c0120437 <timer_bh+257/370>
Adhoc c011d24b <bh_action+1b/50>
Adhoc c011d154 <tasklet_hi_action+44/70>
Adhoc c011cf7b <do_softirq+4b/90>
Adhoc c010a03c <do_IRQ+9c/b0>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c01153c9 <do_page_fault+549/560>
Adhoc c01a44e9 <scrup+69/120>
Adhoc c01fc412 <vgacon_cursor+192/1a0>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0108b04 <error_code+34/3c>
Adhoc c0115be2 <try_to_wake_up+122/150>
Adhoc c0116342 <__wake_up+42/80>
Adhoc c01192f0 <printk+100/110>
Adhoc c0114e6d <bust_spinlocks+3d/50>
Adhoc c0109059 <die+59/70>
Adhoc c01161f4 <do_schedule+144/210>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0115267 <do_page_fault+3e7/560>
Adhoc c01b1534 <account_io_start+44/50>
Adhoc c01b15d9 <req_new_io+49/60>
Adhoc c01dfcfa <mega_busyWaitMbox+2a/40>
Adhoc c01dfe1f <megaIssueCmd+10f/290>
Adhoc c01def83 <mega_runpendq+23/40>
Adhoc c01e14c8 <megaraid_queue+138/250>
Adhoc c01cd67e <scsi_dispatch_cmd+13e/1a0>
Adhoc c0114e80 <do_page_fault+0/560>
Adhoc c0108b04 <error_code+34/3c>
Adhoc c01161f4 <do_schedule+144/210>
Adhoc c0139ed8 <__wait_on_buffer+78/a0>
Adhoc c0166349 <journal_commit_transaction+3e9/f54>
Adhoc c011629e <do_schedule+1ee/210>
Adhoc c0168a46 <kjournald+116/1c0>
Adhoc c0168910 <commit_timeout+0/10>
Adhoc c0107106 <kernel_thread+26/30>
Adhoc c0168930 <kjournald+0/1c0>

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
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Sep 15 2002 - 22:00:36 EST