[Bug 91976] GPU HANG: ecode 4:1:0x01000000, reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=91976

Manuel Krause <manuelkrause at netscape.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |manuelkrause at netscape.net

--- Comment #1 from Manuel Krause <manuelkrause at netscape.net> ---
Created attachment 120181
  --> https://bugs.freedesktop.org/attachment.cgi?id=120181&action=edit
dmesg log of a similar GPU hang

It's taken long time for me to find this BUG. For months I've been searching to
find reasons and solutions for my resumes from hibernation (suspend-to-disk)
sometimes fail and sometimes not. 

Currently I'm using kernel 4.3.0 (vanilla from openSUSE) + the actual vrq patch
from Alfred Chen, the TuxOnIce patch and the BFQ disk scheduler patches v7r8.
As I already annoyed others with the annoying unreliability to always resume
properly (sometimes 25+ attempts needed to get the written image back working,
but sometimes the first one comes up well, in one row of hibernations without
reboot), I decided to compile the i915 into the kernel, yesterday. One problem
with the TuxOnIce resume attempts failing: I never got any failure messages.
Either it worked or the machine locked up at "Doing atomic copy/restore." --
where there seems to occur a mode switch in the working case (module version).

With the compiled-in i915 I do at least get some messages about what's maybe
going on. And... I'm a bit lucky to have done this, as the needed GPU resets
seem to make resuming more relyable on here.

This is a HP Compaq 6730b laptop running openSUSE 13.1, but with actualized
drivers. For Xorg, Mesa and GFX related .rpms I use pontostroy's repository.

Here I attach the dmesg log of a series of resumes from hibernation.

In the next attachment I'd add the /sys/class/drm/card0/error crash dump.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20151127/4f08d3bc/attachment.html>