Description of problem: If the user supplies a KDUMP_COMMANDLINE in /etc/sysconfig/kdump with no "crashkernel=" option, then "service kdump start" will fail The KDUMP_COMMANDLINE is supposed to be passed only to the kdump kernel, it does not reflect the running primary boot kernel. Only the primary kernel needs "crashkernel=" set. And yet the /etc/rc.d/init.d/kdump script checks the kdump options, NOT the boot kernel options, for "crashkernel=" if this option is set. The problem is in function load_kdump() { if [ -z "$KDUMP_COMMANDLINE" ] then KDUMP_COMMANDLINE=`cat /proc/cmdline` fi MEM_RESERVED=`echo $KDUMP_COMMANDLINE | grep "crashkernel=[0-9]\+[MmKkGg]@[0-9]\+[MmGgKk]"` if [ -z "$MEM_RESERVED" ] then $LOGGER "No crashkernel parameter specified for running kernel" return 1 fi which selects the KDUMP_COMMANDLINE options before checking for crashkernel=. Version-Release number of selected component (if applicable): kexec-tools-1.101-177.el5, from CVS. How reproducible: 100% Steps to Reproduce: 1. Set a KDUMP_COMMANDLINE 2. "service kdump start" or reboot. Actual results: 'No crashkernel parameter specified for running kernel' Expected results: kdump should start Additional info: It is important to allow a KDUMP_COMMANDLINE with no crashkernel= option on it, as the command line length for the kdump kernel is quite limited and I already find that it overflows readily if I supply my usual kernel options on it.
Created attachment 157282 [details] patch to scan /proc/cmdline only for crashkernel parameter Yep, thanks for the catch stephen. This patch should fix it. I'll check it in as soon as this gets approved for 5.1
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
fixed in -178.el5. Thanks!
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2007-0548.html