Commen=
t # 8
on bug 11176=
3
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:=20=20
> > > https://bugs.freedesktop.org/show_bug.=
cgi?id=3D111669
> > >=20
> > > For my particular case at least, AMD_DEBUG=3Dnodma seems to =
fix it
> >=20
> > You are refering to sdma0 / sdma1 type hang which is tracked
> > here:https://bugs.freedesktop.org/show_bug.=
cgi?id=3D111481
> >=20
> > For ring_gfx hangs they're quite more reproducible and are not af=
fected by
> > AMD_DEBUG=3Dnodma or AMD_DEBUG=3Dnongg which I already mentioned =
above in the
> > bug description.
>=20
> Sorry, but this is incorrect. My Minecraft hang is most definitely a r=
ing
> gfx hang, *not* sdma. I've posted logs and apitraces in the linked thr=
ead if
> you'd like to check for yourself.
>=20
> I can't explain why nodma isn't working for you, perhaps it doesn't wo=
rk for
> game? Have you tried putting it in /etc/environment so it's system-wid=
e? 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 a=
re
more mysterious than sdma0/1 hangs it seems, since there is no "univer=
sal"
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 han=
gs
for me, so it's really really confusing.