From: Kevin Fenzi <kevin@tummy.com>
To: Mark Haverkamp <markh@osdl.org>
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: Wed, 3 Dec 2003 13:51:40 -0700 [thread overview]
Message-ID: <20031203205141.EB67EF7C86@voldemort.scrye.com> (raw)
In-Reply-To: <1070396482.16903.11.camel@markh1.pdx.osdl.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "Mark" == Mark Haverkamp <markh@osdl.org> writes:
Mark> 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
Mark> This patch is what made aacraid work with over 4 gig of memory
Mark> for me. I have an 8 proc system with 16gig of memory and without
Mark> this patch I get data corruption in high memory.
Mark> I don't boot on the aacraid though.
Is there any way you can try booting from it and see if it's a boot
issue for you as well?
I can try booting the one here from something else and see if it works
with that.
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/zkzd3imCezTjY0ERAtdRAJ9NIp56DWRFI6zxpbgyLtKQzkYcIACfYKil
Z6XcmnrXQ9Qsiy24d7ac044=
=a+PX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-12-03 20:51 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
2003-12-03 16:16 ` bill davidsen
2003-12-03 20:51 ` Kevin Fenzi [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20031203205141.EB67EF7C86@voldemort.scrye.com \
--to=kevin@tummy.com \
--cc=linux-aacraid-devel@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.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.