Bug 621456

Summary: anything that causes oops_in_progress to get set during resume breaks X server resume
Product: Red Hat Enterprise Linux 6 Reporter: Dave Airlie <airlied>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Red Hat Kernel QE team <kernel-qe>
Severity: medium Docs Contact:
Priority: low    
Version: 6.1   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-01-17 01:57:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Dave Airlie 2010-08-05 06:17:05 UTC
If lockdep displays a warning at any point in the system, this causes oops_in_progress to get set, this causes the VT/fbcon layer checks for when it is okay to write to fbcon to trigger.

On suspend/resume this causes fbcon to end up setting a mode when the resume scripts echo 0 to the fb0 state file, and it overwrites the current X mode causing us to end up with nothing on screen.

I'm unsure what the fix is yet, need to talk to upstream.

Comment 1 RHEL Program Management 2011-01-07 04:27:09 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.

Comment 2 Dave Airlie 2011-01-17 01:57:20 UTC
fix went in via backport from upstream prep patches.

*** This bug has been marked as a duplicate of bug 667281 ***