<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [snb] TearFree now triggers stuck semaphores (due to Eliminate the synchronous wait from inside TearFree)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70764#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [snb] TearFree now triggers stuck semaphores (due to Eliminate the synchronous wait from inside TearFree)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=70764">bug 70764</a>
from <span class="vcard"><a class="email" href="mailto:francisbrwn9@gmail.com" title="FBrown <francisbrwn9@gmail.com>"> <span class="fn">FBrown</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=88007" name="attach_88007" title="crash log on drm-intel-nightly">attachment 88007</a> <a href="attachment.cgi?id=88007&action=edit" title="crash log on drm-intel-nightly">[details]</a></span>
crash log on drm-intel-nightly
OK. Following.
[drm] stuck on render ring
[ 610.496014] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 610.496015] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 610.496015] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 610.496016] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 610.496016] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
crash dump is attached</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>