[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CABXGCsN5uR+t76b-fHkEw9+G-uHOkOunznZOHh5R-HFJP=9Zgw@mail.gmail.com>
Date: Fri, 30 May 2025 11:34:32 +0500
From: Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>
To: "Pillai, Aurabindo" <Aurabindo.Pillai@....com>
Cc: "Chung, ChiaHsuan (Tom)" <ChiaHsuan.Chung@....com>, "Wu, Ray" <Ray.Wu@....com>,
"Wheeler, Daniel" <Daniel.Wheeler@....com>, "Deucher, Alexander" <Alexander.Deucher@....com>,
amd-gfx list <amd-gfx@...ts.freedesktop.org>, dri-devel <dri-devel@...ts.freedesktop.org>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>
Subject: Re: 6.15-rc6/regression/bisected - after commit f1c6be3999d2 error
appeared: *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error
On Mon, May 26, 2025 at 10:50 PM Pillai, Aurabindo
<Aurabindo.Pillai@....com> wrote:
>
> [AMD Official Use Only - AMD Internal Distribution Only]
>
>
> Hi Mike,
>
> It is indeed a bit harder, but we were able to repro the issue on the 6000 series. I'll need to get the DMCUB trace log to confirm, but it looks like an SMU hang from within DMCUB. So we'd need more debugging to find out whats going wrong from SMU side. Meanwhile, I've reverted 219898d29c438d8ec34a5560fac4ea8f6b8d4f20 that triggered the issue for a lot of them.
Hi Aurabindo,
219898d29c438d8ec34a5560fac4ea8f6b8d4f20?
Just to clarify - I’m currently running on 6.16-rc0 (90b83efa6701), and
I still see the following constantly spamming the log on 7900XTX:
amdgpu 0000:03:00.0: [drm] *ERROR* dc_dmub_srv_log_diagnostic_data:
DMCUB error - collecting diagnostic data
Let me know if you need me to capture any additional traces or logs.
--
Best Regards,
Mike Gavrilov.
Download attachment "dmesg.zip" of type "application/zip" (48656 bytes)
Powered by blists - more mailing lists