I suspect this is also true for RHEL6.
+++ This bug was initially created as a clone of Bug #522925 +++
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):
Steps to Reproduce:
1. setup kdump.
2. trigger kernel crash (echo c >/proc/sysrq-trigger) from X Window.
No indication of the kdump kernel in progress. Just a frozen X window.
Switch to console to show the kdump kernel is booting.
--- Additional comment from email@example.com on 2009-11-16 07:18:21 EST ---
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:
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
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.