From: Marcel Holtmann <marcel@holtmann.org>
To: Roland Dreier <rolandd@cisco.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 4GB memory and Intel Dual-Core system
Date: Thu, 27 Oct 2005 22:51:18 +0200 [thread overview]
Message-ID: <1130446278.5416.10.camel@blade> (raw)
In-Reply-To: <52mzkuwuzg.fsf@cisco.com>
Hi Roland,
> Marcel> The BIOS and dmidecode tells me that I have 4 GB of RAM
> Marcel> installed and I don't have any idea where to look for
> Marcel> details. What information do you need to analyze this?
>
> Look at the e820 dump in your kernel bootlog. I'll bet you'll see a
> big chunk of reserved address space. Do you have any PCI devices like
> video cards that use a lot of PCI address space?
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000edbb0 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 00000000cec11000 (usable)
BIOS-e820: 00000000cec11000 - 00000000cee12000 (ACPI NVS)
BIOS-e820: 00000000cee12000 - 00000000cf68f000 (usable)
BIOS-e820: 00000000cf68f000 - 00000000cf6e9000 (ACPI NVS)
BIOS-e820: 00000000cf6e9000 - 00000000cf6ed000 (usable)
BIOS-e820: 00000000cf6ed000 - 00000000cf6ff000 (ACPI data)
BIOS-e820: 00000000cf6ff000 - 00000000cf700000 (usable)
I see the stuff above, but the system doesn't contain any PCI device. I
didn't install a PCI-Express video card, because I still use the onboard
card.
> I don't know if EM64T systems (or whatever the right term is) have a
> way of remapping some RAM above 4 GB so that you can use all your
> memory in a case like this.
The kernel is compiled for x86_64 and the term EM64T is correct. The
important question is now how do I remap that memory. Loosing almost a
full GB of memory wasn't my plan when upgrading to 4 GB.
Regards
Marcel
next prev parent reply other threads:[~2005-10-27 20:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 20:33 4GB memory and Intel Dual-Core system Marcel Holtmann
2005-10-27 20:44 ` Roland Dreier
2005-10-27 20:51 ` Marcel Holtmann [this message]
2005-10-27 20:54 ` Roland Dreier
2005-10-27 21:00 ` Marcel Holtmann
2005-10-27 21:06 ` Roland Dreier
2005-10-27 21:08 ` Marcel Holtmann
2005-10-27 21:10 ` Alejandro Bonilla
2005-10-27 20:57 ` Alejandro Bonilla
2005-10-27 20:54 ` Alejandro Bonilla
2005-10-27 20:57 ` Marcel Holtmann
2005-10-27 21:02 ` Alejandro Bonilla
2005-10-27 21:07 ` Marcel Holtmann
2005-10-27 21:15 ` Alejandro Bonilla
2005-10-27 21:19 ` Marcel Holtmann
2005-10-27 22:26 ` Joe Bob Spamtest
2005-10-27 22:05 ` Dave Jones
2005-10-27 22:09 ` Vladimir Lazarenko
2005-11-02 16:21 ` Lennart Sorensen
2005-10-27 22:11 ` Marcel Holtmann
2005-10-27 22:12 ` Dave Jones
2005-10-27 22:17 ` Marcel Holtmann
2005-10-27 22:20 ` Alejandro Bonilla
2005-10-28 0:33 ` Bernd Eckenfels
2005-10-30 22:26 ` Alan Cox
2005-10-31 3:39 ` Alejandro Bonilla Beeche
2005-10-31 13:02 ` Alan Cox
2005-10-31 23:03 ` Martin J. Bligh
2005-11-01 5:03 ` thockin
2005-10-27 22:29 ` Joel Jaeggli
2005-10-27 22:13 ` Alejandro Bonilla
2005-10-27 22:18 ` Marcel Holtmann
2005-10-28 2:35 ` Fawad Lateef
2005-10-28 3:09 ` Joel Jaeggli
2005-10-28 7:19 ` Fawad Lateef
2005-10-28 15:56 ` Joe Bob Spamtest
2005-10-28 15:29 ` Eric W. Biederman
2005-10-28 15:45 ` Alejandro Bonilla
2005-10-28 16:09 ` Eric W. Biederman
2005-10-30 22:24 ` Alan Cox
2005-11-02 16:20 ` Lennart Sorensen
2005-10-27 22:12 ` Andi Kleen
2005-10-27 21:09 ` linux-os (Dick Johnson)
2005-10-27 21:32 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2005-10-28 20:58 Lukas Hejtmanek
2005-10-29 3:32 ` Dave Jones
2005-10-29 11:15 ` Marcel Holtmann
2005-10-30 6:49 ` Dave Jones
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=1130446278.5416.10.camel@blade \
--to=marcel@holtmann.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rolandd@cisco.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