RE: 2.3.20: e820 crash data

nathan.zook@amd.com
Thu, 14 Oct 1999 11:11:01 -0500

This may be related to the other notebook problem we're seeing, or it may
have to do with the "free" memory between 640k & 1M. It would be good if we
could see if /proc/iomem shows use of this "free" memory. Other than that
region, the whole thing looks pretty much like we might expect.

Nathan

-----Original Message-----
From: Jamie Lokier [mailto:lkd@tantalophile.demon.co.uk]
Sent: Thursday, October 14, 1999 10:08 AM
To: linux-kernel@vger.rutgers.edu
Subject: 2.3.20: e820 crash data

Ahem, that's 2.3.20 not 2.1.20:

2.3.20 crashes on my 64MB Toshiba 4070CDT immediately after booting.

I don't see much if the framebuffer device is on (blank screen). But if
it is off, the oops reveals there's a memory allocation problem.

With mem=63M, it boots fine. 2.3.18 was fine without this.

Here is the e820 map printed by the 2.3.20 kernel when it boots
successfully:

e820: 654336 @ 00000000 (usable)
e820: 1024 @ 0009fc00 (reserved)
e820: 16384 @ 000e8000 (usable)
e820: 65536 @ 000f0000 (reserved)
e820: 65929216 @ 00100000 (usable)
e820: 65536 @ 03fe0000 (ACPI data)
e820: 65536 @ 03ff0000 (reserved)
e820: 93696 @ 100a0000 (reserved)
e820: 512 @ 100b6e00 type 4
e820: 299008 @ 100b7000 (reserved)
e820: 524288 @ fff80000 (reserved)

enjoy,
-- Jamie

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

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