<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456#c25">Comment # 25</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - userptr deadlock in Vulkan CTS: mmu_notifier vs workers vs struct_mutex"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108456">bug 108456</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>(In reply to Tvrtko Ursulin from <a href="show_bug.cgi?id=108456#c24">comment #24</a>)
<span class="quote">> CI_DRM_5255 or newer runs contain the fix.
>
> Note that this is not fixing the userptr problem, just the system hang after
> GPU hang which should enable more comfortable testing of Chris' proposed
> userptr fixes.</span >
Also note that mesa kbl hangs were quite capable of locking up the system
before v4.18... To fully protect ourselves we have to prevent any of the
incremental mesa batches from continuing to execute after a hang, as the
context contains none of the register settings or accrued GPU state that the
batches depend upon.</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>
</ul>
</body>
</html>