Bug 522925 - No Indication of Kdump in Progress while in X Window
Summary: No Indication of Kdump in Progress while in X Window
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 524819 592506 810880 810881
TreeView+ depends on / blocked
Reported: 2009-09-12 08:47 UTC by Qian Cai
Modified: 2012-04-09 14:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 592506 810881 (view as bug list)
Last Closed: 2010-05-17 12:40:17 UTC
Type: ---

Attachments (Terms of Use)

Description Qian Cai 2009-09-12 08:47:42 UTC
Description of problem:
After setting up kdump, if the kernel crashes while the user is operating under X Window, there is no indication of the kdump kernel is in progress. The user would be confused to see if this is a kernel failure or frozen X window. Ideally, the display would switch to the console when the kdump kernel is booting. This problem happens with and without KMS.

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

How reproducible:

Steps to Reproduce:
1. setup kdump.
2. trigger kernel crash (echo c >/proc/sysrq-trigger) from X Window.
Actual results:
No indication of the kdump kernel in progress. Just a frozen X window.

Expected results:
Switch to console to show the kdump kernel is booting.

Comment 1 Bug Zapper 2009-11-16 12:18:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:

Comment 2 Neil Horman 2010-05-17 12:40:17 UTC
This has been a long standing problem, one which we just can't fix right now.  During a crash there is currently no safe way to return a video card to text mode so that the kdump boot process is visible, or to put up a banner indicating that a kdump is in progress.  The KMS changes make some of this more possible, but only on certain hardware, and under certain conditions.  Its simply to haphazzard a solution to truly be reasonable at this point.

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