Comment # 8
on bug 111763
from Marko Popovic
(In reply to Doug Ty from comment #7) > (In reply to Marko Popovic from comment #6) > > (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 > > > > 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. > > Sorry, but this is incorrect. My Minecraft hang is most definitely a ring > gfx hang, *not* sdma. I've posted logs and apitraces in the linked thread if > you'd like to check for yourself. > > I can't explain why nodma isn't working for you, perhaps it doesn't work for > game? Have you tried putting it in /etc/environment so it's system-wide? I > don't know what to tell you regarding nodma, but my hang is definitely ring > gfx as well. I guess we just have many different types of hangs then... ring_gfx hangs are more mysterious than sdma0/1 hangs it seems, since there is no "universal" workaround for them. nodma works for stopping global sdma-type hangs for me, nongg works for stopping the citra-related hang of ring_gfx type, but none of those 2 variables work for stopping Starcraft II and RoTR ring_gfx-type hangs for me, so it's really really confusing.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
