Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 592506 - No Indication of Kdump in Progress while in X Window
No Indication of Kdump in Progress while in X Window
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel (Show other bugs)
6.0
All Linux
medium Severity medium
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
:
Depends On: 522925 810881
Blocks: 524819 810880
  Show dependency treegraph
 
Reported: 2010-05-14 22:26 EDT by Qian Cai
Modified: 2012-04-09 10:21 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 522925
: 810880 (view as bug list)
Environment:
Last Closed: 2010-05-17 08:40:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Qian Cai 2010-05-14 22:26:47 EDT
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@redhat.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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 1 RHEL Product and Program Management 2010-05-14 22:45:06 EDT
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.
Comment 2 Neil Horman 2010-05-17 08:40:29 EDT
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.