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.1.18 was fine without this.
Here is the e820 map printed by the 2.1.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/