<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [bdw] GPU HANG on resuming"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89308#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [bdw] GPU HANG on resuming"
href="https://bugs.freedesktop.org/show_bug.cgi?id=89308">bug 89308</a>
from <span class="vcard"><a class="email" href="mailto:alienth@gmail.com" title="Jason Harvey <alienth@gmail.com>"> <span class="fn">Jason Harvey</span></a>
</span></b>
<pre>Upgraded kernel again, this time to the intel-drm-next tag on 3.18:
$ uname -a
Linux artoo 3.18.0-997-generic #201412200341 SMP Sat Dec 20 03:42:55 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Issue still occurs after resume from suspend:
$ dmesg
[32420.465811] [drm] stuck on render ring
[32420.466721] [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [1537], reason:
Rin
g hung, action: reset
[32420.466722] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
sta
ck, including userspace.
[32420.466722] [drm] Please file a _new_ bug report on bugs.freedesktop.org
agai
nst DRI -> DRM/Intel
[32420.466723] [drm] drm/i915 developers can then reassign to the right
componen
t if it's not a kernel issue.
[32420.466724] [drm] The gpu crash dump is required to analyze gpu hangs, so
ple
ase always attach it.
[32420.466724] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[32420.473835] drm/i915: Resetting chip after gpu hang</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>