You are not logged in.

#1 2025-01-11 10:40:07

Greenscreen23
Member
Registered: 2023-03-13
Posts: 3

[SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

Hey,

I am facing some issues with my amdgpu driver.  Sometimes the image is very laggy, making the laptop unusable. Everything else works, video calls are uninterrupted (yet laggy from my side only) and I can still type in the terminal (with very high input delay). It has been happening for some time now, but I have not found a clear indicator to when it happens. Rebooting has so far always fixed the issue.

System Info

Operating System: Arch Linux 
KDE Plasma Version: 6.2.5
KDE Frameworks Version: 6.9.0
Qt Version: 6.8.1
Kernel Version: 6.12.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics
Memory: 30,7 GiB of RAM
Graphics Processor: AMD Radeon 760M
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A5
journalctl -k -b-1 | grep amdgpu
Jan 11 09:58:42 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=74471d0a-1b6e-4dea-a165-539ea963f5d8 rw loglevel=3 rd.luks.name=e2b73488-45b2-4d30-80a1-c577d1f4de9a=root root=/dev/mapper/root amdgpu.sg_display=0
Jan 11 09:58:42 archlinux kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=74471d0a-1b6e-4dea-a165-539ea963f5d8 rw loglevel=3 rd.luks.name=e2b73488-45b2-4d30-80a1-c577d1f4de9a=root root=/dev/mapper/root amdgpu.sg_display=0
Jan 11 09:58:44 archlinux kernel: [drm] amdgpu kernel modesetting enabled.
Jan 11 09:58:44 archlinux kernel: amdgpu: Virtual CRAT table created for CPU
Jan 11 09:58:44 archlinux kernel: amdgpu: Topology: Add CPU node
Jan 11 09:58:44 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: Fetched VBIOS from VFCT
Jan 11 09:58:45 archlinux kernel: amdgpu: ATOM BIOS: 113-PHXGENERIC-001
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: vgaarb: deactivate vga console
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: VRAM: 512M 0x0000008000000000 - 0x000000801FFFFFFF (512M used)
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: GART: 512M 0x00007FFF00000000 - 0x00007FFF1FFFFFFF
Jan 11 09:58:45 archlinux kernel: [drm] amdgpu: 512M of VRAM memory ready
Jan 11 09:58:45 archlinux kernel: [drm] amdgpu: 15697M of GTT memory ready.
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: reserve 0x4000000 from 0x8018000000 for PSP TMR
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: RAS: optional ras ta ucode is not available
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: RAP: optional rap ta ucode is not available
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: SMU is initialized successfully!
Jan 11 09:58:45 archlinux kernel: kfd kfd: amdgpu: Allocated 3969056 bytes on gart
Jan 11 09:58:45 archlinux kernel: kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
Jan 11 09:58:45 archlinux kernel: amdgpu: Virtual CRAT table created for GPU
Jan 11 09:58:45 archlinux kernel: amdgpu: Topology: Add dGPU node [0x15bf:0x1002]
Jan 11 09:58:45 archlinux kernel: kfd kfd: amdgpu: added device 1002:15bf
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: SE 1, SH per SE 2, CU per SH 6, active_cu_number 8
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 8
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring jpeg_dec uses VM inv eng 1 on hub 8
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 13 on hub 0
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: amdgpu: Runtime PM not available
Jan 11 09:58:45 archlinux kernel: [drm] Initialized amdgpu 3.59.0 for 0000:c1:00.0 on minor 1
Jan 11 09:58:45 archlinux kernel: fbcon: amdgpudrmfb (fb0) is primary device
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:225
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:233
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:241
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: [drm] REG_WAIT timeout 1us * 1000 tries - dcn314_dsc_pg_control line:249
Jan 11 09:58:45 archlinux kernel: amdgpu 0000:c1:00.0: [drm] fb0: amdgpudrmfb frame buffer device
Jan 11 09:59:16 Laptop-Greenscreen23 kernel: snd_hda_intel 0000:c1:00.1: bound 0000:c1:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu])
Jan 11 11:02:58 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:58 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:58 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:58 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:59 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:59 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:02:59 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:00 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:00 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:00 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:01 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:01 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:01 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:02 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:02 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:02 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:02 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:03 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:03 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:04 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:04 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:04 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:05 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:05 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:06 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:06 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:06 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Jan 11 11:03:06 Laptop-Greenscreen23 kernel: amdgpu 0000:c1:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data

I have the latest firmware:

fwupdmgr get-updates
Devices with no available firmware updates: 
 • CT500P5SSD8
 • Fingerprint Sensor
 • HDMI Expansion Card
Devices with the latest available firmware version:
 • System Firmware
 • UEFI dbx
No updates available

Let me know if you need more information about my system. I am a bit puzzled as to how to solve this, and would appreciate some help. :)

Lukas

Last edited by Greenscreen23 (2025-02-24 09:13:09)

Offline

#2 2025-01-21 17:58:04

happyhyppo
Member
Registered: 2021-09-29
Posts: 2

Re: [SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

Hi, not an arch user BTW, but found this while googling and I happen to have an account for this forum, so I'm gonna try to help.

Maybe you need this:

https://community.frame.work/t/system-g … ow/61854/2

TL;DR add kernel parameter `amdgpu.dcdebugmask=0x10` (without surrounding back ticks `), and see how it goes

Last edited by happyhyppo (2025-01-21 17:58:22)

Offline

#3 2025-01-24 09:50:56

Greenscreen23
Member
Registered: 2023-03-13
Posts: 3

Re: [SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

Hi, thank you, I must have missed that post. I'll add the kernel parameter and see how it is. It sometimes took a couple of weeks for the issue to reappear, but if I haven't replied in this channel, that means it hasn't appeared yet.

Offline

#4 2025-01-24 15:46:03

seth
Member
Registered: 2012-09-03
Posts: 63,313

Re: [SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

The parameter disables PSR, fits your symptoms and has been addressed here a couple of times.

In case this ends up having fixed your problem and please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Offline

#5 2025-02-20 13:34:06

kikislater
Member
From: Mauritius
Registered: 2016-01-16
Posts: 33

Re: [SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

happyhyppo wrote:

`amdgpu.dcdebugmask=0x10`

Same happens to me suddenly in kernel 6.12.12 and this is working !

Offline

#6 2025-02-24 09:11:14

Greenscreen23
Member
Registered: 2023-03-13
Posts: 3

Re: [SOLVED] amdgpu framework [drm] dc_dmub_srv_log_diagnostic_data

The issue has not appeared to me in a month, so I will mark this as resolved for now. If it comes up again, I will note that here.

Offline

Board footer

Powered by FluxBB