(In reply to wychuchol from comment #14)
> RX 5700 XT Pop OS 19.10 latest Oibaf mesa not su=
re what llvm
> Anomaly 1.5.0 update 3 standalone 64 bit mod for S.T.A.L.K.E.R. Call of
> Pripyat running under wine d3dx11_43->dxvk (winetricks dxvk d3dcomp=
iler_43
> d3dx11_43)
>=20
> Oct 30 02:49:30 pop-os kernel: [ 4864.627343]
> [drm:amdgpu_dm_commit_planes.constprop.0 [amdgpu]] *ERROR* Waiting for
> fences timed out!
> Oct 30 02:49:30 pop-os kernel: [ 4869.231450] [drm:amdgpu_job_timedout
> [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=3D2626284, emit=
ted
> seq=3D2626286
> Oct 30 02:49:30 pop-os kernel: [ 4869.231486] [drm:amdgpu_job_timedout
> [amdgpu]] *ERROR* Process information: process AnomalyDX11.exe pid 5791
> thread AnomalyDX11.exe pid 5791
> Oct 30 02:49:30 pop-os kernel: [ 4869.231487] [drm] GPU recovery disab=
led.
>=20
> Happens at random. Sometimes hangs straight away, sometimes can go ove=
r an
> hour without crash. Complete crash, no option available besides hard r=
eset.
> Not even mouse pointer would move (as with sdma0 hang).
>=20
> I'm sorry if it's not the right place to report this, I'm somewhat new=
 to
> all of this.

Ring gfx type hangs tend to be in Mesa. Report here:
https://gitlab.=
freedesktop.org/mesa/mesa/issues

Also I'm not sure how up to date the Oibaf repo is, but Mesa git landed ACO
recently for Navi cards. You can try with RADV_PERFTEST=3Daco environment
variable set if your Mesa is new enough, and you might have better luck with
hangs.