Comment 44 for bug 1900854

An other test using 5.9.1-050901-lowlatency, display is not breaking anymore but there are still issues in logs after the video has been played once:

export DISPLAY=:0 ; while true ; do mpv 'http://youtu.be/9J5CHTFWnTc' ; sleep 10 ; done

 (+) Video --vid=1 (*) (h264 1280x720)
 (+) Audio --aid=1 --alang=eng (*) (aac 2ch 44100Hz)
AO: [pulse] 44100Hz stereo 2ch float
Using hardware decoding (vaapi).
VO: [gpu] 1280x720 vaapi[nv12]
AV: 00:00:33 / 00:00:33 (99%) A-V: 0.000 Cache: 0.0s

Exiting... (End of file)
 (+) Video --vid=1 (*) (h264 1280x720)
 (+) Audio --aid=1 --alang=eng (*) (aac 2ch 44100Hz)
AO: [pulse] 44100Hz stereo 2ch float
Using hardware decoding (vaapi).
VO: [gpu] 1280x720 vaapi[nv12]
radeon: The kernel rejected CS, see dmesg for more information (-22).
radeon: The kernel rejected CS, see dmesg for more information (-22).

Audio/Video desynchronisation detected! Possible reasons include too slow
hardware, temporary CPU spikes, broken drivers, and broken files. Audio
position will not match to the video (see A-V status field).

radeon: The kernel rejected CS, see dmesg for more information (-22).

On later times, I am not sure VAAPI is still used (yuv420p vs vaapi[nv12]):

 (+) Video --vid=1 (*) (h264 1280x720)
 (+) Audio --aid=1 --alang=eng (*) (aac 2ch 44100Hz)
AO: [pulse] 44100Hz stereo 2ch float
[ffmpeg/video] h264: No support for codec h264 profile 100.
VO: [gpu] 1280x720 yuv420p
AV: 00:00:31 / 00:00:33 (92%) A-V: 0.000 Cache: 2.1s/433KB

dmesg is pretty much the same as:

https://launchpadlibrarian.net/502954026/CurrentDmesg.txt

[ 99.002309] radeon 0000:01:00.0: ring 5 stalled for more than 10080msec
[ 99.002317] radeon 0000:01:00.0: GPU lockup (current fence id 0x00000000000003fb last fence id 0x00000000000003ff on ring 5)
[ 99.012046] radeon 0000:01:00.0: couldn't schedule ib
[ 99.012107] [drm:radeon_uvd_suspend [radeon]] *ERROR* Error destroying UVD (-22)!
[ 99.028154] radeon 0000:01:00.0: Saved 1433 dwords of commands on ring 0.

Once I managed to get backtrace around DRM parts, I'll share it if it happens again.

Do you need more informations ?

Meanwhile let me crosslink this issue to:

https://gitlab.freedesktop.org/drm/amd/-/issues/630