From: Christoph Hellwig <hch@infradead.org>
To: Chris Meadors <clubneon@hereintown.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: MegaRAID on AMD64 under 2.6.1
Date: Thu, 8 Jan 2004 12:12:27 +0000 [thread overview]
Message-ID: <20040108121227.B8987@infradead.org> (raw)
In-Reply-To: <1073512887.8211.39.camel@clubneon.priv.hereintown.net>; from clubneon@hereintown.net on Wed, Jan 07, 2004 at 05:01:28PM -0500
On Wed, Jan 07, 2004 at 05:01:28PM -0500, Chris Meadors wrote:
> I seem to recall some discussion reguarding the MegaRAID driver use on
> AMD64 machines with large amounts of RAM. My machine only has 2 GB of
> RAM, and the driver was working fine under 2.6.0 (note I use Andi
> Kleen's x86_64 patch kit, on an otherwise stock kernel). But with the
> release of 2.6.1-rc1 the driver does not load. I have module support
> disabled and all needed drivers built into the kernel. All my file
> systems (including root) are on logical drives provided by the RAID
> controller. So the kernel panics when attempting to mount the root
> filesystem, if the driver doesn't load.
>
> Looking through the 2.6.1-rc2 patch, it seems that the megaraid.[ch]
> files got some large amount of re-ordering. So I can't easily spot what
> change might have effected the driver.
>
> Here is the lspci output for my specific card:
Can you put a printk into megaraid_probe_one() whether that one actually
gets called?
Also lspci -n output would be very nice to have.
next prev parent reply other threads:[~2004-01-08 12:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 22:01 Chris Meadors
2004-01-08 12:12 ` Christoph Hellwig [this message]
2004-01-08 16:51 ` Chris Meadors
2004-01-08 16:55 ` Christoph Hellwig
2004-01-08 17:19 ` [PATCH] LSI Logic MegaRAID3 PCI ID [Was: MegaRAID on AMD64 under 2.6.1] Chris Meadors
2004-01-08 20:29 ` Chris Meadors
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=20040108121227.B8987@infradead.org \
--to=hch@infradead.org \
--cc=clubneon@hereintown.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®