Bug 690871 - Disabling kdump leads to unbootable system
Summary: Disabling kdump leads to unbootable system
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 16:33 UTC by Marcus Moeller
Modified: 2011-06-13 19:27 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-13 19:27:14 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Marcus Moeller 2011-03-25 16:33:08 UTC 
Description of problem:
Disabling kdump in firstboot leads to a system stucked on grub.

Version-Release number of selected component (if applicable):
RHEL 6.1 Beta

How reproducible:
Disable kdump during firstboot
System should reboot
System hangs during reboot
Forced shutdown leads to broken grub bootloader
Comment 2 Marcus Moeller 2011-03-28 07:10:01 UTC 
The problem does not only occur, after disabling kdump, but after firstboot in general.
Comment 3 Chris Lumens 2011-03-28 13:15:20 UTC 
What is the last thing you see on the screen when you reboot?  Please attach a picture if possible?
Comment 4 Marcus Moeller 2011-03-28 13:25:14 UTC 
It's the (frozen) Plymouth splash and I cannot switch to a virtual console anymore.
Comment 5 Chris Lumens 2011-03-28 13:46:06 UTC 
Well, can you disable plymouth to get some debugging information here?
Comment 6 RHEL Program Management 2011-04-04 02:50:35 UTC 
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Note You need to log in before you can comment on or make changes to this bug.