# Amdgpu Error queueing DMUB command: status=2 when waking from suspend

**URL:** <https://community.frame.work/t/amdgpu-error-queueing-dmub-command-status-2-when-waking-from-suspend/53155>\
**Category:** Linux\
**Tags:** opensuse\
**Created:** [June 18, 2024, 4:41pm UTC](https://community.frame.work/t/amdgpu-error-queueing-dmub-command-status-2-when-waking-from-suspend/53155 "2024-06-18T16:41:26Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![sinatosk](https://avatars.discourse-cdn.com/v4/letter/s/9de0a6/32.png) [@sinatosk](https://community.frame.work/u/sinatosk)\
**Post date:** [September 20, 2024, 6:22am UTC](https://community.frame.work/t/amdgpu-error-queueing-dmub-command-status-2-when-waking-from-suspend/53155/41 "2024-09-20T06:22:21Z")

</div>

I’m using Gentoo with KDE Plamsa 6.1.4 Wayland with [this linux firmware commit](https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=87cae274d38e69f6e9461f966fe42d223e20d7be) with BIOS 3.04beta

I’ve been experiencing this PSR issue since Linux 6.7.x ( I don’t remember 6.6.x ) and used 6.8.x, 6.9.x, 6.10.x

I decided to try Linux 6.11.0 sooner

Unfortunately the PSR issue is still there and I’m sure that any application that’s using Xwayland ( Linux 6.10.x and now 6.11.0 ) has a higher chance of triggering the PSR issue, especially when it comes to video ( youtube, reddit, twitch )

I’m having to use disable Wayland usage in Firefox because of [high CPU usage.](http://community.frame.work/t/high-power-consumption-with-firefox/53481/15)

The PSR issue was also being triggered when using JetBrains editors until I enabled Wayland use in them and the PSR issues reduced significantly.

There have been some improvements during the PSR issue, the screen updates more frequently ( 0.5-1.0 second(s) ) instead every 3-5 seconds ( closer to 3 ).

I’ve tried the following command when on the KDE Plasma desktop and again logging out to the TTY

> sudo cat /sys/kernel/debug/dri/1/amdgpu\_gpu\_recover

and both times the screen goes black ( turns off I guess ) but never comes back on, so I’m having to cold reboot ( holding down power button for about 8 seconds and then turn back on again )

and I have the kernel command line parameter

> amdgpu.gpu\_recovery=1

set too. I think this is required for the amdgpu\_gpu\_recover to work

The kernel log ( different error to Linux 6.10 ) was showing alot ( not as many as Linux 6.10 )

```auto
amdgpu 0000:c2:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

```

I’m wondering if there is a log stored somewhere

and one time I see ( in middle of previous error messages )

```auto
amdgpu 0000:c2:00.0: [drm] *ERROR* [CRTC:79:crtc-0] flip_done timed out

```

and one time I see ( in middle of previous error messages )

```auto
amdgpu 0000:c2:00.0: [drm] enabling link 0 failed: 15

```

When Linux 6.12-rc1 is released ( 29th/30th September maybe? ), I think I’ll try that as it will have Panel Replay ( I’m interpreting it as a better alternative to PSR ) enabled and see how that goes.

---

_[View the full topic](https://community.frame.work/t/amdgpu-error-queueing-dmub-command-status-2-when-waking-from-suspend/53155)._