From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "Patrick J. LoPresti" <patl@users.sourceforge.net>
Cc: Atul.Mukker@lsil.com, linux-scsi@vger.kernel.org
Subject: Re: Linux 2.6.8.1 + megaraid-2.20.3.0 == Oops
Date: Fri, 20 Aug 2004 16:08:02 -0700 [thread overview]
Message-ID: <20040820160802.7b74cfa3.rddunlap@osdl.org> (raw)
In-Reply-To: <s5g3c2hkcod.fsf@patl=users.sf.net>
On 20 Aug 2004 12:22:26 -0400 Patrick J. LoPresti wrote:
| My hardware is a Dell PowerEdge 650 server with a PERC4/SC RAID
| controller. I downloaded the 2.6.8.1 Linux kernel from kernel.org and
| applied this patch:
|
| ftp://ftp.lsil.com/pub/linux-megaraid/drivers/version-2.20.3.0/megaraid2.20.3.0-lk2.6.8.1.patch.gz
|
| The system generates an Oops on boot. I am attaching both my kernel
| .config and the console startup messages below.
|
| Let me know if I can provide any other information.
Looks like mraid_mm_init() hasn't done the
INIT_LIST_HEAD(&adapters_list_g);
yet. You might be able to verify that by using
"initcall_debug" on the kernel boot/command line.
I don't see the expected "megaraid cmm:" message, e.g.
I expected to be able to build these drivers as modules, but that's
not allowed by their Kconfig. Is that because of the module
inter-dependencies?
--
~Randy
next prev parent reply other threads:[~2004-08-20 23:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 16:22 Linux 2.6.8.1 + megaraid-2.20.3.0 == Oops Patrick J. LoPresti
2004-08-20 23:08 ` Randy.Dunlap [this message]
2004-08-21 16:54 ` Patrick J. LoPresti
2004-08-21 17:00 ` Patrick J. LoPresti
2004-08-21 18:07 ` Randy.Dunlap
2004-08-22 19:12 ` Patrick J. LoPresti
2004-08-22 21:31 ` Randy.Dunlap
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=20040820160802.7b74cfa3.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=Atul.Mukker@lsil.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patl@users.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox