From: Kevin Fenzi <kevin@tummy.com>
To: 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:57:27 -0700 [thread overview]
Message-ID: <20031203205730.88B7EF7C86@voldemort.scrye.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Bill> | > Perhaps this patch in 2.6.0-test9 is the culprit? | >
Bill> http://www.linuxhq.com/kernel/v2.6/0-test9/drivers/scsi/aacraid/comminit.c
Bill> | | This patch is what made aacraid work with over 4 gig of
Bill> memory for me. | I have an 8 proc system with 16gig of memory
Bill> and without this patch I | get data corruption in high memory.
Bill> | | I don't boot on the aacraid though.
Bill> It would be interesting to know what memory model is being used
Bill> in each case. Both CONFIG_HIGHMEM* and maybe user/kernel split
Bill> might play.
I am using the 2.6.0 rpms from:
http://people.redhat.com/arjanv/2.5/
Specifically its:
http://people.redhat.com/arjanv/2.5/RPMS.kernel/kernel-smp-2.6.0-0.test11.1.99.i686.rpm
The kernel-2.6.0-test11-i686-smp.config
says:
# CONFIG_NOHIGHMEM is not set
# CONFIG_HIGHMEM4G is not set
CONFIG_HIGHMEM64G=y
CONFIG_HIGHMEM=y
CONFIG_BLK_DEV_UMEM=m
CONFIG_DEBUG_HIGHMEM=y
Bill> Based on one boot with one machine, 4G RAM, it didn't hang.
Bill> Unfortunately a production machine, I was playing following some
Bill> "unscheduled maintenence."
Did you have HIGHMEM set?
kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQE/zk463imCezTjY0ERAuboAKCN4XxByy8NO7UUK2h1eyXtbBIjZgCfSj9M
budyunjfaRG+UhhSHR3IZss=
=uXXJ
-----END PGP SIGNATURE-----
next reply other threads:[~2003-12-03 20:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 20:57 Kevin Fenzi [this message]
2003-12-03 21:26 ` bill davidsen
-- strict thread matches above, loose matches on Subject: below --
2003-12-02 19:35 Kevin Fenzi
2003-12-02 20:21 ` Mark Haverkamp
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
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=20031203205730.88B7EF7C86@voldemort.scrye.com \
--to=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
Powered by JetHome