Hi all, On Thu, 31 Jan 2019 16:38:54 +1100 Stephen Rothwell <[email protected]> wrote: > > [I am guessing that is is something in Andrew's tree that has caused > this.] > > My qemu boot of the powerpc pseries_le_defconfig config failed like this: > > htab_hash_mask = 0x1ffff > ----------------------------------------------------- > numa: NODE_DATA [mem 0x7ffe7000-0x7ffebfff] > Kernel panic - not syncing: sparse_buffer_init: Failed to allocate 2147483648 > bytes align=0x10000 nid=0 from=fffffffffffffff > CPU: 0 PID: 0 Comm: swapper Not tainted 5.0.0-rc4 #2 > Call Trace: > [c00000000105bbd0] [c000000000b1345c] dump_stack+0xb0/0xf4 (unreliable) > [c00000000105bc10] [c000000000111120] panic+0x168/0x3b8 > [c00000000105bcb0] [c000000000e701c8] sparse_init_nid+0x178/0x550 > [c00000000105bd70] [c000000000e709b4] sparse_init+0x210/0x238 > [c00000000105bdb0] [c000000000e468f4] initmem_init+0x1e0/0x260 > [c00000000105be80] [c000000000e3b9b0] setup_arch+0x354/0x3d4 > [c00000000105bef0] [c000000000e33afc] start_kernel+0x98/0x648 > [c00000000105bf90] [c00000000000b270] start_here_common+0x1c/0x52c
A quick bisect leads to this: 1c3c9328cde027eb875ba4692f0a5d66b0afe862 is the first bad commit commit 1c3c9328cde027eb875ba4692f0a5d66b0afe862 Author: Mike Rapoport <[email protected]> Date: Thu Jan 31 10:51:32 2019 +1100 treewide: add checks for the return value of memblock_alloc*() Add check for the return value of memblock_alloc*() functions and call panic() in case of error. The panic message repeats the one used by panicing memblock allocators with adjustment of parameters to include only relevant ones. The replacement was mostly automated with semantic patches like the one below with manual massaging of format strings. @@ expression ptr, size, align; @@ ptr = memblock_alloc(size, align); + if (!ptr) + panic("%s: Failed to allocate %lu bytes align=0x%lx\n", __func__, size, align); Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Mike Rapoport <[email protected]> Reviewed-by: Guo Ren <[email protected]> [c-sky] Acked-by: Paul Burton <[email protected]> [MIPS] Acked-by: Heiko Carstens <[email protected]> [s390] Reviewed-by: Juergen Gross <[email protected]> [Xen] Reviewed-by: Geert Uytterhoeven <[email protected]> [m68k] Cc: Catalin Marinas <[email protected]> Cc: Christophe Leroy <[email protected]> Cc: Christoph Hellwig <[email protected]> Cc: "David S. Miller" <[email protected]> Cc: Dennis Zhou <[email protected]> Cc: Greentime Hu <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Guan Xuetao <[email protected]> Cc: Guo Ren <[email protected]> Cc: Mark Salter <[email protected]> Cc: Matt Turner <[email protected]> Cc: Max Filippov <[email protected]> Cc: Michael Ellerman <[email protected]> Cc: Michal Simek <[email protected]> Cc: Petr Mladek <[email protected]> Cc: Richard Weinberger <[email protected]> Cc: Rich Felker <[email protected]> Cc: Rob Herring <[email protected]> Cc: Rob Herring <[email protected]> Cc: Russell King <[email protected]> Cc: Stafford Horne <[email protected]> Cc: Tony Luck <[email protected]> Cc: Vineet Gupta <[email protected]> Cc: Yoshinori Sato <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Which is just adding the panic we hit. So, presumably, the bug is in a preceding patch :-( I have left the kernel not booting for today. -- Cheers, Stephen Rothwell
pgpn5KkhEyCXq.pgp
Description: OpenPGP digital signature
