Yes, I am using grub, the buggy bootloader. The relevant chunk of
kernal messages are:
BIOS-provided physical RAM map:
BIOS-e820: 000000000009f800 @ 0000000000000000 (usable)
BIOS-e820: 0000000000000800 @ 000000000009f800 (reserved)
BIOS-e820: 0000000000019800 @ 00000000000e6800 (reserved)
BIOS-e820: 0000000013ef0000 @ 0000000000100000 (usable)
BIOS-e820: 000000000000fc00 @ 0000000013ff0000 (ACPI data)
BIOS-e820: 0000000000000400 @ 0000000013fffc00 (ACPI NVS)
BIOS-e820: 0000000000080000 @ 00000000fff80000 (reserved)
On node 0 totalpages: 81904
zone(0): 4096 pages.
zone(1): 77808 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda1 mem=327616K
You are dead on, mem= seems a bit small. Forcing mem=320M on the
command line fixes the problem completely.
BIOS-provided physical RAM map:
BIOS-e820: 000000000009f800 @ 0000000000000000 (usable)
BIOS-e820: 0000000000000800 @ 000000000009f800 (reserved)
BIOS-e820: 0000000000019800 @ 00000000000e6800 (reserved)
BIOS-e820: 0000000013ef0000 @ 0000000000100000 (usable)
BIOS-e820: 000000000000fc00 @ 0000000013ff0000 (ACPI data)
BIOS-e820: 0000000000000400 @ 0000000013fffc00 (ACPI NVS)
BIOS-e820: 0000000000080000 @ 00000000fff80000 (reserved)
On node 0 totalpages: 81920
zone(0): 4096 pages.
zone(1): 77824 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda1 mem=320M
-
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/