public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: ronis@ronispc.chem.mcgill.ca
Cc: linux-kernel@vger.kernel.org
Subject: Re: Memory not being reported
Date: Sat, 24 Jan 2009 02:37:13 -0600	[thread overview]
Message-ID: <497AD339.2030602@shaw.ca> (raw)
In-Reply-To: <1232658295.3455.7.camel@ronispc.chem.mcgill.ca>

David Ronis wrote:
> I'm running 2.6.28.1 on an i686 (slackware-12.1 for the most part) box.
> I recently added some extra memory, expanding from 2Gb to 4.  Everything
> works as expected except that not all of the memory seems to be seen.
> 
> free returns:
> 
>              total       used       free     shared    buffers
> cached
> Mem:       3374860    2099504    1275356          0      86612
> 1032024
> -/+ buffers/cache:     980868    2393992
> Swap:       497972          0     497972
> 
> 
> and cat /proc/meminfo gives:
> 
> MemTotal:        3374860 kB
> MemFree:         1199184 kB
> Buffers:           86816 kB
> Cached:          1036240 kB
> SwapCached:            0 kB
> Active:          1375864 kB
> 
> etc.
> 
> On the other hand, user-space tools like lshw show the 4 1Gb DIMMS as
> does the BIOS configuration boot menu.
> 
> One suspicion is that the configure option CONFIG_HIGHMEM4G=y
> should be unset and the CONFIG_HIGHMEM64G  should be.

Yes, it should be. However, if your chipset doesn't support remapping 
memory above the 4GB mark (some don't, and this is needed in this case 
because various IO areas use up some of the address space below 4GB) 
then it won't be possible to make use of any of that RAM.

Note that when running with more than 4GB of RAM it's generally 
preferable to run a 64-bit kernel if the machine supports it.

> 
> Any help would be appreciated, as would a separate CC since I don't
> subscribe to the list.
> 
> Thanks in advance
> 
> David
> 


  parent reply	other threads:[~2009-01-24  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 21:04 Memory not being reported David Ronis
2009-01-22 22:27 ` Wakko Warner
2009-01-23 12:44 ` markus reichelt
2009-01-24  8:37 ` Robert Hancock [this message]
2009-01-25 17:13   ` David Ronis
2009-01-25 20:10     ` 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=497AD339.2030602@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ronis@ronispc.chem.mcgill.ca \
    /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