From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Missing 1GB RAM, where is it?
Date: Thu, 14 Apr 2011 13:17:11 +0100 [thread overview]
Message-ID: <BANLkTi=ACqho2XGmuww_yGAVY_NRFg646g@mail.gmail.com> (raw)
In-Reply-To: <297dfc5b.7e06db81.4da6da13.9bbb0@o2.pl>
Hi....
On Thu, Apr 14, 2011 at 12:27, andrzej-kardas <andrzej-kardas@o2.pl> wrote:
> Highmem is on:
>
> cat /boot/config-2.6.33.1 ?| grep -i highmem
> # CONFIG_NOHIGHMEM is not set
> # CONFIG_HIGHMEM4G is not set
> CONFIG_HIGHMEM64G=y
> CONFIG_HIGHMEM=y
> # CONFIG_DEBUG_HIGHMEM is not set
Ok, great... support is there...
>>
>> 2. the complete entry grub/lilo stanza that is responsible to execute
>> your current running kernel
>>
>
> menuentry 'Linux 2.6.33.1' --class ubuntu --class gnu-linux --class gnu --class os {
> ? ? ? recordfail
> ? ? ? insmod ext2
> ? ? ? set root='(hd0,2)'
> ? ? ? search --no-floppy --fs-uuid --set 2875dab1-590c-4c56-a1a8-69ac3221e339
> ? ? ? linux ? /boot/vmlinuz-2.6.33.1 root=UUID=2875dab1-590c-4c56-a1a8-69ac3221e339 ro ? quiet splash
> ? ? ? initrd ?/boot/initrd.img-2.6.33.1
> }
OK, so far, no memory reserve or kdump alike execution I saw
above...that's two..
> I noticed that addresses in /proc/iomem are not contiguous as follow:
>
>
> root at lpt:~# cat /proc/iomem
> 00000000-00001fff : System RAM
> 00002000-0000ffff : reserved
> 00010000-0009f7ff : System RAM
> 0009f800-0009ffff : reserved
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000cf000-000d07ff : Adapter ROM
>
>
> hole - how about address range from 000d0800 to 000dffff ??
Now that's something I can't answer directly.... there's a chance that
the address range is reserved for unknown reason (so far).
Hm, how about showing us the output of "cat /proc/meminfo"?
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
next prev parent reply other threads:[~2011-04-14 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 16:06 Enabling Signals in kernel Vijay Ram Chitrapu
2011-04-13 1:01 ` Haojian Zhuang
2011-04-13 19:30 ` julie Sullivan
2011-04-13 17:20 ` Missing 1GB RAM, where is it? Andrzej Kardas
2011-04-14 2:42 ` Mulyadi Santosa
2011-04-14 11:27 ` andrzej-kardas
2011-04-14 12:17 ` Mulyadi Santosa [this message]
2011-04-14 15:23 ` Andrzej Kardas
2011-04-16 6:07 ` Mulyadi Santosa
2011-04-14 15:09 ` Adrian Cornish
2011-04-14 15:43 ` Andrzej Kardas
2011-04-14 16:12 ` Haojian Zhuang
2011-04-15 0:45 ` Haojian Zhuang
[not found] ` <BANLkTik7g8vEf6X+suzwbXD1b4ow1__2xQ@mail.gmail.com>
2011-04-17 7:58 ` Missing 1GB RAM, where is it? - SUMMARY Andrzej Kardas
2011-04-17 15:31 ` julie Sullivan
2011-04-18 10:17 ` andrzej-kardas
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='BANLkTi=ACqho2XGmuww_yGAVY_NRFg646g@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).