[AMD Official Use Only - AMD Internal Distribution Only] Hi Mike,
We were trying to see if we can repro the issue on newer cards as well, but it seems only 6000 series can repro at our end. If you can repro more easily on other cards, please add "drm.debug=0x116 log_buf_len=20M" to your kernel cmdline and grab the dmesg please. I'd also like to know if your issue is fully resolved if "drm/amd/display: more liberal vmin/vmax update for freesync" is reverted. -- Regards, Jay ________________________________ From: Mikhail Gavrilov <[email protected]> Sent: Friday, May 30, 2025 2:34 AM To: Pillai, Aurabindo <[email protected]> Cc: Chung, ChiaHsuan (Tom) <[email protected]>; Wu, Ray <[email protected]>; Wheeler, Daniel <[email protected]>; Deucher, Alexander <[email protected]>; amd-gfx list <[email protected]>; dri-devel <[email protected]>; Linux List Kernel Mailing <[email protected]>; Linux regressions mailing list <[email protected]> Subject: Re: 6.15-rc6/regression/bisected - after commit f1c6be3999d2 error appeared: *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error On Mon, May 26, 2025 at 10:50 PM Pillai, Aurabindo <[email protected]> wrote: > > [AMD Official Use Only - AMD Internal Distribution Only] > > > Hi Mike, > > It is indeed a bit harder, but we were able to repro the issue on the 6000 > series. I'll need to get the DMCUB trace log to confirm, but it looks like an > SMU hang from within DMCUB. So we'd need more debugging to find out whats > going wrong from SMU side. Meanwhile, I've reverted > 219898d29c438d8ec34a5560fac4ea8f6b8d4f20 that triggered the issue for a lot > of them. Hi Aurabindo, 219898d29c438d8ec34a5560fac4ea8f6b8d4f20? Just to clarify - I’m currently running on 6.16-rc0 (90b83efa6701), and I still see the following constantly spamming the log on 7900XTX: amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data Let me know if you need me to capture any additional traces or logs. -- Best Regards, Mike Gavrilov.
