[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0808240058h3d286151x18cba0939f175edd@mail.gmail.com>
Date: Sun, 24 Aug 2008 09:58:42 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Johannes Weiner" <hannes@...urebad.de>
Cc: "Yinghai Lu" <yhlu.kernel@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: 9a2d43b: __alloc_bootmem_core(): zero-sized request
On Sat, Aug 23, 2008 at 9:12 AM, Johannes Weiner <hannes@...urebad.de> wrote:
> "Vegard Nossum" <vegard.nossum@...il.com> writes:
>>
>> I was trying out
>>
>> commit 9a2d43b7566caeeeb414aa628bc2759028897dbb
>> Date: Tue Jul 15 21:21:43 2008 +0200
>>
>> ..as part of the debugging of a different issue, but I got this:
>>
>> __alloc_bootmem_core(): zero-sized request
[...]
>> I saw some bootmem errata lately, can I cherry-pick anything to fix
>> this?
>
> This behaviour hasn't changed after the rewrite.
Yep, the error is somewhere else.
Inserted a printk("nr_kernel_pages = %llu\n", nr_kernel_pages); and
this is the output:
nr_kernel_pages = 13869392367443771392
...it looks very, very big. I think this is initialized via
free_area_init_*() functions, which come from arch code. Does x86
experts know if any of this changed recently (i.e. after July 15)?
The whole dmesg and config can be seen here:
http://userweb.kernel.org/~vegard/bugs/20080824-numa/
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists