From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111763] ring_gfx hangs/freezes on Navi gpus
Date: Mon, 30 Sep 2019 15:10:38 +0000 [thread overview]
Message-ID: <bug-111763-502-iRMFHbmZ9p@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1048 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #6 from Marko Popovic <popovic.marko@protonmail.com> ---
(In reply to Doug Ty from comment #5)
> I've been getting this too with Minecraft:
> https://bugs.freedesktop.org/show_bug.cgi?id=111669
>
> For my particular case at least, AMD_DEBUG=nodma seems to fix it
(In reply to Marko Popovic from comment #0)
> There is another type of freeze/hang happening when playing Starcraft II via
> D9VK. This one doesn't seem to be related to either ngg or dma because I
> have them both disabled by AMD_DEBUG=nodma and AMD_DEBUG=nongg and the hangs
> occur anyway, on exactly the same place every time.
You are refering to sdma0 / sdma1 type hang which is tracked
here:https://bugs.freedesktop.org/show_bug.cgi?id=111481
For ring_gfx hangs they're quite more reproducible and are not affected by
AMD_DEBUG=nodma or AMD_DEBUG=nongg which I already mentioned above in the bug
description.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2332 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-09-30 15:10 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 [this message]
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
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-iRMFHbmZ9p@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.