From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Johannes Weiner" <hannes@saeurebad.de>
Cc: "Yinghai Lu" <yhlu.kernel@gmail.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 9a2d43b: __alloc_bootmem_core(): zero-sized request
Date: Sun, 24 Aug 2008 09:58:42 +0200 [thread overview]
Message-ID: <19f34abd0808240058h3d286151x18cba0939f175edd@mail.gmail.com> (raw)
In-Reply-To: <87myj4yzll.fsf@skyscraper.fehenstaub.lan>
On Sat, Aug 23, 2008 at 9:12 AM, Johannes Weiner <hannes@saeurebad.de> wrote:
> "Vegard Nossum" <vegard.nossum@gmail.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
next prev parent reply other threads:[~2008-08-24 7:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 19:24 Vegard Nossum
2008-08-22 19:54 ` Vegard Nossum
2008-08-23 7:12 ` Johannes Weiner
2008-08-24 7:58 ` Vegard Nossum [this message]
2008-08-24 8:22 ` Yinghai Lu
2008-08-24 8:43 ` Vegard Nossum
2008-08-24 8:58 ` Yinghai Lu
2008-08-24 8:23 ` Vegard Nossum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=19f34abd0808240058h3d286151x18cba0939f175edd@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®