On Thu, 10 May 2012, Stan Hoeppner wrote: > If this doesn't fix the issue, and memtest and other utils can see all > 64GB just fine, then I'd say you're dealing with a BIOS bug. The very top of /var/log/dmesg has the kernel debug output about the memory map. It might well tell us very quickly who is the culprit, if the user with the problem can post it for the best working case and the non-working case. > BTW, you originally mentioned you pulled all 16 sticks from a production > server that had run fine for months/years, and installed them in this > system. Now you tell use you ordered the 16 Mushkin sticks for this > build. This conflicting story leads me to wonder exactly what memory > you have, where you're being straight with us, and where you're not. > Makes it really hard to assist in this troubleshooting effort when we > don't know what information is reliable. Indeed. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh Thanks for the info about dmesg! It says this: [ 0.000000] BIOS-provided physical RAM map: [ 0.000000] BIOS-e820: 0000000000000100 - 000000000009e800 (usable) [ 0.000000] BIOS-e820: 000000000009e800 - 00000000000a0000 (reserved) [ 0.000000] BIOS-e820: 00000000000e6000 - 0000000000100000 (reserved) [ 0.000000] BIOS-e820: 0000000000100000 - 00000000dff80000 (usable) [ 0.000000] BIOS-e820: 00000000dff8e000 - 00000000dff90000 (reserved) [ 0.000000] BIOS-e820: 00000000dff90000 - 00000000dffa2000 (ACPI data) [ 0.000000] BIOS-e820: 00000000dffa2000 - 00000000dffe0000 (ACPI NVS) [ 0.000000] BIOS-e820: 00000000dffe0000 - 00000000f0000000 (reserved) [ 0.000000] BIOS-e820: 00000000ffe00000 - 0000000100000000 (reserved) [ 0.000000] BIOS-e820: 0000000100000000 - 000000101f000000 (usable) [ 0.000000] DMI present. [ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) [ 0.000000] last_pfn = 0x101f000 max_arch_pfn = 0x400000000 [ 0.000000] MTRR default type: uncachable [ 0.000000] MTRR fixed ranges enabled: [ 0.000000] 00000-9FFFF write-back [ 0.000000] A0000-EFFFF uncachable [ 0.000000] F0000-FFFFF write-protect [ 0.000000] MTRR variable ranges enabled: [ 0.000000] 0 base 000000000000 mask FFFF80000000 write-back [ 0.000000] 1 base 000080000000 mask FFFFC0000000 write-back [ 0.000000] 2 base 0000C0000000 mask FFFFE0000000 write-back [ 0.000000] 3 disabled [ 0.000000] 4 disabled [ 0.000000] 5 disabled [ 0.000000] 6 disabled [ 0.000000] 7 disabled [ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [ 0.000000] e820 update range: 00000000e0000000 - 000000101f000000 (usable) ==> (reserved) [ 0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memory, losing 61936MB of RAM. |