Hi....
On Thu, Apr 14, 2011 at 12:27, andrzej-kardas <andrzej-kardas@xxxxx> 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@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
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
