nathan.zook@amd.com wrote:
> I've dropped Linus off the direct list. I think we should be able to debug
> this one w/o his help. ;-)
>
> Lines 594-606 of setup.c, which is the old section cause problems with
> 0-length regions, now properly handles them. This must be some new problem.
>
> Could we have the e820 data out of /var/log/dmesg? head should work.
Jan 6 05:03:56 thefinal kernel: e820: 0009fc00 @ 00000000 (usable)
Jan 6 05:03:56 thefinal kernel: e820: 00000400 @ 0009fc00 (reserved)
Jan 6 05:03:56 thefinal kernel: e820: 00004000 @ 000e8000 (usable)
Jan 6 05:03:56 thefinal kernel: e820: 00010000 @ 000f0000 (reserved)
Jan 6 05:03:56 thefinal kernel: e820: 03ee0000 @ 00100000 (usable)
Jan 6 05:03:56 thefinal kernel: e820: 00010000 @ 03fe0000 (ACPI data)
Jan 6 05:03:56 thefinal kernel: e820: 00010000 @ 03ff0000 (reserved)
Jan 6 05:03:56 thefinal kernel: e820: 00016e00 @ 100a0000 (reserved)
Jan 6 05:03:56 thefinal kernel: e820: 00000200 @ 100b6e00 (ACPI NVS)
Jan 6 05:03:56 thefinal kernel: e820: 00049000 @ 100b7000 (reserved)
Jan 6 05:03:56 thefinal kernel: e820: 00080000 @ fff80000 (reserved)
The map looks plausible to me. How do I tell which page ranges the
kernel is using for memory allocation?
-- 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/
This archive was generated by hypermail 2b29 : Fri Jan 07 2000 - 21:00:06 EST