public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: ravibt@gmail.com, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: BIOS detects 4 GB RAM, but kernel does not
Date: Wed, 26 Jul 2006 10:54:46 -0600	[thread overview]
Message-ID: <44C79E56.2040603@shaw.ca> (raw)
In-Reply-To: <1153931278.034068.54630@h48g2000cwc.googlegroups.com>

ravibt@gmail.com wrote:
> Hello,
> 
>  On a dual core Pentium 4 EM64T machine (Intel Desktop Board D915GAV),
> we used four 1GB RAM (DDR 400) modules. The BIOS (EV91510A.86A.0444)
> detected all the four 1 GB modules, but once the OS is booted, only
> ~3.1GB is available for usage (from dmesg: "Memory: 3210516k/3267772k
> available"; see below). The kernel used is version 2.6.9-22.ELsmp
> coming with 'CentOS release 4.2 Final'.
> [The four RAM modules have been tested OK with the 'memtest'].
> 
>  Using "mem=4096m" while booting the kernel also did not help. Searched
> through the old messages and it looks like in most of the cases
> enabling some memory-hole related option in BIOS is suggested, but in
> this case probably the BIOS is fine. Not sure if some kernel
> configuration option is missing or if someother version of the kernel
> needs to be used.
> 
> This being a 64 bit machine, we expected memory-remap to be happening.
> Is there a way in which ~900 MB of RAM can be made usable?
> Any pointers will be of great help.
> 
> Please let me know if more information is needed than the following
> transcripts (/proc/iomem and dmesg):

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.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2006-07-26 16:54 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 ` Robert Hancock [this message]
2006-07-28 17:03   ` BIOS detects 4 GB RAM, but kernel does not Jan Engelhardt
2006-07-28 17:06     ` Robert Hancock
     [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=44C79E56.2040603@shaw.ca \
    --to=hancockr@shaw.ca \
    --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