Laptop 13 AMD Ryzen 7 7840U Ubuntu Freezing

[Elie_Asmar]

Hello,

My machine specs: Ubuntu 24.04 - Kernel 6.14.0-29 - BIOS 3.16

It was working fine for a year now, but in the last week it froze 3 times. It became fully unresponsive and I had to press the power button to turn it off and reboot. I mostly need a way to debug/troubleshoot and find out what the issue is. Any logs or something I could look into? The only thing I can say is that the freezing happened when I was running my terminal window, 2nd workstation, using alacritty, tmux, nvim.

So I donno if it’s one of these tools causing some issue, or if it’s a hardware thing, or kernel thing, or a fullscreen thing. Any idea how I could debug or investigate this?

N.B: I don’t know if it’s a coincidence or what, but this started happening after i started doing a small performance testing for an application i’m writing, so sometimes i fully used all 8 cores, etc. I never did that before so it’s a first, just like the freezing is a first. Any guidance would be helpful.

And one thing I noticed the second time this happened, I didn’t touch it for 30 min to see if it would recover on its own, but then the screen became fully white, that’s when I turned it off with the power button.

Just ran this command to get some info: journalctl -p err and got the following for yesterday and today’s freezes:

Sep 22 19:38:26 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR [PLANE:58:plane-3] commit wait timed outSep 22 19:38:26 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:26 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:27 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:27 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:27 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:27 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:28 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 19:38:38 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR [CRTC:79:crtc-0] flip_done timed outSep 22 19:53:06 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR flip_done timed outSep 22 19:53:06 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR [CRTC:79:crtc-0] commit wait timed outSep 22 19:53:16 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR flip_done timed outSep 22 19:53:16 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR [CONNECTOR:93:eDP-1] commit wait timed outSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR flip_done timed outSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR [PLANE:58:plane-3] commit wait timed outSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic dataSep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dpia_query_hpd_status: for link(5) dpia(0) failed with status(0), curren>Sep 22 20:35:57 elie-Laptop-13-AMD-Ryzen-7040Series kernel: amdgpu 0000:c1:00.0: [drm] ERROR dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

…

Sep 23 16:28:03 elie-Laptop-13-AMD-Ryzen-7040Series gdm3[1713]: Gdm: on_display_added: assertion ‘GDM_IS_REMOTE_DISPLAY (display)’ failedSep 23 16:28:03 elie-Laptop-13-AMD-Ryzen-7040Series gdm3[1713]: Gdm: on_display_removed: assertion ‘GDM_IS_REMOTE_DISPLAY (display)’ failedSep 23 16:28:20 elie-Laptop-13-AMD-Ryzen-7040Series gdm-password][96940]: gkr-pam: unable to locate daemon control fileSep 23 16:28:20 elie-Laptop-13-AMD-Ryzen-7040Series gdm3[1713]: Gdm: on_display_added: assertion ‘GDM_IS_REMOTE_DISPLAY (display)’ failedSep 23 16:28:21 elie-Laptop-13-AMD-Ryzen-7040Series systemd[96959]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-97210.scope - Application launched by gnome-se>Sep 23 16:28:21 elie-Laptop-13-AMD-Ryzen-7040Series systemd[96959]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-97207.scope - Application launched by gnome-s>Sep 23 16:28:22 elie-Laptop-13-AMD-Ryzen-7040Series systemd[96959]: Failed to start app-gnome-im\x2dlaunch-97452.scope - Application launched by gnome-session-binary.Sep 23 16:28:22 elie-Laptop-13-AMD-Ryzen-7040Series systemd[96959]: Failed to start app-gnome-ubuntu\x2dreport\x2don\x2dupgrade-97487.scope - Application launched by g>Sep 23 16:28:22 elie-Laptop-13-AMD-Ryzen-7040Series systemd[96959]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-97528.scope - Application launched by gnome>Sep 23 16:28:23 elie-Laptop-13-AMD-Ryzen-7040Series gdm3[1713]: Gdm: on_display_removed: assertion ‘GDM_IS_REMOTE_DISPLAY (display)’ failed

[JL_Framework]

