<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi minecraft forge splash freeze since 17.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101294#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - radeonsi minecraft forge splash freeze since 17.1"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101294">bug 101294</a>
from <span class="vcard"><a class="email" href="mailto:maraeo@gmail.com" title="Marek Olšák <maraeo@gmail.com>"> <span class="fn">Marek Olšák</span></a>
</span></b>
<pre>The bisected commit only uncovers the existing deadlock scenario.
Summary of the issue.
amdgpu_bo_create
-> pb_cache_reclaim_buffer (lock pb_cache::mutex)
-> pb_cache_is_buffer_compat
-> amdgpu_bo_wait (lock bo_fence_lock) - DEADLOCK
pb_reference
-> pb_destroy
-> amdgpu_bo_destroy_or_cache
-> pb_cache_add_buffer (lock::pb_cache::mutex) - DEADLOCK
amdgpu_cs_flush (lock bo_fence_lock)
-> amdgpu_add_fence_dependency (loop-wait for submission_in_progress) -
DEADLOCK
It looks the best way to prevent this deadlock is to unify pb_cache::mutex and
bo_fence_lock under one lock, that is, one of them has to go.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>