<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110848#c19">Comment # 19</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Everything using GPU gets stuck after running+killing parallel Media loads (after running 3D benchmarks)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=110848">bug 110848</a>
from <span class="vcard"><a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> <span class="fn">Chris Wilson</span></a>
</span></b>
<pre>The patch we identified as being problematic was reverted just before 5.2; tbf
I don't have a lot of confidence that was the only problematic patch in that
mm/ series.
e8f06c34fa..8991a80f85 does contain more fences, and so increased opportunity
for a missed wakeup. They would however be shown as processes stuck waiting for
a fence inside i915; whereas what your kernel stacks show are processes stuck
waiting for page io (if I read that correctly, generally from __dput).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>