From: Daniel Drake <dsd@gentoo.org>
To: linux-scsi@vger.kernel.org
Subject: Bootup oops in scsi_run_queue with megaraid-newgen
Date: Fri, 25 Nov 2005 11:52:06 +0000 [thread overview]
Message-ID: <4386FAE6.10101@gentoo.org> (raw)
Hi,
A Gentoo user has reported he is unable to boot using the megaraid-newgen
driver, whereas the legacy driver works fine.
This is on kernel 2.6.14.2 on x86-64.
The problem is fixed in 2.6.15-rc2 but I'm curious as to whether anybody knows
which patch solved this, so that it can be submitted to linux-stable and added
to Gentoo's kernel releases.
Here is the oops (transcribed from a low quality photo, might include some typos)
scsi0: LSI Logic MegaRAID driver
scsi[0]: scanning scsi channel 0 [Phy 0] for non-raid devices
scsi[0]: scanning scsi channel 1 [Phy 1] for non-raid devices
Unable to handle kernel null pointer dereference at .. RIP : scsi_run_queue+25
Oops: 0000 [1] SMP
CPU 1
Pid: 0, comm: swapper Not tainted
Call Trace:
<IRQ> scsi_end_request
scsi_io_completion
scsi_softirq
__do_softirq
call_softirq
do_softirq
do_IRQ
ret_from_intr
<EOI> flat_scmd_IFI_mask
default_idle
cpu_idle
start_secondary
Any ideas? The original bug is at http://bugs.gentoo.org/show_bug.cgi?id=113463
Thanks,
Daniel
reply other threads:[~2005-11-25 11:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4386FAE6.10101@gentoo.org \
--to=dsd@gentoo.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.