<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've reverted the patch in amd-staging-drm-next and also sent the patch to the stable list.</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);">
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</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" style="color: inherit;">
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
--</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regards,</div>
<div 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> Friday, May 30, 2025 3:59 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 Fri, May 30, 2025 at 6:48 PM 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>
> 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.<br>
> 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.<br>
<br>
Hi Aurabindo,<br>
<br>
With drm.debug=0x116, I was able to capture the DMCUB error on the<br>
7900XTX even during system boot.<br>
Here’s a snippet from the log:<br>
<br>
[ 140.307960] amdgpu 0000:03:00.0: [drm:drm_atomic_state_init]<br>
Allocated atomic state 000000003bcb4982<br>
[ 140.307978] amdgpu 0000:03:00.0: [drm:drm_atomic_get_plane_state]<br>
Added [PLANE:77:plane-6] 00000000d20ccca3 state to 000000003bcb4982<br>
[ 140.307985] amdgpu 0000:03:00.0: [drm:drm_atomic_get_crtc_state]<br>
Added [CRTC:80:crtc-0] 00000000267a47e8 state to 000000003bcb4982<br>
[ 140.307992] amdgpu 0000:03:00.0: [drm:drm_atomic_set_fb_for_plane]<br>
Set [FB:132] for [PLANE:77:plane-6] state 00000000d20ccca3<br>
[ 140.308214] amdgpu 0000:03:00.0: [drm:drm_mode_addfb2] [FB:134]<br>
[ 140.506110] amdgpu 0000:03:00.0: [drm:dc_dmub_srv_wait_for_idle<br>
[amdgpu]] No reply for DMUB command: status=3<br>
[ 140.506572] amdgpu 0000:03:00.0: [drm] *ERROR*<br>
dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic<br>
data<br>
[ 140.506605] amdgpu 0000:03:00.0:<br>
[drm:dc_dmub_srv_log_diagnostic_data [amdgpu]] DMCUB STATE:<br>
[ 140.507065] amdgpu 0000:03:00.0:<br>
[drm:dc_dmub_srv_log_diagnostic_data [amdgpu]] dmcub_version<br>
: 07002d00<br>
[ 140.507500] amdgpu 0000:03:00.0:<br>
[drm:dc_dmub_srv_log_diagnostic_data [amdgpu]] scratch [0]<br>
: 00000003<br>
[ 140.507924] amdgpu 0000:03:00.0:<br>
[drm:dc_dmub_srv_log_diagnostic_data [amdgpu]] scratch [1]<br>
: 07002d00<br>
[ 140.508341] amdgpu 0000:03:00.0:<br>
[drm:dc_dmub_srv_log_diagnostic_data [amdgpu]] scratch [2]<br>
: 00000000<br>
[ 140.508591] amdgpu 0000:03:00.0: [drm:dc_dmub_srv_wait_for_idle<br>
[amdgpu]] No reply for DMUB command: status=3<br>
[ 140.508944] amdgpu 0000:03:00.0: [drm] *ERROR*<br>
dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic<br>
data<br>
<br>
><br>
> 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.<br>
<br>
Yes, the issue was fully resolved by reverting commit f1c6be3999d2.<br>
<br>
I’ve attached the full kernel log below.<br>
<br>
-- <br>
Best Regards,<br>
Mike Gavrilov.<br>
</div>
</span></font></div>
</div>
</body>
</html>