Comment 11 for bug 1949497

I'm experiencing the problem on radeon driver too. Only way to run without any error is setting power_dpm_state to "battery" (or setting power_dpm_force_performance_level to "low").

It gives gpu fault error:

[ 173.274091] radeon 0000:01:00.0: WB enabled
[ 173.274093] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00
[ 173.274095] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr 0x0000000080000c04
[ 173.274096] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr 0x0000000080000c08
[ 173.274097] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000080000c0c
[ 173.274098] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr 0x0000000080000c10
[ 173.274642] debugfs: File 'radeon_ring_gfx' in directory '0' already present!
[ 173.274647] debugfs: File 'radeon_ring_cp1' in directory '0' already present!
[ 173.274649] debugfs: File 'radeon_ring_cp2' in directory '0' already present!
[ 173.274650] debugfs: File 'radeon_ring_dma1' in directory '0' already present!
[ 173.274653] debugfs: File 'radeon_ring_dma2' in directory '0' already present!
[ 173.469429] [drm] ring test on 0 succeeded in 1 usecs
[ 173.469435] [drm] ring test on 1 succeeded in 1 usecs
[ 173.469439] [drm] ring test on 2 succeeded in 1 usecs
[ 173.469448] [drm] ring test on 3 succeeded in 4 usecs
[ 173.469454] [drm] ring test on 4 succeeded in 3 usecs
[ 173.469488] [drm] ib test on ring 0 succeeded in 0 usecs
[ 173.469516] [drm] ib test on ring 1 succeeded in 0 usecs
[ 173.469542] [drm] ib test on ring 2 succeeded in 0 usecs
[ 173.469556] [drm] ib test on ring 3 succeeded in 0 usecs
[ 173.469568] [drm] ib test on ring 4 succeeded in 0 usecs
[ 173.690183] radeon 0000:01:00.0: GPU fault detected: 146 0x0aa31014
[ 173.690189] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_ADDR 0x00100DD5
[ 173.690191] radeon 0000:01:00.0: VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x03010014
[ 173.690192] VM fault (0x04, vmid 1) at page 1052117, write from CB (16)
[ 184.196457] Asynchronous wait on fence radeon:radeon.gfx:28 timed out (hint:submit_notify [i915])
[ 184.196439] Asynchronous wait on fence 0000:00:02.0:gnome-shell[1653]:3b6 timed out (hint:intel_atomic_commit_ready [i915])
[ 184.196921] Asynchronous wait on fence radeon:radeon.gfx:26 timed out (hint:submit_notify [i915])
[ 184.232357] radeon 0000:01:00.0: ring 0 stalled for more than 10244msec
[ 184.232376] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000025 last fence id 0x0000000000000029 on ring 0)
[ 184.740610] radeon 0000:01:00.0: ring 0 stalled for more than 10752msec
[ 184.740635] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000025 last fence id 0x0000000000000029 on ring 0)
[ 185.252668] radeon 0000:01:00.0: ring 0 stalled for more than 11264msec
[ 185.252690] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000025 last fence id 0x0000000000000029 on ring 0)
[ 185.764745] radeon 0000:01:00.0: ring 0 stalled for more than 11776msec
[ 185.764771] radeon 0000:01:00.0: GPU lockup (current fence id 0x0000000000000025 last fence id 0x0000000000000029 on ring 0)
...

I tried the 4.19 kernel 1-2 weeks ago (with Ubuntu 20.04 and latest mesa drivers), application launches fine and runs without any error. But after playing games for hours, sometimes it gives the gfx timeout error again.