From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111763] ring_gfx hangs/freezes on Navi gpus
Date: Sun, 10 Nov 2019 13:58:51 +0000 [thread overview]
Message-ID: <bug-111763-502-UZpyb6YV2b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-111763-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #33 from Daniel Suarez <danielsuarez369@protonmail.com> ---
(In reply to Marko Popovic from comment #32)
> (In reply to Daniel Suarez from comment #31)
> > (In reply to Marko Popovic from comment #30)
> > > (In reply to Daniel Suarez from comment #29)
> > > > (In reply to Marko Popovic from comment #28)
> > > > > I think this bug report can be closed now, Mesa 20 git basically fixes radv
> > > > > related ring_gfx hangs, there is still hang that happens in Citra emulator
> > > > > (ngg related) but AMD developers are aware of it so will probably get fixed
> > > > > too.
> > > >
> > > > Yeah.. "soon". Still waiting for them to fix bug 111481
> > >
> > > SDMA hangs have nothing to do with ring_gfx hangs which were mostly radv
> > > related and are fixed now
> >
> > Still, I can't even play Vulkan titles reliably because the system
> > constantly hangs even with the workarounds in the bug report. AMD really
> > needs to fix them.
>
> Mesa 20.0 should fix Vulkan hangs for you, and with nodma SDMA is disabled
> fully so you can't get any hangs that are SDMA related.
That workaround delays the hangs af best, and I have gotten hangs from OpenGl
Games and also by using amdvlk.
Don't get me wrong I'm not saying this bug report shouldn't be closed, I'm just
saying that you saying "soon" is very misleading. AMD hasn't still properly
fixed bugs that lead to hangs by just watching Firefox, and it's been MONTHS.
"soon" for them is months apperantly
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3046 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-10 13:58 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 [this message]
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-UZpyb6YV2b@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.