From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111763] ring_gfx hangs/freezes on Navi gpus
Date: Wed, 13 Nov 2019 00:04:37 +0000 [thread overview]
Message-ID: <bug-111763-502-9FzTo4QGLL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #37 from Andrew Sheldon <asheldon55@gmail.com> ---
(In reply to Daniel Suarez from comment #33)
> That workaround delays the hangs af best, and I have gotten hangs from
> OpenGl Games and also by using amdvlk.
>
Those hangs shouldn't be SDMA related, however. If you are getting hangs from
specific games, report them on the corresponding bug tracker
(https://gitlab.freedesktop.org/mesa/mesa for OGL and RADV,
https://github.com/GPUOpen-Drivers/AMDVLK/issues for AMDVLK).
I suggest using RADV_PERFTEST=aco with mesa-git for the most stable Vulkan
experience (or try the AMDGPU-PRO Vulkan driver).
There's also the "divide error" random hang issue, but it shouldn't be related
to SDMA either.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1827 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-11-13 0:04 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-22 12:01 [Bug 111763] ring_gfx hangs/freezes on Navi gpus bugzilla-daemon
2019-09-23 2:46 ` bugzilla-daemon
2019-09-23 6:56 ` bugzilla-daemon
2019-09-23 6:57 ` bugzilla-daemon
2019-09-23 7:00 ` bugzilla-daemon
2019-09-30 12:18 ` bugzilla-daemon
2019-09-30 15:10 ` bugzilla-daemon
2019-09-30 21:55 ` bugzilla-daemon
2019-09-30 22:02 ` bugzilla-daemon
2019-10-03 12:26 ` bugzilla-daemon
2019-10-11 13:37 ` bugzilla-daemon
2019-10-11 13:57 ` bugzilla-daemon
2019-10-15 12:58 ` bugzilla-daemon
2019-10-15 17:10 ` bugzilla-daemon
2019-10-23 7:26 ` bugzilla-daemon
2019-10-31 12:09 ` bugzilla-daemon
2019-10-31 12:11 ` bugzilla-daemon
2019-11-01 1:23 ` bugzilla-daemon
2019-11-01 16:26 ` bugzilla-daemon
2019-11-02 12:35 ` bugzilla-daemon
2019-11-02 23:11 ` bugzilla-daemon
2019-11-04 16:08 ` bugzilla-daemon
2019-11-04 16:10 ` bugzilla-daemon
2019-11-04 22:13 ` bugzilla-daemon
2019-11-05 6:07 ` bugzilla-daemon
2019-11-05 16:28 ` bugzilla-daemon
2019-11-09 2:54 ` bugzilla-daemon
2019-11-09 12:42 ` bugzilla-daemon
2019-11-09 20:12 ` bugzilla-daemon
2019-11-10 12:20 ` bugzilla-daemon
2019-11-10 13:50 ` bugzilla-daemon
2019-11-10 13:51 ` bugzilla-daemon
2019-11-10 13:53 ` bugzilla-daemon
2019-11-10 13:55 ` bugzilla-daemon
2019-11-10 13:58 ` bugzilla-daemon
2019-11-10 14:00 ` bugzilla-daemon
2019-11-10 14:04 ` bugzilla-daemon
2019-11-12 23:15 ` bugzilla-daemon
2019-11-13 0:04 ` bugzilla-daemon [this message]
2019-11-19 9:52 ` 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-111763-502-9FzTo4QGLL@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox