From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Yinghai Lu" <yhlu.kernel@gmail.com>
Cc: "Johannes Weiner" <hannes@saeurebad.de>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 9a2d43b: __alloc_bootmem_core(): zero-sized request
Date: Sun, 24 Aug 2008 10:43:59 +0200 [thread overview]
Message-ID: <19f34abd0808240143y10b143c6s6f2b6753490d652f@mail.gmail.com> (raw)
In-Reply-To: <86802c440808240122r64ac91beu68e7782d5056bbb3@mail.gmail.com>
On Sun, Aug 24, 2008 at 10:22 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
>> 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/
>>
>
> seems something wrong about apic probe...
>
> MPTABLE: OEM ID: Intel Product ID: Lakeport Warning! May not
> be a NUMA-Q system!
It is not a NUMA-Q system, it's a normal desktop-class Pentium 4
machine with HT. But still, this kernel is expected to work, isn't it?
(At least expected to tell me "cannot boot" instead of giving
unexplainable errors.)
> MPTABLE: Product ID: Lakeport <6>MPTABLE: APIC at: 0xFEE00000
> Processor #0 15:6 APIC version 20 (quad 0, apic 1)
> Processor #0 (Bootup-CPU)
> Bus #0 is PCI (node 0)
> Bus #1 is PCI (node 0)
> Bus #2 is PCI (node 0)
> Bus #3 is ISA (node 0)
> I/O APIC #2 Version 32 at 0xFEC00000.
> Enabling APIC mode: NUMA-Q. Using 1 I/O APICs
>
>
> please check with tip/master to see if it is fixed already...
Yes, the v2.6.27-rc4 boots fine. I was wondering if you knew that this
problem had occurred in the past (and if so, which commits I can
cherry-pick to fix it). But I guess there is not much to do. It is
also hard to test this same config with newer kernels, because
something in the Kconfig changed in an incompatible way (e.g. NUMAQ
setting changes when I change kernel versions).
Unless anybody can think of something, I think I will leave this
problem alone. It's an older version after all. Thanks for looking at
it! :-)
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 8:44 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
2008-08-24 8:22 ` Yinghai Lu
2008-08-24 8:43 ` Vegard Nossum [this message]
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=19f34abd0808240143y10b143c6s6f2b6753490d652f@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®