Hello, and welcome to the forum.

This sounds like a problem that people have reported before, and that I have encountered - namely, a problematic combination of kernel and BIOS. But I will let others, more knowledgeable than I, confirm (or deny) that.

[Mario_Limonciello]

Just a few potential causes I know of

GitHub - daitj/gnome-display-brightness-ddcutil: Display brightness slider for gnome shell using...

• Gnome/kde Night light feature.

[Victor-Ray_Sobye]

From what I could find this seems to be a recurring driver issue for AMD GPU’s, mostly happening for Ubuntu but also a few NixOS and Arch users have encountered this issue (probably affects a lot of users with different distro’s since it’s seemingly a driver issue and isn’t really distro specific but these were the ones primarily reporting it), some recently and others a few years back. I’ve put some links below with more info and various steps you can try. There’s also lots more about this on the forum you can search for.

[RESPONDED] Error waiting for DMUB idle: status=3

Yes I was still seeing the issue, albeit somewhat rarely, before I stopped using the FW13 on a regular basis. I returned to using it for the first time in some months today after getting the upgraded screen, and wouldn’t you know it, I’m now seeing different fun amdgpu crashes. I need stability for my productivity so my daily driver is a MBP now. [ 3202.711724] [ C11] gmc_v11_0_process_interrupt: 146 callbacks suppressed [ 3202.711731] [ C11] amdgpu 0000:c1:00.0: amdgpu: [mmhub] page f…

Reddit - The heart of the internet

Bug #2047154 “[amdgpu][drm] *ERROR* flip_done timed out” : Bugs :...

[bisected, regression] Intermittent freezes (flip_done timed out) since...

Computer randomly locks up at graphical level / Kernel & Hardware / Arch...

DCMUB Error on BIOS 3.05 + Kernel 6.13.1 hit a very nasty AMDGPU bug on Framework Laptop 13 (AMD Ryzen 7 7840U)

I wasn’t able to reproduce any of the above-mentioned issue with 0x12 for awhile now, probably since the MESA bump, any issue is gone. I will move back to 0x10 and drive that for 6 months or so and report if I see any issue show up. EDIT : At the time, this comment was made I’m running MESA 25.0.7 & Linux kernel 6.16.8 with in my kernel cmdlineamdgpu.dcdebugmask=0x12, BIOS version 3.05

[Victor-Ray_Sobye]

Just gonna add this in here, I remembered the Arch wiki’s Framework 13 page had mentioned this issue and possible solutions in chapter 7.16.

Framework Laptop 13 - ArchWiki

[JL_Framework]

Our very own ArchWiki page? That’s going to a godsend!

But, hold on, what’s this?’ Section 7.13 of that wiki has the following title.

(AMD) TLP is not advised for power management. PPD is recommended

That is bad news, especially for the following reason. A thread (on this forum - here) cited by the wiki says: ‘PPD’ does little and is no longer developed. To think that I thought that running Linux on a Framework would be easy!

[Stebalien]

That’s not the whole story.

1. PPD intentionally does little because the defaults should be fixed such that setting the power profile is all that’s necessary.
2. PPD is maintained and was adopted into the upower project.

Also see PPD’s “Why Not” section.

Note: the recommendation to use PPD came from @Mario_Limonciello, the AMD kernel dev who also maintains PPD.

[JL_Framework]

Dear Stebalien

Re 1: surely, for laptops running Linux, various power-saving tweaks are necessary; I am not even clear that PPD will switch power-state upon power-supply change. But, ah, the page that you linked seems to show that PPD does and/or can do more than I thought.

Re 2: I’ll have to look into how to install PPD.

Your ‘bot’ link puzzled me, especially after I saw that it points to a location that says nothing about bots.

EDIT: I am in danger of de-railing the thread. The forum discussion of ppd-Vs-tlp is here.

[Stebalien]

@JL_Framework

Your ‘bot’ link puzzled me, especially after I saw that it points to a location that says nothing about bots.

Ah, sorry, that’s a combination of:

1. This forum automatically trying to fetch the title of the link.
2. The linked page’s anti-bot measures.