All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 101294] radeonsi minecraft forge splash freeze since 17.1
Date: Mon, 19 Jun 2017 15:12:35 +0000	[thread overview]
Message-ID: <bug-101294-502-grhTrNs3Ep@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101294-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 826 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101294

--- Comment #7 from Marek Olšák <maraeo@gmail.com> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1628 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-06-19 15:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-04  3:08 [Bug 101294] radeonsi minecraft forge splash freeze since 17.1 bugzilla-daemon
2017-06-05  2:36 ` bugzilla-daemon
2017-06-05  3:45 ` bugzilla-daemon
2017-06-05 18:18 ` bugzilla-daemon
2017-06-06  1:45 ` bugzilla-daemon
2017-06-18 15:47 ` bugzilla-daemon
2017-06-18 23:54 ` bugzilla-daemon
2017-06-18 23:54 ` bugzilla-daemon
2017-06-19 15:12 ` bugzilla-daemon [this message]
2017-06-19 15:15 ` bugzilla-daemon
2017-06-19 16:21 ` bugzilla-daemon
2017-06-19 18:13 ` bugzilla-daemon
2017-06-19 18:57 ` bugzilla-daemon
2017-06-19 19:34 ` bugzilla-daemon
2017-06-20 18:05 ` bugzilla-daemon
2017-07-11 22:23 ` bugzilla-daemon
2017-07-12  1:03 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-101294-502-grhTrNs3Ep@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.