Re: 2.6.16-rc5 huge memory detection regression

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/

Relevant Pages

  • [PATCH 2.6.24] mm: BadRAM support for broken memory
    ... This is the latest version of the BadRAM patch, ... run Linux on broken memory. ... a new kernel appeared, ... the BadRAM subsystem dealing with statically challanged RAM modules. ...
    (Linux-Kernel)
  • Re: Patch 4/6 randomize the stack pointer
    ... > it," so perhaps this would be a good compromise. ... less than 512M of memory to keep track of. ... what about the case where you have gobs of RAM and need a highmem ... Kernel data structures, no. ...
    (Linux-Kernel)
  • Re: Allocating kernel memory
    ... > I never complained about the real memory that was used but pointed out ... > that a large portion of the kernel virtual address space is used up. ... RAM you should avoid PAE, ... But it was limited to 1GB of physical RAM. ...
    (comp.os.linux.development.system)
  • Re: OS-question
    ... MacOS X supports>4GB of RAM on IA32 and so does FreeBSD but I don't know ... Linux can use up to 64 Gigabytes of physical memory on x86 systems. ... If you are compiling a kernel which will never run on a machine with ...
    (comp.arch)
  • Re: ISP1760 driver crashes
    ... I recompiled the kernel without HIGHMEM and it works. ... the memory is highmem and not in kernel so the buffer is NULL ... usb-storage doesn't allocate the memory. ...
    (Linux-Kernel)