In my case, this definitely only happens when the mutter compositor switches to direct scanout. My most reliable reproducer is clicking an image in the Telegram desktop snap, which goes solid-fullscreen and enables mutter to do direct scanout.
Nov 03 11:20:17 thinkpad kernel: amdgpu 0000:63:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data Nov 03 11:20:18 thinkpad kernel: amdgpu 0000:63:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data Nov 03 11:20:18 thinkpad kernel: amdgpu 0000:63:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data Nov 03 11:20:19 thinkpad kernel: amdgpu 0000:63:00.0: [drm] REG_WAIT timeout 1us * 100000 tries - mpc2_assert_idle_mpcc line:481 Nov 03 11:20:29 thinkpad kernel: amdgpu 0000:63:00.0: [drm] *ERROR* [CRTC:80:crtc-0] flip_done timed out This only seems to happen when scanning-out to the internal laptop screen, while it does not happen when connected to an external screen with USB-C to HDMI. Thinkpad Z13 (Gen 1), AMD Ryzen 7 PRO 6850U. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2047154 Title: [amdgpu][drm] *ERROR* flip_done timed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2047154/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
