Bug 852545

Summary: GPU hang with dual monitors on wakeup
Product: [Fedora] Fedora Reporter: jeremiah.mans
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: ajax, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-31 17:51:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description jeremiah.mans 2012-08-28 21:28:45 UTC 
Description of problem:

With kernel releases since 3.4.0 (roughly -- the exact version has been deleted from my machine now), when my system has a second monitor attached externally and the screens go to sleep, the system does not reliably wake back up and display.  Instead, commonly I get this error message in the dmesg:

[21477.876334] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[21477.876342] [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state
[21477.881551] [drm:kick_ring] *ERROR* Kicking stuck wait on render ring
[21483.985872] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[21486.481599] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[21486.481841] [drm:i915_reset] *ERROR* GPU hanging too fast, declaring wedged!
[21486.481845] [drm:i915_reset] *ERROR* Failed to reset chip.

I am using the Gnome 3 desktop

How reproducible:  75+% of the time
Comment 1 jeremiah.mans 2012-08-28 21:30:27 UTC 
I believe this bug is related to one discussed in the comments of:

https://bugzilla.redhat.com/show_bug.cgi?id=753050

though it is (probably) not the same primary bug.
Comment 2 Fedora End Of Life 2013-07-03 19:25:35 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2013-07-31 17:51:47 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.