linux-kernel - Intel-Quad on GA-P35-S3 motherboard with 4*2GB

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 14 Sep 2007 10:50:24 +0200
From:	Wojciech Kromer <wojciech.kromer@....com.pl>
To:	linux-kernel@...r.kernel.org
Subject: Intel-Quad on GA-P35-S3 motherboard with 4*2GB 

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?







 

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/