From: Robert Hancock <hancockr@shaw.ca>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: ravibt@gmail.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS detects 4 GB RAM, but kernel does not
Date: Fri, 28 Jul 2006 11:06:08 -0600 [thread overview]
Message-ID: <44CA4400.5020005@shaw.ca> (raw)
In-Reply-To: <Pine.LNX.4.61.0607281902560.4972@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> Essentially I don't think there is much you can do about this on this board.
>> The memory space starting at around 3.2GB is being used by the memory-mapped IO
>> regions for the PCI and PCI Express devices and motherboard resources and
>> therefore "covers up" the RAM in that part of the address space. The solution
>> to this is for the system to remap the affected memory above the 4GB mark,
>> which is possible with Athlon 64/Opteron CPUs and on some of the Intel server
>> chipsets. However, I don't think any Intel desktop chipsets support this for
>> some unfathomable reason.
>
> Maybe PAE can help?
No.. it's not a matter of being unable to reach the address space, but
the memory used by the IO regions is essentially overridden and
unavailable to the kernel. PAE is not applicable on x86-64 anyway..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next prev parent reply other threads:[~2006-07-28 17:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1153931278.034068.54630@h48g2000cwc.googlegroups.com>
2006-07-26 16:54 ` BIOS detects 4 GB RAM, but kernel does not Robert Hancock
2006-07-28 17:03 ` Jan Engelhardt
2006-07-28 17:06 ` Robert Hancock [this message]
[not found] ` <1153933737.200164.160870@m73g2000cwd.googlegroups.com>
[not found] ` <1154007393.940693.259680@i42g2000cwa.googlegroups.com>
[not found] ` <mH3yg.16777$2u4.7977@trnddc06>
2006-07-27 19:41 ` Robert Hancock
[not found] ` <1154112339.037481.119210@p79g2000cwp.googlegroups.com>
2006-07-29 2:04 ` Robert Hancock
2006-07-29 22:21 ` Andi Kleen
[not found] ` <fa.6TLi9h8OI9J6KX0+lv+D4/CEU0U@ifi.uio.no>
[not found] ` <fa.adpnQx0XAWgd4+g2tR5HDa2qHDw@ifi.uio.no>
[not found] ` <1154145714.279248.233230@m73g2000cwd.googlegroups.com>
2006-07-29 18:12 ` Robert Hancock
[not found] ` <1154143992.635239.225440@p79g2000cwp.googlegroups.com>
2006-07-29 18:25 ` Robert Hancock
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=44CA4400.5020005@shaw.ca \
--to=hancockr@shaw.ca \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ravibt@gmail.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