kdump fails to initialise with `crashkernel=1024M@16M` on some RHEL5 kernels

Solution Unverified - Updated

Environment

  • Red Hat Enterprise Linux 5
  • kdump/kexec configured to capture vmcore
  • Large memory system
  • Large kdump crashkernel offset

Issue

On some RHEL5 kernels since RHEL5.5, attempting to use settings of crashkernel=1024M@16M in grub.conf to initialise kdump fails with:

crashkernel reservation failed - memory is in use  
crashkernel reservation failed - memory is in use

However lower values like crashkernel=512M@16M will work fine.

Resolution

  • This issue was resolved under errata RHSA-2011-1065.
    Please update to kernel-2.6.18-274.el5 or later.

Root Cause

This issue was tracked under Red Hat Private Bug This content is not included.662102.

SBR
Product(s)
Components
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.