Re: 2.6.16-rc5 huge memory detection regression

From: Martin MOKREJŠ
Date: Tue Mar 07 2006 - 07:26:07 EST


BTW, BIOS during the POST test shows all 16GB, it is only linux-2.6.16-rc5 who get's it wrong. Even the summary window provided by BIOS just before grub gets loaded shows 16GB of RAM.
I don't believe it is anything else then the kernel.

Andrew Morton wrote:
Martin MOKREJ__ <mmokrejs@xxxxxxxxxxxxxxxxxxxxxx> wrote:

I just tested 2.6.16-rc5 kernel on MSI 9136 dual Xeon server motherboard with 16 GB of memory and the kernel detects only 8 GB of RAM instead. 2.6.15 kernel detected properly 16 GB. I haven't tested any kernel revisions in between these two, but could if you point me in a specific direction. Attaching diff(1) output of dmesg(1) outputs.
Please Cc: me in replies. Thanks!
Martin


[boot-2.6.15_to_16-rc5.diff text/plain (12156 bytes)]


The diff is useful.


--- tmp/boot-2.6.15.txt 2006-03-07 11:45:48.015509048 +0100
+++ tmp/boot-2.6.16-rc5.txt 2006-03-07 11:45:48.029506920 +0100
@@ -1,4 +1,4 @@
-Linux version 2.6.15 (root@phylo) (gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9)) #1 SMP Mon Mar 6 20:20:06 MET 2006
+Linux version 2.6.16-rc5 (root@phylo) (gcc version 3.4.5 (Gentoo 3.4.5-r1, ssp-3.4.5-1.0, pie-8.7.9)) #1 SMP Mon Mar 6 19:58:24 MET 2006
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009a800 (usable)
BIOS-e820: 000000000009a800 - 00000000000a0000 (reserved)
@@ -12,16 +12,16 @@
BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
BIOS-e820: 00000000ff800000 - 00000000ffc00000 (reserved)
BIOS-e820: 00000000fffffc00 - 0000000100000000 (reserved)
- BIOS-e820: 0000000100000000 - 0000000430000000 (usable)
-16256MB HIGHMEM available.
+ BIOS-e820: 0000000100000000 - 0000000230000000 (usable)
+8064MB HIGHMEM available.


These numbers are what the BIOS is telling the kernel about your machine. Was the BIOS changed?

If not, you might need to wiggle those DIMMs or something.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/