<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<p style="font-family:Calibri;font-size:10pt;color:#0000FF;margin:5pt;font-style:normal;font-weight:normal;text-decoration:none;" align="Left">
[AMD Official Use Only - AMD Internal Distribution Only]<br>
</p>
<br>
<div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Hi Mike,</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
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.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature" class="elementToProof">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
--</div>
<div class="elementToProof" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div class="elementToProof" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Jay<br>
</div>
</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com><br>
<b>Sent:</b> Sunday, June 1, 2025 5:37 PM<br>
<b>To:</b> Pillai, Aurabindo <Aurabindo.Pillai@amd.com><br>
<b>Cc:</b> Chung, ChiaHsuan (Tom) <ChiaHsuan.Chung@amd.com>; Wu, Ray <Ray.Wu@amd.com>; Wheeler, Daniel <Daniel.Wheeler@amd.com>; Deucher, Alexander <Alexander.Deucher@amd.com>; amd-gfx list <amd-gfx@lists.freedesktop.org>; dri-devel <dri-devel@lists.freedesktop.org>;
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>; Linux regressions mailing list <regressions@lists.linux.dev><br>
<b>Subject:</b> Re: 6.15-rc6/regression/bisected - after commit f1c6be3999d2 error appeared: *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">On Sat, May 31, 2025 at 1:13 AM Pillai, Aurabindo<br>
<Aurabindo.Pillai@amd.com> wrote:<br>
><br>
> [AMD Official Use Only - AMD Internal Distribution Only]<br>
><br>
><br>
> Hi Mike,<br>
><br>
> Thanks for the logs. I've reverted the patch in amd-staging-drm-next and also sent the patch to the stable list.<br>
><br>
> 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<br>
<br>
Hi Aurabindo,<br>
<br>
I’ve attached the amdgpu_dm_dmub_tracebuffer and the full kernel log<br>
captured after the hang on the 6900XT.<br>
<br>
Let me know if you need any additional data or testing.<br>
<br>
-- <br>
Best Regards,<br>
Mike Gavrilov.<br>
</div>
</span></font></div>
</div>
</body>
</html>