From: Mark Haverkamp <markh@osdl.org>
To: Kevin Fenzi <kevin@tummy.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux aacraid devel <linux-aacraid-devel@dell.com>
Subject: Re: aacraid and large memory problem (2.6.0-test11)
Date: Tue, 02 Dec 2003 12:21:22 -0800 [thread overview]
Message-ID: <1070396482.16903.11.camel@markh1.pdx.osdl.net> (raw)
In-Reply-To: <20031202193520.74481F7CC8@voldemort.scrye.com>
On Tue, 2003-12-02 at 11:35, Kevin Fenzi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Greetings,
>
> Booting 2.6.0-test11 on a machine with 8GB memory and using the
> aacraid driver results in a hang on boot. Passing mem=2048M causes it
> to boot normally. 4GB also hangs. 2.6.0-test8 booted normally on this
> same hardware.
>
> 8GB memory, dual xeon 3.06mhz with hyperthreading, RedHat 9 on it
> currently.
>
> Happy to provide details on setup/software, etc.
>
> Perhaps this patch in 2.6.0-test9 is the culprit?
> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c
This patch is what made aacraid work with over 4 gig of memory for me.
I have an 8 proc system with 16gig of memory and without this patch I
get data corruption in high memory.
I don't boot on the aacraid though.
--
Mark Haverkamp <markh@osdl.org>
next prev parent reply other threads:[~2003-12-02 20:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 19:35 aacraid and large memory problem (2.6.0-test11) Kevin Fenzi
2003-12-02 20:21 ` Mark Haverkamp [this message]
2003-12-03 16:16 ` bill davidsen
2003-12-03 20:51 ` Kevin Fenzi
2003-12-03 21:57 ` Mark Haverkamp
2003-12-03 22:28 ` Kevin Fenzi
2003-12-03 22:53 ` bill davidsen
2003-12-03 23:25 ` Mark Haverkamp
2003-12-11 17:53 ` Kevin Fenzi
2003-12-03 20:57 Kevin Fenzi
2003-12-03 21:26 ` bill davidsen
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=1070396482.16903.11.camel@markh1.pdx.osdl.net \
--to=markh@osdl.org \
--cc=kevin@tummy.com \
--cc=linux-aacraid-devel@dell.com \
--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;
as well as URLs for NNTP newsgroup(s).