From: Simon Brown <lists@700c.org>
To: linux-kernel@vger.kernel.org
Subject: Accessing more than 2GB of memory with a 32 bit kernel
Date: Wed, 12 Jun 2013 17:54:15 +0100 [thread overview]
Message-ID: <1371056055.24587.140661243104889.29DDEEB4@webmail.messagingengine.com> (raw)
Hello,
For the sake of an old prototype peripheral I'm using a non PAE 32 bit
x86 kernel and I'm having trouble accessing memory above 2 GB. The
system has 4GB installed and all is well with a PAE kernel.
I'm obviously expecting to lose some memory due to memory mapped devices
but I wasn't expecting to lose 2GB. Instead I'm suspecting a BIOS bug.
The system reports:
free -m
total used free shared buffers
cached
Mem: 2012 491 1521 0 40
277
The mtrr table looked odd so I enabled sanitisation:
[ 0.000000] original variable MTRRs
[ 0.000000] reg 0, base: 2GB, range: 2GB, type UC
[ 0.000000] reg 1, base: 0GB, range: 4GB, type WB
[ 0.000000] reg 2, base: 4GB, range: 2GB, type WB
[ 0.000000] total RAM covered: 4096M
[ 0.000000] Found optimal setting for mtrr clean up
[ 0.000000] gran_size: 64K chunk_size: 64K num_reg: 2
lose cover RAM: 0G
[ 0.000000] New variable MTRRs
[ 0.000000] reg 0, base: 0GB, range: 2GB, type WB
[ 0.000000] reg 1, base: 4GB, range: 2GB, type WB
I don't understand the gap in the new table.
The motherboard is an Asus P5K with an Intel® P35 chipset. I'm using the
ubuntu lucid kernel (2.6.32) but the problem is also present with the
ubuntu precise kernel.
I'm at the limit of my understanding, can anyone advise how to debug
further?
Thanks,
Simon
next reply other threads:[~2013-06-12 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 16:54 Simon Brown [this message]
2013-06-12 17:35 ` JA Magallón
2013-06-12 20:10 ` Rik van Riel
2013-06-12 21:33 ` JA Magallón
2013-06-13 22:38 ` Simon Brown
2013-06-13 22:32 ` Simon Brown
2013-06-14 0:14 ` Rik van Riel
2013-06-14 0:31 ` 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=1371056055.24587.140661243104889.29DDEEB4@webmail.messagingengine.com \
--to=lists@700c.org \
--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
all inboxes | Powered by JetHome®