lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 24 Aug 2008 10:43:59 +0200
From:	"Vegard Nossum" <>
To:	"Yinghai Lu" <>
Cc:	"Johannes Weiner" <>,
	"Linux Kernel Mailing List" <>
Subject: Re: 9a2d43b: __alloc_bootmem_core(): zero-sized request

On Sun, Aug 24, 2008 at 10:22 AM, Yinghai Lu <> wrote:
>> nr_kernel_pages = 13869392367443771392
>> 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:
> 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! :-)


"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
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists