From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 101294] radeonsi minecraft forge splash freeze since 17.1 Date: Mon, 19 Jun 2017 15:12:35 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1245560252==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 801346E1C4 for ; Mon, 19 Jun 2017 15:12:35 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1245560252== Content-Type: multipart/alternative; boundary="14978851550.c0a7.27269"; charset="UTF-8" --14978851550.c0a7.27269 Date: Mon, 19 Jun 2017 15:12:35 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D101294 --- Comment #7 from Marek Ol=C5=A1=C3=A1k --- 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. --=20 You are receiving this mail because: You are the assignee for the bug.= --14978851550.c0a7.27269 Date: Mon, 19 Jun 2017 15:12:35 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 7 on bug 10129= 4 from Marek Ol=C5=A1=C3=A1k 
The bisected commit only uncovers the existing deadlock scenar=
io.

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.

You are receiving this mail because:
  • You are the assignee for the bug.
= --14978851550.c0a7.27269-- --===============1245560252== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1245560252==--