Repeated :firefox crashing AMD GPU on Ryzen 7, Linux Ubuntu 24.04.2 LTS

[Matt99001]

System Info: 
Ubuntu 24.04.2 LTS desktop, Ryzen 7 5800X (8c/16t), 32 GB RAM, AMD GPU, ASUS ROG STRIX B550-F GAMING WIFI II motherboard.

crash only seems to occur while watching facebook reels..

Log data:
16:37:34 kernel: snd_hda_intel 0000:08:00.1: spurious response 0x0:0x0, last cmd=0x970740
16:37:34 kernel: snd_hda_intel 0000:08:00.1: spurious response 0x200:0x0, last cmd=0x970740
16:37:34 kernel: snd_hda_intel 0000:08:00.1: spurious response 0x0:0x0, last cmd=0x370740
16:37:24 gdm3: Gdm: on_display_removed: assertion 'GDM_IS_REMOTE_DISPLAY (display)' failed
----------------
kernel: amdgpu 0000:08:00.0: amdgpu: ring gfx_0.0.0 timeout...
kernel: amdgpu 0000:08:00.0: amdgpu: Process firefox-bin pid 123351...

Running it by Gemni: 

Firefox was offloading video or heavy web page rendering directly onto your GPU's hardware chips. Something caused a massive bottleneck, the command "ring" timed out, and the GPU completely froze trying to handle it.

2. The Chain Reaction

Once the graphics chip seized up, the rest of the display stack crumbled in a cascade:

• The GPU Engine Locks Up: The kernel tries to force-reset the card to save it, but the hardware fails to respond (failed to halt cp gfx and MES failed to respond).

• The Audio Dies: Notice all those snd_hda_intel errors right after? Even though it says "Intel," that is actually the generic Linux driver controlling the HDMI/DisplayPort audio controller built directly onto your AMD card. Because the graphics card crashed, its audio subsystem started spitting out "spurious responses" and timing out.

• The Desktop Crashes: Finally, Gnome Desktop (gdm3) loses its connection to the monitor because the video card stopped talking, giving you those display errors and dropping you out of your session.

  The Workaround: Tame Firefox's Hardware Acceleration

  Since this specific crash was triggered directly by firefox-bin locking up the amdgpu driver, we can drastically increase your stability by telling Firefox to stop leaning so heavily on the GPU's experimental Linux hardware acceleration features.

  Let's toggle a couple of safety switches inside Firefox:

  1. Open Firefox, type about:config into the address bar, and hit Enter. Accept the warning.

  2. Search for media.hardware-video-decoding.enabled and double-click it to change it from true to false.

  3. Search for layers.acceleration.disabled and double-click it to change it from false to true.

     -------------------
     I've had this problem for a couple of months and have been trying to resolve it. 
     Now I'm passing the torch. 
     If there's any questions of needs to see a complete log, shoot me a message
     matt99001@
     that gmail place. 
     Just put FIREFOX in the subject line so I notice it.. 
     
     
     

[shanen5]

Your specifics suggest you're deeper than I am, but perhaps the crashes I'm seeing are related? Firefox keeps asking if I want to force the shutdown or wait, and eventually it dies. Once it gets to that state it is basically useless and work cannot be saved. Is there some way to compare notes to see if there is an underlying cause? It started getting bad a few updates ago and does not seem to be affecting Firefox on other platforms. I only have one other Ubuntu box right now, and I don't actually use Firefox very often on that one.