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

On Mon, Sep 8, 2008 at 1:00 PM, Luca Tettamanti <kronos.it@xxxxxxxxx> wrote:
On Mon, Sep 8, 2008 at 9:35 PM, Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
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...

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?

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/

Relevant Pages

  • Re: [PATCH] x86: extend e820 ealy_res support 32bit - fix #2
    ... The kernel *cannot* assume it is safe to read. ... Now, to support using the E820 map for early reservations, we can simply define new "fake" E820 types. ... The easiest way to do that, is to pre-sanitize the map so that all unknown-type entries are collapsed into ...
    (Linux-Kernel)
  • Re: [2.6.27] overlapping early reservations [was: early exception - lockdep related?]
    ... can you post boot log with working kernel + "debug"? ... This is the map of the early reservations (will send the dmesg + debug later): ... same config as a non-working kernel minus LOCKDEP, ...
    (Linux-Kernel)
  • Re: USB regression (and other failures) in 2.6.2[45]*
    ... In my current testing kernel, which I believe is the one with which I ... captured the sole successful non-2.6.23.1 dmesg so far, ... then none of your USB devices would be able to run at high speed. ... That would require me to learn enough of how git works, ...
    (Linux-Kernel)
  • Re: Two FC7 questions
    ... or to never remove an old kernel. ... display for the motor home. ... map so the direction your moving is up, ... I have used roadnav with a smaller display when when using a GPS, ...
    (Fedora)
  • Re: [crash] Re: Latest brk patchset
    ... leaves the space under the kernel avaliable for allocating pagetable ... make sure we map enough to fit linear map pagetables ... that mm/init.c can allocate space from the e820 allocator ... for the linear map of low memory. ...
    (Linux-Kernel)