From: "James Kirin" <james.kirin40@gmail.com>
To: "Roland Dreier" <rdreier@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y
Date: Tue, 13 Jan 2009 22:10:18 -0500 [thread overview]
Message-ID: <baeb34bc0901131910n55cae670qc9d02c9f78c6432@mail.gmail.com> (raw)
In-Reply-To: <adaeiz6k4o4.fsf@cisco.com>
Thank you for your reply, Roland. Unfortunately, this continues
happening after having installed the most recent version of the BIOS
available from Dell.
I understand this is a problem in the BIOS and not the kernel, but is
there a way to have the kernel work around this bug in the BIOS and
make that memory accessible? Eg,
http://www.gossamer-threads.com/lists/linux/kernel/991748#991748
The difference seems to be that the BIOS on this machine I am using
does list 8GB memory available.
Thanks for any help,
James
On Tue, Jan 13, 2009 at 9:22 PM, Roland Dreier <rdreier@cisco.com> wrote:
> > I am running kernel 2.6.28 on a computer with 8GB RAM. The BIOS
> > detects all 8GB, yet
> >
> > jk@as12:~$ free
> > total used free shared buffers cached
> > Mem: 3622504 799696 2822808 0 90936 369604
> > -/+ buffers/cache: 339156 3283348
> > Swap: 6867776 0 6867776
>
> The message in your kernel log:
>
> [ 0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 4096MB of RAM.
> [ 0.000000] ------------[ cut here ]------------
> [ 0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/main.c:1662 mtrr_trim_uncached_memory+0x283/0x2a4()
>
> is a clue. You might want to look for a BIOS update for your
> motherboard.
>
> - R.
>
next prev parent reply other threads:[~2009-01-14 3:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 1:46 James Kirin
2009-01-14 2:22 ` Roland Dreier
2009-01-14 3:10 ` James Kirin [this message]
2009-01-14 6:07 ` Yinghai Lu
2009-01-14 16:14 ` Roland Dreier
2009-01-14 18:16 ` Yinghai Lu
2009-01-15 19:50 ` James Kirin
2009-01-15 20:35 ` James Kirin
2009-01-15 20:45 ` Yinghai Lu
2009-01-15 20:51 ` Yinghai Lu
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=baeb34bc0901131910n55cae670qc9d02c9f78c6432@mail.gmail.com \
--to=james.kirin40@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.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®