Red Hat Bugzilla – Bug 244649
kdump init scripts don't work if user supplies KDUMP_COMMANDLINE
Last modified: 2007-11-30 17:07:44 EST
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
if [ -z "$KDUMP_COMMANDLINE" ]
MEM_RESERVED=`echo $KDUMP_COMMANDLINE | grep
if [ -z "$MEM_RESERVED" ]
$LOGGER "No crashkernel parameter specified for running kernel"
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.
Steps to Reproduce:
1. Set a KDUMP_COMMANDLINE
2. "service kdump start" or reboot.
'No crashkernel parameter specified for running kernel'
kdump should start
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
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.