Bug 717210 - Screen blanking out for a few seconds randomly on i915 graphics
Screen blanking out for a few seconds randomly on i915 graphics
Status: CLOSED CURRENTRELEASE
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel (Show other bugs)
15
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Adam Jackson
Fedora Extras Quality Assurance
[cat:modesetting]
:
Depends On: 695034
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-28 07:32 EDT by Stephen Gallagher
Modified: 2011-10-11 15:50 EDT (History)
7 users (show)

See Also:
Fixed In Version: kernel-2.6.40.6-0.fc15.x86_64
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-10-11 15:50:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Stephen Gallagher 2011-06-28 07:32:19 EDT
Description of problem:
At random times (usually when changing workspaces in gnome-shell) the screen will blank out and become unresponsive for several seconds. I see an error message appear in /var/log/messages (see Additional info) when this happens.

Version-Release number of selected component (if applicable):
kernel-2.6.38.8-34.fc15.x86_64

I am using this kernel to test a fix for the related bz#695034

How reproducible:
Inconsistent. This happens randomly.


Steps to Reproduce:
Unsure, seems to happen most often while changing workspaces in gnome-shell, but sometimes it just happens on its own while I'm not touching the keyboard or mouse.
  
Actual results:
Screen blanks out and system becomes unresponsive for several seconds.

Expected results:
Uninterrupted activity.

Additional info:

From /var/log/messages
Jun 28 07:24:46 sgallagh520 kernel: [ 2195.100586] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Jun 28 07:24:46 sgallagh520 kernel: [ 2195.111813] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 602503 at 602500, next 602504)
Jun 28 07:24:46 sgallagh520 kernel: [ 2195.115203] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000
Jun 28 07:24:46 sgallagh520 kernel: [ 2195.118349] [drm:init_ring_common] *ERROR* gen6 bsd ring initialization failed ctl 00000000 head 00000000 tail 00000000 start 00000000
Jun 28 07:24:46 sgallagh520 kernel: [ 2195.139871] [drm:init_ring_common] *ERROR* blt ring initialization failed ctl 0001f003 head 00000000 tail 00000000 start 00000000
Jun 28 07:24:52 sgallagh520 kernel: [ 2201.416913] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Jun 28 07:24:52 sgallagh520 kernel: [ 2201.416989] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -11 (awaiting 602505 at 602501, next 602506)
Comment 1 Josh Boyer 2011-10-11 11:57:07 EDT
Is this still happening with the 2.6.40.6 kernel update?
Comment 2 Matěj Cepl 2011-10-11 12:13:54 EDT
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*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.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.
Comment 3 Stephen Gallagher 2011-10-11 12:35:37 EDT
I have not seen this issue in some time. I'm not sure when exactly it stopped happening.

I am currently running kernel-2.6.40.6-0.fc15.x86_64
Comment 4 Matěj Cepl 2011-10-11 15:50:49 EDT
Thank you for letting us know.

Note You need to log in before you can comment on or make changes to this bug.