From: Jiri Slaby <jirislaby@gmail.com>
To: Andreas Hartmann <andihartmann@01019freenet.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: missing 700 MB of RAM
Date: Mon, 22 Nov 2010 23:37:45 +0100 [thread overview]
Message-ID: <4CEAF0B9.5020401@gmail.com> (raw)
In-Reply-To: <icep09$2hd$1@ID-44327.news.uni-berlin.de>
You should reply-to-all.
On 11/22/2010 10:58 PM, Andreas Hartmann wrote:
> Jiri Slaby wrote:
>> On 11/21/2010 08:02 PM, Andreas Hartmann wrote:
>>> I've got 8 GB RAM installed, but linux reports 7,3 GB. Where is the
>>> missing RAM (700 MB)?
>> ...
>>> The motherboard is a GA-MA78GM-S2H (64bit, AMD) with a on board Radeon
>>> HD 3200 VGA card. The card uses 256 MB of RAM - so 444 MB of RAM are
>>> missing. Where are they gone?
>>
>> Hi, ask your BIOS:
>>
>>> BIOS-provided physical RAM map:
>>> BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
>>> BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
>>> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>>> BIOS-e820: 0000000000100000 - 00000000afde0000 (usable)
>>> BIOS-e820: 00000000afde0000 - 00000000afde3000 (ACPI NVS)
>>> BIOS-e820: 00000000afde3000 - 00000000afdf0000 (ACPI data)
>>> BIOS-e820: 00000000afdf0000 - 00000000afe00000 (reserved)
>>> BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved)
>>> BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
>>> BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
>>
>> It reports 7677M of usable mem. Or maybe your loader is cheating on you?
>> I doubt so...
>
> Ok. That's right. Anyway, I'm wondering about the difference to free:
>
> total used free shared buffers cached
> Mem: 7706580 5271096 2435484 0 79232 3049120
>
> which is 7526M. This means, there are missing 151M of usable RAM?!
Yes, and if you look into dmesg, you will see:
Your BIOS doesn't leave a aperture memory hole
Please enable the IOMMU option in the BIOS setup
This costs you 32 MB of RAM
Mapping aperture over 32768 KB of RAM @ 20000000
Then there is some kernel code+data (11M), mem_map (108M) etc.
7677-108-32-11=7526
> I would have expected, that free reprots the same amount as the kernel
> reports to be usable.
>
> On the other hand, I would have expected, that the amount, reported by
> free + gfx-memory should nearly be 8 GB. Here it is: 7782. Thus there
> are missing 410 MB between the installed hardware and free + gfx-memory.
Since the BIOS is not reporting the memory, kernel can do only a little
about that.
> Removing the difference between free and physical ram map (410 - 151),
> ~259 MB are remaing. This is nearly the amount for the gfx-card, which
> has already been removed. Could it be, that the gfx-memory is reserved
> twice - once by the bios and another time by the kernel?!
I don't understand where you got the numbers...
regards,
--
js
next prev parent reply other threads:[~2010-11-22 22:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fRnsu-1X9-15@gated-at.bofh.it>
[not found] ` <fRrcJ-8j1-3@gated-at.bofh.it>
2010-11-22 21:58 ` missing 700 MB of RAM Andreas Hartmann
2010-11-22 22:37 ` Jiri Slaby [this message]
2010-11-21 19:02 Andreas Hartmann
2010-11-21 23:05 ` Jiri Slaby
2010-11-22 4:55 ` Thomas Fjellstrom
2010-11-22 23:26 ` Yinghai Lu
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=4CEAF0B9.5020401@gmail.com \
--to=jirislaby@gmail.com \
--cc=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.org \
/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