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

[bugzilla-daemon at bugzilla.kernel.org]

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

--- Comment #21 from Daniel Vetter <daniel at ffwll.ch> ---
(In reply to Mark E. from comment #20)
> 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.

A) and B) are very likely the same bug, but also very likely completely
unrelated to issue C).

For issue C) we can't tell what's wrong without the error state. But please
file a new bug report - for us it's much easier to mark a bug as duplicate
after analysis than trying to untangle different bugs reported in the same
bugzilla.

For issue A/B please also file a new (separate) bug report. For that one we
need dmesg with drm.debug=0xe added to the kernel cmdline (you might need to
increase the dmesg buffer or grab dmesg for disk logs, there's lots of stuff).
We need everything from the boot-up message to when you've hit the black screen
issue after resume.

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