Description of problem: Occasionally (a few times/day, perhaps) my screens go dark for ~1 second or so. When things come back, the pointer has been warped to the center of the screen. Version-Release number of selected component (if applicable): xorg-x11-drv-intel-2.14.0-3.fc16.x86_64 How reproducible: Happens regularly, but not on command Steps to Reproduce: 1. Work for a while, get seriously engrossed in a linux-kernel flamewar 2. Watch the world go black 3. Watch inflammatory response typing be directed into the wrong window due to the pointer movement Actual results: Distracting display blackouts Expected results: No distracting display blackouts Additional info: I have this in my log from the time of the last incident Mar 21 10:33:47 bike kernel: [775907.038955] i2c i2c-10: sendbytes: NAK bailout. Mar 21 10:33:47 bike kernel: [775907.165266] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 1 Mar 21 10:33:47 bike kernel: [775907.165271] [drm:drm_edid_block_valid] *ERROR* Raw EDID: Mar 21 10:33:47 bike kernel: [775907.165297] I have looked in the log other times and not found anything, though. Intel Q35 graphics.
Some digging suggests I'm not the only one seeing this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/712075
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.
Created attachment 486877 [details] dmesg output This is the dmesg output, as requested.
Created attachment 486880 [details] /var/log/messages Here is the messages file since boot. GDM sure does like to babble...
Created attachment 486881 [details] Xorg.0.log
This is off-topic, but just to note these warning from Xorg.0.log: [ 14.602] (WW) Option "xkb_variant" requires an string value [ 14.602] (WW) Option "XkbVariant" requires an string value [ 14.636] (WW) Option "xkb_variant" requires an string value [ 14.636] (WW) Option "XkbVariant" requires an string value [ 14.648] (WW) Option "xkb_variant" requires an string value [ 14.648] (WW) Option "XkbVariant" requires an string value [ 14.649] (WW) Option "xkb_variant" requires an string value [ 14.649] (WW) Option "XkbVariant" requires an string value Take a look at https://fedoraproject.org/wiki/Input_device_configuration for instructions how to do it. Back to our scheduled program now.
This looks interesting: Mar 22 12:05:51 bike kernel: [ 1488.018363] 00 Mar 22 12:05:51 bike kernel: [ 1488.085317] Mar 22 12:09:55 bike kernel: [ 1731.471005] render error detected, EIR: 0x00000010 Mar 22 12:09:55 bike kernel: [ 1731.471005] page table error Mar 22 12:09:55 bike kernel: [ 1731.471005] PGTBL_ER: 0x00000002 Mar 22 12:09:55 bike kernel: [ 1731.471005] [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x00000010, masking Mar 22 12:09:55 bike kernel: [ 1731.471624] render error detected, EIR: 0x00000010 Mar 22 12:09:55 bike kernel: [ 1731.471624] page table error Mar 22 12:09:55 bike kernel: [ 1731.471624] PGTBL_ER: 0x00000002 Mar 22 12:24:51 bike kernel: [ 2628.038820] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 197 Mar 22 12:24:51 bike kernel: [ 2628.038825] [drm:drm_edid_block_valid] *ERROR* Raw EDID: Mar 22 12:24:51 bike kernel: [ 2628.038849] Mar 22 12:43:51 bike kernel: [ 3768.038810] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 165 Mar 22 12:43:51 bike kernel: [ 3768.038814] [drm:drm_edid_block_valid] *ERROR* Raw EDID: Mar 22 12:43:51 bike kernel: [ 3768.038838] Mar 22 13:02:51 bike kernel: [ 4908.031734] i2c i2c-10: sendbytes: NAK bailout. Mar 22 13:02:52 bike kernel: [ 4908.186365] [drm:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 61 Mar 22 13:02:52 bike kernel: [ 4908.186376] [drm:drm_edid_block_valid] *ERROR* Raw EDID: Mar 22 13:02:52 bike kernel: [ 4908.186380] Mar 22 13:02:52 bike kernel: [ 4908.186402] Passing the bug to developers.
FWIW, I tried the workaround given on the launchpad bug page: echo 0 > /sys/module/drm_kms_helper/parameters/poll and I've not seen the behavior since. It's been almost 24 hours, so I'm becoming increasingly confident that things have really changed.
Hi there! I don't know if it's the same issue but my display get dark too and there's nothing i can do about it. I have to blindly ctrl+f2 and ctrl+alt+del to reset my dell vostro 1400. And i know how to securely reproduce it. Use note for some time and then suspend and resume. Then try to play a movie file, not in the browser, any file you have on your desktop. The screen goes dark. If i reset as described above I can watch the movie. $ lspci | grep -i graphics 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) $ rpm -qa | grep intel xorg-x11-drv-intel-2.14.0-4.fc15.i686 $ uname -a Linux padme 2.6.38.2-9.fc15.i686 #1 SMP Wed Mar 30 16:54:01 UTC 2011 i686 i686 i386 GNU/Linux Reseting now to get the log files.
Created attachment 490962 [details] Xorg.0.log
Created attachment 490963 [details] dmesg
Created attachment 490964 [details] messages
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.