[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 <[email protected]>
Sent: Sunday, June 1, 2025 5:37 PM
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 Sat, May 31, 2025 at 1:13 AM Pillai, Aurabindo
<[email protected]> 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.

Reply via email to