[lkml]   [2019]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: linux-next: powerpc le qemu boot failure after merge of the akpm tree
Hi all,

On Thu, 31 Jan 2019 16:38:54 +1100 Stephen Rothwell <> 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 <>
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);

Signed-off-by: Mike Rapoport <>
Reviewed-by: Guo Ren <> [c-sky]
Acked-by: Paul Burton <> [MIPS]
Acked-by: Heiko Carstens <> [s390]
Reviewed-by: Juergen Gross <> [Xen]
Reviewed-by: Geert Uytterhoeven <> [m68k]
Cc: Catalin Marinas <>
Cc: Christophe Leroy <>
Cc: Christoph Hellwig <>
Cc: "David S. Miller" <>
Cc: Dennis Zhou <>
Cc: Greentime Hu <>
Cc: Greg Kroah-Hartman <>
Cc: Guan Xuetao <>
Cc: Guo Ren <>
Cc: Mark Salter <>
Cc: Matt Turner <>
Cc: Max Filippov <>
Cc: Michael Ellerman <>
Cc: Michal Simek <>
Cc: Petr Mladek <>
Cc: Richard Weinberger <>
Cc: Rich Felker <>
Cc: Rob Herring <>
Cc: Rob Herring <>
Cc: Russell King <>
Cc: Stafford Horne <>
Cc: Tony Luck <>
Cc: Vineet Gupta <>
Cc: Yoshinori Sato <>
Signed-off-by: Andrew Morton <>

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.
Stephen Rothwell
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2019-01-31 07:07    [W:0.064 / U:23.908 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site