Comme=
nt # 12
on bug 10235=
8
from Thomas Hellstr=C3=B6m
(In reply to haro41 from comment #11)
> i applied your patch successful, still the freez=
es, maybe in average a bit
> later now.
>=20
> The behavoir changed a bit:
>=20
> before patch:
>=20
> vblank_mode=3D2 (default)-> always freezes inside 0..2 minutes runt=
ime,=20
> framerate fix/clamped at 50(as expected)
> vblank_mode=3D0 -> no freezes at all, dynamic, high framer=
ates=20
> LIBGL_DRI3_DISABLE=3D1 -> no freezes at all, framerate fix at 50=
=20
>=20
>=20
> after patch:
>=20
> vblank_mode=3D2 (default)-> always freezes inside 0..2 minutes runt=
ime,=20
> framerate fix/clamped at 100(!!)
> vblank_mode=3D0 -> no freezes at all, dynamic, high framer=
ates=20
> LIBGL_DRI3_DISABLE=3D1 -> no freezes at all, framerate fix at 50=
=20
>=20
>=20
> To be honest, i am not familiar enough with DRM internals to understan=
d what
> exactly happens here, but it looks like something is broken in respect=
to
> DRI 3 usage.
>=20
> Somehow i think i could be the only one with this freezes and to ensur=
e i am
> not wasting your time:
> Can you give me a hint, where i should look first to exclude it is som=
ething
> specific to my system/setup?
That's really weird :).
Actually I don't think anything's wrong with your setup, but rather that
there's a multithreading bug in dri3 or the app. There's no concurrency
protection at all in the dri3 client and I'm not sure that's correct. I thi=
nk
you're the only one seeing this possibly perhaps because you're the first to
try it with a heavily multithreaded application.
Anyway, I'm OK with commenting out the glFinish() wait for swapbuffers until
someone has the possibility to debug this thoroughly. Unfortunately WarThun=
der
doesn't run on vmware's svga driver (yet) due to bugs...
It would also be good to try to rule out server side radeon dri3 problems.
Perhaps by running it on nouveau or intel...