Bug 605223 - Inits kdump before asking whether to use it
Summary: Inits kdump before asking whether to use it
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kexec-tools (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
Target Milestone: rc
: ---
Assignee: Cong Wang
QA Contact: Red Hat Kernel QE team
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-17 13:10 UTC by Bastien Nocera
Modified: 2013-09-30 02:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-15 06:55:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Bastien Nocera 2010-06-17 13:10:24 UTC

1. Install RHEL6 snapshot
2. Boot first time
3. The spinner stops for a long while because kdump is generating a new ramdisk:
No kdump initial ramdisk found.^[[60G[^[[0;33mWARNING^[[0;39m]^M
Rebuilding /boot/initrd-2.6.32-33.el6.i686kdump.img
4. I get asked whether to enable kdump in firstboot...

kdump should *not* be enabled by default, especially when there is a question about whether to enable it in firstboot.

Comment 2 RHEL Product and Program Management 2010-06-17 13:33:55 UTC
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

Comment 3 Cong Wang 2010-07-05 09:18:17 UTC
We already discussed this in kdump meeting, the reason why we enable kdump before firstboot is that we want to avoid a reboot after the user disables it with firstboot. This is intended, not a bug.

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