Created attachment 298139 [details]
dmesg

Jul 31 09:50:49 helium kernel: [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* Waiting for fences timed out!
    Jul 31 09:50:52 helium kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=18739, emitted seq=18742
    Jul 31 09:50:52 helium kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process com.github.rafo pid 4266 thread gjs:cs0 pid 4320
    Jul 31 09:50:52 helium kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
    Jul 31 09:50:53 helium kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_2.1.0 test failed (-110)
    Jul 31 09:50:53 helium kernel: [drm:amdgpu_gfx_enable_kcq.cold [amdgpu]] *ERROR* KCQ enable failed
    Jul 31 09:50:53 helium kernel: [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block <gfx_v9_0> failed -110


In certain situations I'm able to crash/freeze my system by playing mp4 videos with (vaapi-acceleration) enabled. If the crash/freeze happens, the screen goes black and the system isn't responding to any input. Sadly in this case it's at random if something was able to write output to the log. In most cases there is nothing written about the crash in the log.


My environment is 
GNOME in Wayland mode
With native Wayland apps (in this Case Firefox and clapper (https://rafostar.github.io/clapper/)
APU is an Ryzen 5 4500U


For Firefox I'm not able to reliable recreate that bug. It happens at random while scrolling in twitter and reddit. Never happens in Netflix or Youtube for example.

Luckily I was able to recreate it with an app called clapper and a video provided by someone on reddit: 
https://cdn.discordapp.com/attachments/399812928854949890/870910339548590180/VID_20210731_124021.mp4

Steps:
1. Have GNOME running in Wayland mode and vaapi installed (check with 
'vainfo`)
2. Install clapper
3. Download the video
4. Run the video in Clapper
5. While running, launch the video again in clapper


It should *not* create another instance of clapper, but try to re-launch the video in the same instance of clapper that was already running. You'll hear maybe a few sec of the audio, but your whole session is frozen and will enter an all black screen without possible recovery a few sec later.

I'm able to recreate this with every Kernel I tested. So down to 5.8