[AMD Official Use Only - AMD Internal Distribution Only] Hi Mike,
Thanks for the logs. I can confirm that there is an SMU hang from within DMCUB firmware. We'll debug this further with another team and get back to you. -- Regards, Jay ________________________________ From: Mikhail Gavrilov <mikhail.v.gavri...@gmail.com> Sent: Sunday, June 1, 2025 5:37 PM To: Pillai, Aurabindo <aurabindo.pil...@amd.com> Cc: Chung, ChiaHsuan (Tom) <chiahsuan.ch...@amd.com>; Wu, Ray <ray...@amd.com>; Wheeler, Daniel <daniel.whee...@amd.com>; Deucher, Alexander <alexander.deuc...@amd.com>; amd-gfx list <amd-...@lists.freedesktop.org>; dri-devel <dri-devel@lists.freedesktop.org>; Linux List Kernel Mailing <linux-ker...@vger.kernel.org>; Linux regressions mailing list <regressi...@lists.linux.dev> Subject: Re: 6.15-rc6/regression/bisected - after commit f1c6be3999d2 error appeared: *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error On Sat, May 31, 2025 at 1:13 AM Pillai, Aurabindo <aurabindo.pil...@amd.com> wrote: > > [AMD Official Use Only - AMD Internal Distribution Only] > > > Hi Mike, > > Thanks for the logs. I've reverted the patch in amd-staging-drm-next and also > sent the patch to the stable list. > > If its possible, please also collect the dmcub trace log (cat > /sys/kernel/debug/dri/0/amdgpu_dm_dmub_tracebuffer) after the hang. Its > usually dri/0 or dri/1 folder Hi Aurabindo, I’ve attached the amdgpu_dm_dmub_tracebuffer and the full kernel log captured after the hang on the 6900XT. Let me know if you need any additional data or testing. -- Best Regards, Mike Gavrilov.
