SUSE Support

Here When You Need Us

kexec may fail with kernel panic when crashkernel parameter is passed

This document (7023981) is provided subject to the disclaimer at the end of this document.


SUSE Linux Enterprise Server 15 Service Pack 1 (SLES 15 SP1)


With kexec boot, system could fail to boot further with below error: 

  Kernel panic - not syncing: ERROR: Failed to allocate 0x0000000000004000 bytes below 0x0000000020000000. 

  CPU: 0 PID: 0 Comm: swapper Not tainted 4.12.14-135.gbb021ec-default #1 SLE15-SP1 (unreleased) 
  Call Trace: 
 [c00000000122fcf0] [c000000000a19368] dump_stack+0xb0/0xf0 (unreliable) 
 [c00000000122fd30] [c000000000a15efc] panic+0x144/0x31c 
 [c00000000122fdc0] [c000000000d3c8e4] memblock_alloc_base+0x44/0x58 

 This issue is seen on large configuration systems when "crashkernel=" parameter is passed to the kernel.


Working on a fix to ensure the memory available in first memory block (other than
what is used for KDump) is larger than 128MB. This change can have impact on
older configurations. While a fix that works for all cases is arrived at, 
use an offset greater than 128MB for crashkernel during kexec boot. For example:

  kexec -l --append="`cat /proc/cmdline` crashkernel=X@160M" --initrd=/boot/initrd-`uname -r` /boot/vmlinux-`uname -r` 

where X is the memory to be reserved for KDump.


System resources need memory to be reserved in the first memory block. While the
size of first memory block is usually 512MB or greater, memory for crashkernel is
reserved at an offset of 128MB by default. This leaves less than 128MB memory to
reserve for system resources that need memory in the first memory block. On large
configuration systems this memory may not be sifficient, especially with kexec
boot where initrd is also placed below 128MB adding to these memory constraints
and eventually leading to allocation failure.


This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7023981
  • Creation Date: 28-Jun-2019
  • Modified Date:03-Mar-2020
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.