Hide Forgot
I'm not sure what causes the issue, but I suspect that it's related to suspending and/or hibernate. Please see screenshot for the type of corruption, and my dmesg output. To me, the horizontal bands look like GPU memory management issues . . . like something in the framebuffer is getting scrambled, lost, or overwritten. Please let me know what I can do to help debug this. Thanks! Nick
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 505176 [details] dmesg output
Created attachment 505177 [details] /var/log/messages
Created attachment 505178 [details] Xorg.0.log
Created attachment 505179 [details] Xorg.9.log
Created attachment 505181 [details] Screenshot from the day before I reported this bug
Created attachment 505182 [details] screenshot which corrolates to the logs I attached today
Today I booted without rhgb and quiet. The screen corruption occurs after "restoring backlight state". Coloured horizontally banded lines flash on the screen during the switch from console to X. It's been a very long time since I saw a system do this . . . and that was during Xinit, years ago. I suspect that this bug is do to problems resulting from how hardware is reinitialized after hibernation. For example, the hardware state specified in my /etc/dbus/rules.d/10-trackpoint.rules is lost after hibernation, and I have to manually run "udevadm test /sys/devices/platform/i8042/serio1" to get my pre-hibernation speed and sensitivity settings back.
nope, it's not hibernation related. Unfortunately I didn't have drm.debug turned on, nor was I able to take a screenshot, but this bug triggered the hangcheck_ring_idle error again, according to dmesg. When I switched to the console to reboot from the completely unresponsive Gnome Shell, the screen stayed black, with no text, no matter what VC I switched to. This time, using the Gnome Shell overview mode, while coming out of suspend seemed to have triggered it. Could the compositor be triggering a framebuffer memory management bug? Because there was no fonts or even garbled text in the console, I wonder if this might be KMS-related too.
I guess I can confirm this bug too. From time to time, certain areas of the screen get corrupted, and usually scrolling past the corrupted area seems to "clean" it. I've noticed the following seemingly relevant lines on /var/log/messages: Jul 11 09:33:15 corp-gabriels kernel: [ 4746.960016] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Jul 11 09:33:15 corp-gabriels kernel: [ 4746.960109] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 723904 at 723896, next 723905) I'm also attaching two screenshots demoing the issue.
Created attachment 513253 [details] /var/log/messages
Created attachment 513254 [details] Corrupted volume bar display on Clementine
Created attachment 513255 [details] GNOME Shell top bar corrupted display
Created attachment 513256 [details] Corrupted Skype avatar display
By the way, my board is reported as "Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02)" by lspci.
Copying the driver files from the equivalent Ubuntu X.org Intel driver package seems to make the problem go away.
Oops, too soon. The problem persists, but apparently it's less evident with the Ubuntu-packaged driver.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping