From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Tom Moore <tmoore@spatial.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4Gb ram not showing up
Date: Mon, 4 Jun 2007 15:10:52 -0400 [thread overview]
Message-ID: <20070604191052.GD10008@csclub.uwaterloo.ca> (raw)
In-Reply-To: <46642C60.209@spatial.ca>
On Mon, Jun 04, 2007 at 11:14:40AM -0400, Tom Moore wrote:
> I am having some difficulty trying to get my 4Gb of ram recognized by
> the system. I have tried googling around to get some information on how
> to do this configuration, but I have come up dry. I suspect that the
> reason that there is not much info on how to set things up is because
> usually it just works. However, on my system I don't think it is.
>
> By the way, I am not subscribed to this mailing list, so could you
> please CC me any replies.
>
> The basics are that I have an Athlon 64 X2 Dual core, 4Gb ram, ASUS
> M2N-MX motherboard. The bios has a configuration item for MTRR mapping,
> with options for CONTINUOUS and DISCRETE. I have selected CONTINUOUS,
> which explicitly describes the PCI hole as non-cacheable. The other
> option leaves the PCI hole undescribed.
>
> My config has selected
> CONFIG_HIGHMEM4G=y
That supports of to 4GB memory space.
> free -m reports the following....
> total used free shared buffers cached
> Mem: 2906 2794 112 0 275 31
> -/+ buffers/cache: 2487 419
> Swap: 4996 366 4630
>
>
> /proc/mtrr contains the following....
>
> reg00: base=0x00000000 ( 0MB), size=4096MB: write-back, count=1
> reg01: base=0x100000000 (4096MB), size=1024MB: write-back, count=1
> reg02: base=0xc0000000 (3072MB), size=1024MB: uncachable, count=1
Your memory map however has 3GB at address 0 and 1GB at address 4GB (so
memory is places at address 0 - 3GB and 4-5GB. The addresses from 3 to
4GB are reserved for PCI).
If you run a 64bit kernel you will see it all, or you can use a kernel
configured for 64GB memory space.
> Relevant bootup messages include these....
> Jun 3 13:50:52 fawkes Linux version 2.6.20-gentoo-r8 (root@fawkes) (gcc
> version 4.1.1 (Gentoo 4.1.1-r3)) #6 SMP Tue May 15 10:18:59 EDT 2007
> Jun 3 13:50:52 fawkes BIOS-provided physical RAM map:
> Jun 3 13:50:52 fawkes sanitize start
> Jun 3 13:50:52 fawkes sanitize end
> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000000000000 size:
> 000000000009fc00 end: 000000000009fc00 type: 1
> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM
> Jun 3 13:50:52 fawkes copy_e820_map() start: 000000000009fc00 size:
> 0000000000000400 end: 00000000000a0000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000000e0000 size:
> 0000000000020000 end: 0000000000100000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000000100000 size:
> 00000000b7ec0000 end: 00000000b7fc0000 type: 1
> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7fc0000 size:
> 000000000000e000 end: 00000000b7fce000 type: 3
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7fce000 size:
> 0000000000022000 end: 00000000b7ff0000 type: 4
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000b7ff0000 size:
> 0000000000010000 end: 00000000b8000000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000fec00000 size:
> 0000000000001000 end: 00000000fec01000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000fee00000 size:
> 0000000000100000 end: 00000000fef00000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 00000000ff780000 size:
> 0000000000880000 end: 0000000100000000 type: 2
> Jun 3 13:50:52 fawkes copy_e820_map() start: 0000000100000000 size:
> 0000000040000000 end: 0000000140000000 type: 1
> Jun 3 13:50:52 fawkes copy_e820_map() type is E820_RAM
> Jun 3 13:50:52 fawkes BIOS-e820: 0000000000000000 - 000000000009fc00
> (usable)
> Jun 3 13:50:52 fawkes BIOS-e820: 000000000009fc00 - 00000000000a0000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000000e0000 - 0000000000100000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 0000000000100000 - 00000000b7fc0000
> (usable)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7fc0000 - 00000000b7fce000
> (ACPI data)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7fce000 - 00000000b7ff0000
> (ACPI NVS)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000b7ff0000 - 00000000b8000000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000fec00000 - 00000000fec01000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000fee00000 - 00000000fef00000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 00000000ff780000 - 0000000100000000
> (reserved)
> Jun 3 13:50:52 fawkes BIOS-e820: 0000000100000000 - 0000000140000000
> (usable)
> Jun 3 13:50:52 fawkes Warning only 4GB will be used.
> Jun 3 13:50:52 fawkes Use a PAE enabled kernel.
Oh look, it even tells you right there that you have to use a PAE (>4GB
for 32bit machines) kernel to get all your ram.
--
Len Sorensen
next prev parent reply other threads:[~2007-06-04 19:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 15:14 Tom Moore
2007-06-04 19:10 ` Lennart Sorensen [this message]
2007-06-04 19:45 ` Tom Moore
2007-06-04 22:28 ` Wakko Warner
2007-06-05 13:12 ` Tom Moore
2007-06-05 13:37 ` Joseph Fannin
[not found] ` <46646B4C.2070707@spatial.ca>
2007-06-05 18:57 ` Lennart Sorensen
2007-06-06 21:18 ` Satyam Sharma
2007-06-07 6:58 ` Jan Engelhardt
2007-06-07 13:33 ` Tom Moore
2007-06-07 20:13 ` Lennart Sorensen
2007-06-06 11:45 ` Andi Kleen
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=20070604191052.GD10008@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=tmoore@spatial.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
all inboxes | Powered by JetHome®