6.15-rc6/regression/bisected - after commit f1c6be3999d2 error appeared: *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error

[Pillai, Aurabindo]

[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.gavrilov at gmail.com>
Sent: Sunday, June 1, 2025 5:37 PM
To: Pillai, Aurabindo <Aurabindo.Pillai at amd.com>
Cc: Chung, ChiaHsuan (Tom) <ChiaHsuan.Chung at amd.com>; Wu, Ray <Ray.Wu at amd.com>; Wheeler, Daniel <Daniel.Wheeler at amd.com>; Deucher, Alexander <Alexander.Deucher at amd.com>; amd-gfx list <amd-gfx at lists.freedesktop.org>; dri-devel <dri-devel at lists.freedesktop.org>; Linux List Kernel Mailing <linux-kernel at vger.kernel.org>; Linux regressions mailing list <regressions at 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.Pillai at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20250602/3a0284be/attachment-0001.htm>