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

["Luca Tettamanti" <kronos.it@gmail.com>]

On Mon, Sep 8, 2008 at 10:46 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Mon, Sep 8, 2008 at 1:00 PM, Luca Tettamanti <kronos.it@gmail.com> wrote:
>> On Mon, Sep 8, 2008 at 9:35 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>>> On Mon, Sep 8, 2008 at 12:14 PM, Luca Tettamanti <kronos.it@gmail.com> wrote:
>>>> On Mon, Sep 8, 2008 at 8:04 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>>>>> On Mon, Sep 8, 2008 at 10:54 AM, Luca Tettamanti <kronos.it@gmail.com> 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...
>>
>>  BIOS-provided physical RAM map:
>>  BIOS-e820: 0000000000000000 - 000000000009c800 (usable)
>>  BIOS-e820: 000000000009c800 - 00000000000a0000 (reserved)
>>  BIOS-e820: 00000000000e4000 - 0000000000100000 (reserved)
>>  BIOS-e820: 0000000000100000 - 00000000bbf90000 (usable)
>>  BIOS-e820: 00000000bbf90000 - 00000000bbf9e000 (ACPI data)
>>  BIOS-e820: 00000000bbf9e000 - 00000000bbfe0000 (ACPI NVS)
>>  BIOS-e820: 00000000bbfe0000 - 00000000bc000000 (reserved)
>>  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
>>  BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
>>  last_pfn = 0xbbf90 max_arch_pfn = 0x3ffffffff
>>
>> dmesg is attached, but I haven't rebooted yet.
>
> so some config works, others not?

Yes, that's correct, but it doesn't seem related to a particular
configuration item (moon phase maybe).
For example the kernel I'm using right now (-rc4-something) has the
same config as a non-working kernel minus LOCKDEP, but git-current
minus LOCKDEP does not work. On another kernel I got a working config
just enabling DEBUG_INFO, in another case I disabled MTD.

Luca