All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91790] TONGA hang in amdgpu_ring_lock
Date: Fri, 28 Aug 2015 12:31:34 +0000	[thread overview]
Message-ID: <bug-91790-502-LMl3YWc3Ln@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91790-502@http.bugs.freedesktop.org/>


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

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

--- Comment #2 from Mathias Tillman <master.homer@gmail.com> ---
Created attachment 117967
  --> https://bugs.freedesktop.org/attachment.cgi?id=117967&action=edit
dmesg with added debug output

I've done some more testing, turns out that it never reaches
amdgpu_ring_unlock_commit on certain cases, and that's what causes it to hang,
since the mutex never unlocks.
I added some debug output to the code, gfx/sdma0 is ring->name, 0/9 is
ring->idx and the address is the address of the ring struct.
As you can see in the log, it calls amdgpu_ring_lock on ring 9 with name sdma0,
and then afterwards it calls it again on ring 0 with name gfx, without calling
amdgpu_ring_unlock_commit.
I will add some more debug output in hopes of finding why exactly it's never
unlocked, and if it is fixable. I should mention that these random lockups do
not happen while using the proprietary catalyst driver, so it must be something
in the amdgpu driver.

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

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

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

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

  parent reply	other threads:[~2015-08-28 12:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-28  8:49 [Bug 91790] TONGA hang in amdgpu_ring_lock bugzilla-daemon
2015-08-28 10:30 ` bugzilla-daemon
2015-08-28 12:31 ` bugzilla-daemon [this message]
2015-08-28 12:46 ` bugzilla-daemon
2015-08-28 12:54 ` bugzilla-daemon
2015-08-28 16:03 ` bugzilla-daemon
2015-08-28 16:07 ` bugzilla-daemon
2015-09-01 18:20 ` bugzilla-daemon
2015-09-01 19:58 ` bugzilla-daemon
2015-09-02  9:15 ` bugzilla-daemon
2015-09-02 20:09 ` bugzilla-daemon
2015-09-02 20:40 ` bugzilla-daemon
2015-09-03  8:56 ` bugzilla-daemon
2015-09-03 10:24 ` bugzilla-daemon
2015-09-03 11:34 ` bugzilla-daemon
2015-09-03 11:46 ` bugzilla-daemon
2019-11-19  8:06 ` 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-91790-502-LMl3YWc3Ln@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.