Red Hat Bugzilla – Bug 605223
Inits kdump before asking whether to use it
Last modified: 2013-09-29 22:17:00 EDT
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
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.
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
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.