[Bug 58381] i915: GPU hangs after upgrade to 3.8.13 or 3.9

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Sep 6 10:12:49 PDT 2013


https://bugzilla.kernel.org/show_bug.cgi?id=58381

Mark E. <mk at cognitivedissonance.ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mk at cognitivedissonance.ca

--- Comment #20 from Mark E. <mk at cognitivedissonance.ca> ---
I was going to file a separate bug but this one seems quite similar.   I have
had the below problem with at least my last few kernels (3.9.6, 3.10.1),
previously with 3.2 or 3.6 it was fine.  I could verify the last working
version if asked, but the problem definitely started between 3.2 and 3.9; I
remember noticing this immediately after compiling the kernel but decided to
live with it.

There are three distinct but similar issues:

A) When coming back from hibernate or sleep, the screen is often (50/50)
screwed up, sometimes illegibly.  HID works, and moving the desktop around or
back and forth to console a few times usually clears it up.

B) Sometimes that does not work and a reboot is required, meaning (A) and (B)
differ only in severity.

C) Less often, the screen rapidly degrades, and HID response is very sluggish,
implying some wheels are spinning. Syslog/console will then contain:

[drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung
[drm] capturing error event; look for more information in
/sys/kernel/debug/dri/0/i915_error_stat

This error report distinguishes (C) from (A) and (B). I have checked i915_error
 immediately in situation (A) and (B) when it is still possible, but there is
no error there then. 

Within 60 seconds in situation (C) the system reboots itself. I've created a
shell shortcut to dump i915_error_state to disk with minimal keystrokes and
will report that here if anything comes out of it.

BTW: This problem occurs without chrome installed.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the intel-gfx-bugs mailing list