kexec is failing with kernel panic

Solution Unverified - Updated -


The kexec system call causes a booting process failure with an error similar to the following:

[    0.000000] Kernel panic - not syncing: ERROR: Failed to allocate 0x0000000000004000 bytes below 0x0000000020000000.
[    0.000000] 
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.18.0-128.el8.ppc64le #1
[    0.000000] Call Trace:
[    0.000000] [c00000000165fc70] [c000000000d1c06c] dump_stack+0xb0/0xf4 (unreliable)
[    0.000000] [c00000000165fcb0] [c0000000001432e4] panic+0x148/0x324
[    0.000000] [c00000000165fd50] [c0000000010e0484] memblock_alloc_base+0x44/0x58
[    0.000000] [c00000000165fdc0] [c0000000010aace8] alloc_stack+0x74/0xac
[    0.000000] [c00000000165fe30] [c0000000010ab650] emergency_stack_init+0xa8/0x18c
[    0.000000] [c00000000165fe90] [c0000000010aa8c4] setup_arch+0x38c/0x414
[    0.000000] [c00000000165ff00] [c0000000010a3c80] start_kernel+0x90/0x658

This problem usually happens on large configuration systems when the crashkernel parameter is passed to the kernel.


Red Hat Enterprise Linux 8.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content