Bug 589937 - kdump is enabled by default but not configured
kdump is enabled by default but not configured
Status: CLOSED DUPLICATE of bug 581422
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kexec-tools (Show other bugs)
6.0
All Linux
low Severity medium
: rc
: ---
Assigned To: Neil Horman
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-07 06:55 EDT by Stefan Assmann
Modified: 2010-05-07 12:35 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-05-07 12:35:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stefan Assmann 2010-05-07 06:55:27 EDT
Description of problem:
kdump seems to be enabled by default in RHEL6. After the installation I see the following in the boot messages:
no kdump initial ramdisk found. [WARNING]
Rebuilding /boot/initrd-2.6.32-23.el6.x86_64kdump.img
Starting kdump: [FAILED]

However kdump isn't even configured properly. There's no kernel commandline parameter specified. Starting system-config-kdump also failed with "This system does not have enough memory for kdump to be viable."

System has 512MB, shouldn't that be enough to run kdump?

Version-Release number of selected component (if applicable):
kexec-tools-2.0.0-68.el6.x86_64
system-config-kdump-2.0.2.1-11.el6.noarch

How reproducible:
always
Comment 2 RHEL Product and Program Management 2010-05-07 08:58:30 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Neil Horman 2010-05-07 12:35:39 EDT

*** This bug has been marked as a duplicate of bug 581422 ***

Note You need to log in before you can comment on or make changes to this bug.