Bug 1043723

Created attachment 837517 [details]
picture of screen

Attached is an picture of the screen when this happens.

I'm experiencing this, and other graphics problems on same Haswell chip.

This seems to be because Fedora is currently on xorg-x11-drv-intel version 2.21.15. A number of Haswell issues have been fixed upstream, and the current version is 2.99.906.

I have confirmed I don't have the suspend/resume problem on another distro that is using the 2.99.906 release and I'm working on trying to get that version on Fedora 20 to test.

For what it's worth, I'm experiencing essentially the same problem with an i7-4770K which has Intel HD Graphics 4600. Will attach a photo as well.

# lspci|grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

# rpm -qa|grep intel
xorg-x11-drv-intel-2.21.15-5.fc20.x86_64

Created attachment 861650 [details]
Photo of the screen corruption

From my perspective, I don't think that this bug is valid anymore, at least not as I originally reported it.

I'm using xorg-x11-drv-intel-2.21.15-7.fc20.x86_64 and not seeing anything wrong. I see that several other people have added themselves to this bug, is there still a problem?

Hi,
I too am currently using xorg-x11-drv-intel-2.21.15-7.fc20.x86_64 but the bug persists. As it's persisted for several months, I can elaborate a bit on the symptoms.

Upon resume from DPMS sleep, the screen is garbled with fragments of old display bits. It's often "mostly black" as in the two screenshots above. More frequently it's partly black and partly composed of an irregular assortment of fragments of icons/menus/webpages/etc -- bits of whatever GUIs that are in or have been in recent use.

Very infrequently it shows an outdated screenshot of something I'd been working on previously. For example, if I edit a document in LibreOffice, and then save the document and exit LibreOffice, a later DPMS resume might show a screen that includes the LibreOffice GUI and my document.

A reliable way to "fix" it is to click on a taskbar button, which triggers a screen redraw/refresh, and all is well until the next DPMS resume.

I'm not a kernel/driver hacker, but my guess is that upon DPMS resume, it redraws the screen sourced from the wrong block of memory---possibly even an arbitrary block of memory. That would explain the random fragments of old screen updates that it's getting---as various GUI bits get allocated/freed, it leaves GUI bits strewn about in memory, and an arbitrary chunk will likely contain some of them.

I'm still having the issue as well, using the same driver version and an HD 4400.   As with the others, triggering a screen refresh (in my case, triggering Expo in Cinnamon) "fixes" the problem (until the next DPMS off).

HD 4600 here, according to Xorg log. Only seems to happen with a secondary display connected (on HDMI). It's particularly bothersome with the KDE lock screen, which seems to never do a full refresh so you have to enter your password blind.

Hi,
Motivated by Eric's comment above, two days ago I installed 

  xorg-x11-drv-intel-2.99.911-20.intel20142.x86_64

from Intel's intellinuxgraphics repo, and since then, resuming from DPMS suspend is no longer garbled.

Is it possible to get the 2.99.911 version into Fedora's repo?

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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