Re: Bug#584846: Detects only 64MB and fails to boot on Intel GreenCity board if e820 hooked by GRUB2

[H. Peter Anvin]

On 06/12/2010 06:58 AM, Ben Hutchings wrote:
> Josh Triplett reported this problem with memory sizing:
> 
>>
>> A kernel built from c549e71d073a6e9a4847497344db28a784061455 finds <64MB
>> of RAM; a kernel built from c549e71d073a6e9a4847497344db28a784061455^
>> successfully finds all 4GB of RAM.
>>
>> Also note that newer upstream kernels, including v2.6.35-rc3, fail as
>> well.  Since later kernels revert part of the above commit, the issue
>> must lie with the parts of the commit not reverted.
>>
>> And, again, I can reproduce this using the stock upstream GRUB2 1.98
>> release built from source, by booting it from a USB key, and then
>> booting the disk MBR via:
>>
>> set root=(hd1)
>> drivemap (hd1) (hd0)
>> chainloader +1
>> boot
>>
>> Nothing special about drivemap here; anything that uses grub's mmap
>> module to reserve memory via e820 (GRUB_MACHINE_MEMORY_RESERVED) will
>> cause grub to hook e820 and trigger this bug.  However, in stock grub,
>> only drivemap does this.
>>

It's kind of hard to know what is involved, since clearly it relates to
Grub2, which -- how do I say this politely -- seems to excel at doing
things in the most inferior way possible.  This is a great example of that.

The most likely reason it fails is because Grub2 uses ACPI 3-style reads
of the board memory map, gets wrong results for the same reasons the
kernel do, and then pass then downstream to the kernel.  As such, there
is absolutely nothing the kernel can do about it.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

--
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/