[Bug 90183] GPU HANG: ecode 7:0:0x86dfbff9, in compiz [1938], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Jens <jens-bugs.freedesktop.org at spamfreemail.de> ---
To be quick (and to avoid any errors during compilation that I might introduce)
I tested the mainline kernels available from Ubuntu at
kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-nightly. Here are my results
so far.

2015-04-10-vivid: Boots fine and does S4 suspend/resume fine three times in a
row (so far) including restauration of X11 desktop. No load testing yet.

2015-05-11-vivid: Boots fine, S4 suspend works as well, after resume I get the
"GPU HANG" message with a backtrace. and X11 seems to restart (after ~10seconds
I get kicked back to the login screen). 

2015-04-14-vivid: Boots fine, S4 suspend works as well, after resume I get the
"GPU HANG" message with a backtrace. and X11 seems to restart (after ~10seconds
I get kicked back to the login screen).

2015-04-15-vivid: Boots fine, S4 suspend works as well, after resume I get the
"GPU HANG" message with a backtrace. and X11 seems to restart (after ~10seconds
I get kicked back to the login screen).

2015-04-21-vivid: Does not boot. Last message on console: "Ignoring BGRT:
Invalid status 0 (expected 1). But I think all the other kernels show this too
but it is replaced too quickly by the desktop.

2015-04-29-vivid: Does not boot cleanly - desktop does not appear, but I can
get to the text console. In syslog I get the "GPU HANG: ecode 7:2:0x00d7ffe9,
in Xorg" message, even without a S4 suspend. I saved the full dmesg output if
required. After a S4 suspend, the symptom is the same as in the 2015-04-21
kernel (does not boot).

2015-05-01-vivid: Boots fine, but when I do S4 suspend via 'pm-hibernate', the
machine seems to shut off but does not power down (all fans are quiet but the
power LED stays on). After a forced power cycle (4 seconds on power button)
there is a normal reboot. According to syslog the machine did not even try to
resume.


Does this help already? Or do I need to start bisecting between 2015-04-10 and
-11? Or test something else altogether?

Thank you for supporting!

-- 
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/20150501/e7eff034/attachment.html>