View Issue Details

IDProjectCategoryView StatusLast Update
0005031CentOS-6kexec-toolspublic2012-07-05 07:48
ReporterBlueH2O 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Platformx86_64OSCentOSOS Version6.0
Product Version 
Target VersionFixed in Version 
Summary0005031: Kdump does not recognize crashkernel reserved memory
DescriptionKdump is failing to start with this error:

kdump: No crashkernel parameter specified for running kernel

However, the parameter was specified in grub but does not appear in /proc/cmdline:

# cat /etc/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=10
title CentOS (2.6.32-71.29.1.el6.x86_64)
    root (hd0,0)
    kernel /vmlinuz-2.6.32-71.29.1.el6.x86_64 ro root=UUID=21f56dd1-0de4-418b-bc87-ca8240ed4caa rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=auto vga=0x317
    initrd /initramfs-2.6.32-71.29.1.el6.x86_64.img

# cat /proc/cmdline
ro root=UUID=21f56dd1-0de4-418b-bc87-ca8240ed4caa rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us vga=0x317

Changing this from "auto" to "256M@16M" causes it to appear in /proc/cmdline:

# cat /proc/cmdline
ro root=UUID=21f56dd1-0de4-418b-bc87-ca8240ed4caa rd_NO_LUKS rd_NO_LVM rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us crashkernel=256M@16M vga=0x317

..but kdump still claims there was "No crashkernel parameter specified for running kernel." This is very broken.

Using kexec-tools-2.0.0-145.el6.x86_64 and kernel-2.6.32-71.29.1.el6.x86_64.
TagsNo tags attached.

Activities

BlueH2O

BlueH2O

2011-08-03 17:24

reporter   ~0013080

This should have been in category CentOS-6.
toracat

toracat

2011-08-03 21:32

manager   ~0013083

Changed to CentOS-6.
BlueH2O

BlueH2O

2012-01-30 19:23

reporter   ~0014370

It appears this is still broken in 6.2. I have in my GRUB configuration:

title CentOS (2.6.32-220.4.1.el6.x86_64)
        root (hd0,0)
        kernel /vmlinuz-2.6.32-220.4.1.el6.x86_64 ro root=UUID=2a58aa55-59d5-4f99-b3b9-0d1b5e2edd7f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
        initrd /initramfs-2.6.32-220.4.1.el6.x86_64.img

But messages reports:

Jan 30 12:16:20 lab174 kernel: Command line: ro root=UUID=2a58aa55-59d5-4f99-b3b9-0d1b5e2edd7f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM
Jan 30 12:16:20 lab174 kernel: crash memory driver: version 1.1
Jan 30 12:16:20 lab174 kdump: No crashkernel parameter specified for running kernel

/proc/cmdline has all of the above in it EXCEPT the crashkernel parameter.

kexec-tools-2.0.0-209.el6.x86_64
zhsxcn

zhsxcn

2012-03-06 07:22

reporter   ~0014618

Set 256M as crashkernel parameter instead of 256M@16M on CentOS 6.x.
Have fun!
BlueH2O

BlueH2O

2012-03-06 13:59

reporter   ~0014620

Read my notes again. It should work with "auto" but it does not.
BlueH2O

BlueH2O

2012-03-21 20:18

reporter   ~0014714

On a RHEL 6.2 box here, using "crashkernel=auto" results in ccrashkernel=129M@0M in /proc/cmdline. So this is working in RHEL but not in CentOS?
hsksyusk

hsksyusk

2012-07-05 07:48

reporter   ~0015368

"/usr/share/doc/kexec-tools-2.0.0/kexec-kdump-howto.txt" says ...

There is also a third specification for the crashkernel parameter:
crashkernel=auto
This specification allows the kernel to decide how much meory to reserve for the
purposes of kdump. It will make this determination based on the amount of
memory you have in your system, and scale the allocation accordingly. Note that
if you have less than 4Gb of memory in your system, this specification will opt
to not allocate any memory for the purposes of kdump.

Issue History

Date Modified Username Field Change
2011-08-03 16:48 BlueH2O New Issue
2011-08-03 17:24 BlueH2O Note Added: 0013080
2011-08-03 21:22 toracat Project CentOS-5 => CentOS-6
2011-08-03 21:32 toracat Note Added: 0013083
2012-01-30 19:23 BlueH2O Note Added: 0014370
2012-03-06 07:22 zhsxcn Note Added: 0014618
2012-03-06 13:59 BlueH2O Note Added: 0014620
2012-03-21 20:18 BlueH2O Note Added: 0014714
2012-07-05 07:48 hsksyusk Note Added: 0015368