Re: HIGHMEM

From: William Lee Irwin III (wli@holomorphy.com)
Date: Tue Apr 15 2003 - 10:14:39 EST


On Tue, Apr 15, 2003 at 04:39:30PM +0200, Nagy Tibor wrote:
> <6>BIOS-provided physical RAM map:
> <4> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> <4> BIOS-e820: 0000000000100000 - 00000000fbffe000 (usable)
> <4> BIOS-e820: 00000000fbffe000 - 00000000fc000000 (reserved)
> <4> BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> <4> BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
> <4> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> <5>3135MB HIGHMEM available.
> <5>896MB LOWMEM available.
[...]
> <6>BIOS-provided physical RAM map:
> <4> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> <4> BIOS-e820: 0000000000100000 - 00000000dfff0000 (usable)
> <4> BIOS-e820: 00000000dfff0000 - 00000000dfffec00 (ACPI data)
> <4> BIOS-e820: 00000000dfffec00 - 00000000dffff000 (reserved)
> <4> BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
> <4> BIOS-e820: 00000000fee00000 - 00000000fee10000 (reserved)
> <4> BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
> <5>2687MB HIGHMEM available.
> <5>896MB LOWMEM available.
> There is a big hole between 00000000dffff000 and 00000000fec00000, which
> is not used on the new machine. What can I do?

Presumably that was lost to ACPI. The hole between 0xdffff000 and
0xfec00000 appears to not be covered by the e820.

Try turning ACPI off in your .config since there's something that
looks relevant to it different between 2.4 and 2.5. You also might
want to follow up with .config's just in case. I'll look at 2.5's e820
stuff, but no promises.

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



This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:36 EST