I can't see whole 8GB of ram.
With F2 BIOS release i can only work with kernel param mem=4G.
After updating to F4 BIOS release I can work with mem=8G, but I see this:
# free -m
total used free shared buffers cached
Mem: 6473 474 5999 0 29 278
Without mem=8G kernel starts to slow down and hangs while starting
filesystem.
There is no message.
My whole memory was tested with memtest. Full test took about 48hour. Is
it wrong?
I have: Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
There are 4 * 2GB / 667MHz DIMMs.
# cat /proc/iomem |grep RAM
00000000-0009f7ff : System RAM
00100000-9fedffff : System RAM
100000000-25fffffff : System RAM
# dmesg|grep BIOS-e820
BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
BIOS-e820: 0000000000100000 - 000000009fee0000 (usable)
BIOS-e820: 000000009fee0000 - 000000009fee3000 (ACPI NVS)
BIOS-e820: 000000009fee3000 - 000000009fef0000 (ACPI data)
BIOS-e820: 000000009fef0000 - 000000009ff00000 (reserved)
BIOS-e820: 00000000c0000000 - 00000000c4000000 (reserved)
BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
BIOS-e820: 0000000100000000 - 0000000260000000 (usable)
I can see that higer memory range was remmaped,
by why accesing something greater than 100000000 is problematic?
Do I need to change something i kernel configuration?
-
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| H. Peter Anvin | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Christoph Lameter | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
git: | |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
