Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?]

From: Yinghai Lu
Date: Mon Sep 08 2008 - 15:36:03 EST


On Mon, Sep 8, 2008 at 12:14 PM, Luca Tettamanti <kronos.it@xxxxxxxxx> wrote:
> On Mon, Sep 8, 2008 at 8:04 PM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
>> On Mon, Sep 8, 2008 at 10:54 AM, Luca Tettamanti <kronos.it@xxxxxxxxx> wrote:
>>
>> can you post boot log with working kernel + "debug"?
>
> This is the map of the early reservations (will send the dmesg + debug later):
>
> [ 0.000000] (6 early reservations) ==> bootmem [0000000000 - 00bbf90000]
> [ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==>
> [0000000000 - 0000001000]
> [ 0.000000] #1 [0000006000 - 0000008000] TRAMPOLINE ==>
> [0000006000 - 0000008000]
> [ 0.000000] #2 [0000200000 - 0000d012b8] TEXT DATA BSS ==>
> [0000200000 - 0000d012b8]
> [ 0.000000] #3 [00037dc000 - 00040fe2d9] RAMDISK ==>
> [00037dc000 - 00040fe2d9]
> [ 0.000000] #4 [000009c800 - 0000100000] BIOS reserved ==>
> [000009c800 - 0000100000]
> [ 0.000000] #5 [0000008000 - 000000b000] PGTABLE ==>
> [0000008000 - 000000b000]
>
> As a side note: I've bigger older (2.6.26) kernels that boots fine,
> and smaller 2.6.27 kernels that do not work, e.g. this one:

that could explain sth. big kernel use more, and lilo put ramdisk
high from 0x37dc000

>
> Overlapping early reservations b71000-effb43 RAMDISK to 200000-c84ecf
> TEXT DATA BSS

need to figure out, lilo put ramdisk so low...

need to know e820 table layout...

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