Without amdgpu.dcdebugmask=0x210, I get the DMUB error the first time that I remove the usb-c wireless hdmi transmitter. (I never get to disconnect the transmitter a second time because the computer is unusable after this.) With the kernel option, I get the error when I plug the transmitter back in after removing it. This is using NixOS 24.11, kernel 6.11.x (as well as 6.6.x) and Gnome 47
The crashes significantly decreased with kernel 6.11. While I still experienced some minor UI glitches, crashes occurred only every 1-2 weeks.
After installing kernel 6.12, the glitches are gone. I’m hopeful that this update has fully resolved the issue, as @sinatosk mentioned, but only time will tell.
Oops. I wasn’t specific about my kernel version. I can still reproduce this on my AMD FW 13 running NixOS 24.11 with kernel 6.12.5 by unplugging my wireless display adapter
I just discovered that it matters which port I connect this wireless usb-c-to-hdmi adapter to (Amazon.com: Wireless HDMI Transmitter and Receiver, Upgrade Type-C 3.1 Port Wireless Hdmi Plug & Play Portable 2.4G/5G for Streaming Video and Audio to HDTV/Projector/Monitor from Martphone/Tablet/Laptop : Electronics). The back-left and back-right ports actually work fine. And as suggested by Expansion Card Functionality on Framework Laptop 13 (AMD Ryzen™ 7040 Series), the front-left port doesn’t work at all. The front-right port works until I unplug the transmitter, at which point the journal fills with DMUB errors and the machine is unusable. The knowledgebase article doesn’t lead me to expect this
This happens with every kernel that I have tested, including 6.6.x and 6.12.x, and none of the workarounds that I have found on this page helped
But now that I know to be very careful to avoid the front-right port I’m much less bothered by this
Mine are no longer so frequent but definitely exist. I get them a few times a week, but I probably only use the laptop for a couple of hours a day.
Happening to me at least once a day. I did not make the connection between the console error on restart and this “random” lag that is unrecoverable until restarting.
All I know is that it’s more likely to come up during the initial start of a video but that hasn’t been a reliable indicator.My CPU goes haywire on the system monitor but it doesn’t reflect on the process monitor - during the issue there is nothing about 3% CPU - so there is no obvious process causing this.
On my FW16 I’m also getting this dmesg error when my display goes blank a couple of times a week. Usually after my laptop has been sitting overnight doing nothing and I go to use it in the morning. It’s not being suspended.
The sudo cat /sys/kernel/debug/dri/1/amdgpu_gpu_recover command is the only thing that fixes it short of a reboot.
I’m using Ubuntu 24.10 with Bios 3.05, kernel 6.11.0-13.
interesting, my FW13 AMD UI started to freeze this week. Not during wakeup, but normal use.
sometimes journal has DMCUB error sometimes not.
- BIOS 3.05
- Debian testing/unstable
- kernel 6.12.13-amd64
- XFCE 4.20.1 with xserver, no wayland
amdgpu_gpu_recover always works, but I have to do this via ssh.
My FW13 AMD also semi-freezes as described, at random times during usage. Running journalctl -b -1 -p 0..3 after a reboot I see a lot of
amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
as well as a bunch of other errors.
- Operating System: Kubuntu 24.10
- KDE Plasma Version: 6.1.5
- Qt Version: 6.6.2
- Kernel Version: 6.11.0-13-generic (64-bit)
- Graphics Platform: Wayland
- Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics
- BIOS version: 03.05
Full log:
journalctl -b -1 -p 0..3
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: unknown error 0
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: unknown error 0
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: UCSI_GET_PDOS failed (-5)
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: unknown error 0
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: unknown error 256
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
fev 14 20:20:09 mj-framework13 systemd-udevd[437]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:61 Unknown group 'uaccess', ignoring.
fev 14 20:20:09 mj-framework13 (udev-worker)[466]: hiddev0: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:61 Only network interfaces can be renamed, ignoring NAME="usb/%k".
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: unknown error 256
fev 14 20:20:09 mj-framework13 kernel: ucsi_acpi USBC000:00: GET_CABLE_PROPERTY failed (-5)
fev 14 20:20:09 mj-framework13 kernel: cros-usbpd-charger cros-usbpd-charger.5.auto: Unexpected number of charge port count
fev 14 20:20:09 mj-framework13 kernel: cros-usbpd-charger cros-usbpd-charger.5.auto: probe with driver cros-usbpd-charger failed with error -71
fev 14 20:20:11 mj-framework13 systemd-udevd[437]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:61 Unknown group 'uaccess', ignoring.
fev 14 20:20:17 mj-framework13 sddm-helper[1690]: gkr-pam: unable to locate daemon control file
fev 14 20:20:19 mj-framework13 systemd-udevd[437]: /usr/lib/udev/rules.d/69-mixxx-usb-uaccess.rules:61 Unknown group 'uaccess', ignoring.
fev 14 20:20:20 mj-framework13 obexd[2233]: Unable to acquire registery: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: Unit evolution-source-re>
fev 14 20:20:20 mj-framework13 obexd[2233]: Unable to acquire registery: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: Unit evolution-source-re>
fev 14 20:39:43 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:44 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:44 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:44 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:45 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:45 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:45 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:46 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:46 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:46 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:46 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:47 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:47 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:47 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:48 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
fev 14 20:39:48 mj-framework13 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
1 Like
Same here, Ubuntu 25.04. Started out of nowhere.
This is really interesting – so I also have graphical freezes at random times. It’s been, more or less, ever since I got the machine (a few months ago), but I had some idea that I had never seen it happen back with an older 6.6 kernel, when I was very first running the machine… I sort of wrote that down as it just being a very intermittent problem and was proceeding trying to track it down on modern kernels.
Did you do an upgrade and then it started happening? Or it just started out of nowhere without any system / driver changes?
I made a mistake updating to Ubuntu 25.10. And the issue only happens when charger unplugged.
Will roll-back (via backup & re-install) to 24.04 - it wasn’t perfect, but it was quite stable.
That’s super-interesting. I might try going all the way back to that 6.6 kernel if I can, at some point, and see if it actually solves the issue like I halfway thought it did. I kind of thought it was my imagination but if you observed the same “real old stuff works, more recent stuff doesn’t” behavior then maybe it’s worth trying. Thanks.
And yes, some of the poking I was doing seemed like it was indicating that it was somehow related to power management, so it would certainly make sense if it only happened when not plugged in… but like I say, it’s sort of hard to tell what was real information about stuff that worked / didn’t work / made it more common, and how much was just randomness because it doesn’t happen all that often.
1 Like
Hello there, just had this (or similar issue) on
my System
- Framework 16 (1st Gen)
- with dGPU (1st Gen AMD)
- on Fedora 42 (Workstation Edition)
- with BIOS Version 03.05 (from fwupd)
- using Linux 6.16.7-200.fc42.x86_64 (unchanged, from fedora)
- with a second Monitor connected via HDMI using a Dell WD22TB4 Thunderbolt docking station
- with automatic brightness already disabled in GNOME Settings
- with the GitHub - daitj/gnome-display-brightness-ddcutil: Display brightness slider for gnome shell using ddcutil backend Extension enabled in GNOME (and ddcutil installed per README)
Previous to today’s system updates via gnome-software this setup worked flawlessly.
I can only provide the selinux-audit log for which components were updated as gnome-software provides no update-history and packagekit crashes when trying to access it’s transaction history (pkcon get-transactions always segfaults on my system when trying to print the results).
selinux SOFTWARE_UPDATE audit
op=update sw=“gstreamer1-1.26.6-1.fc42.i686”
op=update sw=“gstreamer1-1.26.6-1.fc42.i686”
op=update sw=“libsoup3-3.6.5-6.fc42.i686”
op=update sw=“p11-kit-0.25.8-1.fc42.i686”
op=update sw=“mesa-vulkan-drivers-25.1.9-1.fc42.i686”
op=update sw=“mesa-libGL-25.1.9-1.fc42.i686”
op=update sw=“mesa-libEGL-25.1.9-1.fc42.i686”
op=update sw=“pipewire-alsa-1.4.8-2.fc42.i686”
op=update sw=“pipewire-1.4.8-2.fc42.i686”
op=update sw=“pipewire-libs-1.4.8-2.fc42.i686”
op=update sw=“mesa-libgbm-25.1.9-1.fc42.i686”
op=update sw=“mesa-dri-drivers-25.1.9-1.fc42.i686”
op=update sw=“libsoup3-3.6.5-6.fc42.x86_64”
op=update sw=“python-pip-wheel-24.3.1-5.fc42.noarch”
op=update sw=“qt6-qttranslations-6.9.2-1.fc42.noarch”
op=update sw=“tldr-3.4.2-1.fc42.noarch”
op=update sw=“pipewire-pulseaudio-1.4.8-2.fc42.x86_64”
op=update sw=“pipewire-plugin-libcamera-1.4.8-2.fc42.x86_64”
op=update sw=“pipewire-alsa-1.4.8-2.fc42.x86_64”
op=update sw=“p11-kit-trust-0.25.8-1.fc42.x86_64”
op=update sw=“p11-kit-server-0.25.8-1.fc42.x86_64”
op=update sw=“p11-kit-client-0.25.8-1.fc42.x86_64”
op=update sw=“mesa-vulkan-drivers-25.1.9-1.fc42.x86_64”
op=update sw=“mesa-va-drivers-25.1.9-1.fc42.x86_64”
op=update sw=“mesa-libGL-25.1.9-1.fc42.x86_64”
op=update sw=“mesa-libEGL-25.1.9-1.fc42.x86_64”
op=update sw=“pipewire-gstreamer-1.4.8-2.fc42.x86_64”
op=update sw=“gstreamer1-plugin-libav-1.26.6-1.fc42.x86_64”
op=update sw=“gst-editing-services-1.26.6-1.fc42.x86_64”
op=install sw=“mesa-va-drivers-25.1.9-1.fc42.i686”
op=update sw=“gstreamer1-plugins-bad-free-1.26.6-1.fc42.x86_64”
op=update sw=“gstreamer1-plugins-good-qt-1.26.6-1.fc42.x86_64”
op=update sw=“python3-boto3-1.40.30-1.fc42.noarch”
op=update sw=“pipewire-utils-1.4.8-2.fc42.x86_64”
op=update sw=“xen-libs-4.19.3-4.fc42.x86_64”
op=update sw=“qt6-qtwayland-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qt5compat-6.9.2-1.fc42.x86_64”
op=update sw=“gstreamer1-plugins-good-qt6-1.26.6-1.fc42.x86_64”
op=update sw=“qt6-qtmultimedia-6.9.2-1.fc42.x86_64”
op=update sw=“tesseract-libs-5.5.0-5.fc42.x86_64”
op=update sw=“ibus-typing-booster-2.27.75-1.fc42.noarch”
op=install sw=“python3-httpx-0.27.2-3.fc42.noarch”
op=install sw=“python3-httpcore-1.0.7-2.fc42.noarch”
op=update sw=“expat-2.7.2-1.fc42.i686”
op=install sw=“python3-h11-0.14.0-7.fc42.noarch”
op=install sw=“tesseract-common-5.5.0-5.fc42.noarch”
op=install sw=“tesseract-langpack-eng-4.1.0-10.fc42.noarch”
op=install sw=“tesseract-tessdata-doc-4.1.0-10.fc42.noarch”
op=update sw=“qt6-qtquick3d-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtquicktimeline-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtdeclarative-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtsvg-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtshadertools-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtbase-gui-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtbase-6.9.2-1.fc42.x86_64”
op=update sw=“qt6-qtbase-common-6.9.2-1.fc42.noarch”
op=update sw=“qt6-filesystem-6.9.2-1.fc42.x86_64”
op=update sw=“xen-licenses-4.19.3-4.fc42.x86_64”
op=update sw=“selinux-policy-targeted-42.9-1.fc42.noarch”
op=update sw=“selinux-policy-42.9-1.fc42.noarch”
op=update sw=“pipewire-jack-audio-connection-kit-1.4.8-2.fc42.x86_64”
op=update sw=“pipewire-jack-audio-connection-kit-libs-1.4.8-2.fc42.x86_64”
op=update sw=“pipewire-1.4.8-2.fc42.x86_64”
op=update sw=“python3-s3transfer-0.14.0-1.fc42.noarch”
op=install sw=“python3-anyio-4.8.0-1.fc42.noarch”
op=install sw=“python3-certifi-2025.07.09-1.fc42.noarch”
op=install sw=“python3-sniffio-1.3.1-4.fc42.noarch”
op=update sw=“python3-botocore-1.40.30-1.fc42.noarch”
op=update sw=“gstreamer1-plugins-good-1.26.6-1.fc42.x86_64”
op=update sw=“gstreamer1-plugins-bad-free-libs-1.26.6-1.fc42.x86_64”
op=install sw=“mesa-filesystem-25.1.9-1.fc42.i686”
op=update sw=“gstreamer1-plugins-base-1.26.6-1.fc42.x86_64”
op=update sw=“mesa-libgbm-25.1.9-1.fc42.x86_64”
op=update sw=“mesa-dri-drivers-25.1.9-1.fc42.x86_64”
op=update sw=“mesa-filesystem-25.1.9-1.fc42.x86_64”
op=update sw=“p11-kit-0.25.8-1.fc42.x86_64”
op=update sw=“expat-2.7.2-1.fc42.x86_64”
op=update sw=“pipewire-libs-1.4.8-2.fc42.x86_64”
op=update sw=“gstreamer1-1.26.6-1.fc42.x86_64”
After the PackageKit Offline Update Reboot (post update install) and logging in to GNOME the internal display froze, the external display still working without problem. After trying to adjust any display setting (scaling/resolution/enable-disable display) in gnome-settings the external display stutters (as previously described by others). Rebooting fixes the problem until logging back into GNOME when the behavior appears the same again.
Disabling the above named GNOME Extension immediately (without reboot or session-restart) fixes the frozen internal display and the problem is gone. So for anyone using this extension (or using ddcutil or similar software directly) this could be the cause of your problem.
some shortened and redacted logs
#Disabled Extension (11:40)
11:37:43 - ddcutil: [ 9627] /dev/i2c-6, Checking EDID failed after 3 tries (B)
11:37:43 - ddcutil: [ 9627] /dev/i2c-6, Checking EDID failed after 3 tries (B)
11:37:42 - ddcutil: [ 9627] (i2c_check_open_bus_alive) Retrying i2c_check_edid_exists_by_dh() (c): Sleeping for 1000 milliseconds
11:37:41 - ddcutil: [ 9627] (i2c_check_open_bus_alive) Retrying i2c_check_edid_exists_by_dh() (c): Sleeping for 1000 milliseconds
11:37:41 - ddcutil: No traced function stack for current thread
11:37:41 - ddcutil: Traced function stack on entry to i2c_check_open_bus_alive()
11:37:41 - ddcutil: [ 9627] Error detecting VCP version using VCP feature xDF: Error_Info[DDCRC_DISCONNECTED in i2c_check_open_bus_alive]
11:37:41 - ddcutil: [ 9627] /dev/i2c-6, Checking EDID failed after 3 tries (B)
11:37:40 - ddcutil: [ 9627] (i2c_check_open_bus_alive) Retrying i2c_check_edid_exists_by_dh() (c): Sleeping for 1000 milliseconds
11:37:39 - ddcutil: [ 9627] (i2c_check_open_bus_alive) Retrying i2c_check_edid_exists_by_dh() (c): Sleeping for 1000 milliseconds
11:37:39 - ddcutil: No traced function stack for current thread
11:37:39 - ddcutil: Traced function stack on entry to i2c_check_open_bus_alive()
10:39:41 - ddcutil: [ 4518] /dev/i2c-6, Checking EDID failed after 3 tries (B)
#PowerOn (10:38)
#PowerOff (10:35)
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR Error queueing DMUB command: status=2
[…]
10:26:41 - ddcutil: [ 5429] /dev/i2c-6, Checking EDID failed after 3 tries (B)
[…]
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR Error queueing DMUB command: status=2
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[…]
10:24:35 - —[ end trace 0000000000000000 ]—
[…]
10:24:35 - RIP: 0010:dmub_replay_get_state+0x54/0x80 [amdgpu]
[…]
10:24:35 - CPU: 6 UID: 0 PID: 1049 Comm: kworker/u64:11 Not tainted 6.16.7-200.fc42.x86_64 #1 PREEMPT(lazy)
[…]
10:24:35 - WARNING: CPU: 6 PID: 1049 at drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_replay.c:38 dmub_replay_get_state+0x54/0x80 [amdgpu]
10:24:35 - ------------[ cut here ]------------
[…]
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR Error queueing DMUB command: status=2
10:XX:XX - amdgpu 0000:c4:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
[…]
10:23:05 - amdgpu 0000:03:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x07002F00
10:21:19 - ddcutil: [ 4335] /dev/i2c-6, Checking EDID failed after 3 tries (B)
10:21:18 - ddcutil: [ 4335] (i2c_check_open_bus_alive) Retrying i2c_check_edid_exists_by_dh() (c): Sleeping for 1000 milliseconds
10:20:13 - amdgpu 0000:c4:00.0: amdgpu: [drm] DMUB hardware initialized: version=0x08005100
10:20:12 - amdgpu 0000:c4:00.0: amdgpu: [drm] Loading DMUB firmware via PSP: version=0x08005100
#PackageKit Offline Update Post-Install Restart (10:20)
#Restart into PackageKit Offline Update (10:18)
10:13:45 - ddcutil: [ 52326] /dev/i2c-6, Checking EDID failed after 3 tries (B)
10:12:24 - ddcutil: [ 51953] /dev/i2c-6, Checking EDID failed after 3 tries (B)
Such issues are not unheard of when using ddcutil: GitHub · Where software is built