From: Andreas Dilger <adilger@turbolabs.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Eugene Chupkin <ace@credit.com>,
linux-kernel@vger.kernel.org, tmeagher@credit.com
Subject: Re: 2.4.x ram issues?
Date: Tue, 12 Feb 2002 21:31:19 -0700 [thread overview]
Message-ID: <20020212213119.A25535@lynx.turbolabs.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10202121726530.683-100000@mail.credit.com> <E16aoic-0003of-00@the-village.bc.nu>
In-Reply-To: <E16aoic-0003of-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Wed, Feb 13, 2002 at 02:00:22AM +0000
On Feb 13, 2002 02:00 +0000, Alan Cox wrote:
> > I have a problem with high ram support on 2.4.7 to 2.4.17 all behave the
> > same. I have a quad Xeon 700 box with 16gb of ram on an Intel SKA4 board.
> > The ram is all the same 16 1gb PC100 SDRAM modules from Crucial. If I
> > compile the kernel with high ram (64gb) support, my system runs very slow,
> > it takes about 15 minutes for make menuconfig to come up. If I recompile
> > the kernel with 4gb support, it runs perfectly normal and very fast, but I
> > have 12 gigs that I can't use. Is this a known issue? Is there a fix? I
> > tried just about everything and I am all out of options. Please help!
>
> Thats almost certainly indicating that the memory type range registers
> were not set up correcly by the BIOS. Check /proc/mtrr and also ask your
> vendor about BIOS updates to address the problem
The other possibility with that much RAM is that the page tables are taking
up all of the low RAM. Andrea has a patch to put the page tables into
higmem in the recent -aa kernels.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2002-02-13 4:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 1:40 Eugene Chupkin
2002-02-13 2:00 ` Alan Cox
2002-02-13 2:52 ` Eugene Chupkin
2002-02-13 4:31 ` Andreas Dilger [this message]
2002-02-13 19:05 ` Eugene Chupkin
2002-02-13 19:21 ` Andreas Dilger
2002-02-13 20:33 ` Eugene Chupkin
2002-02-13 22:29 ` Mike Fedyk
2002-02-21 23:09 ` Eugene Chupkin
2002-02-14 19:13 ` Pavel Machek
2002-02-14 20:54 ` Eugene Chupkin
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=20020212213119.A25535@lynx.turbolabs.com \
--to=adilger@turbolabs.com \
--cc=ace@credit.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tmeagher@credit.com \
/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®