RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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):
kernel-2.6.31-2.fc12.x86_64
xorg-x11-drv-ati-6.12.2-19.fc12.x86_64

How reproducible:
always

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.

--- Additional comment from fedora-triage-list 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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

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
inclusion.

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.