[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250916091055.GAaMkpn72GrFnsueCF@fat_crate.local>
Date: Tue, 16 Sep 2025 11:10:55 +0200
From: Borislav Petkov <bp@...en8.de>
To: Bert Karwatzki <spasswolf@....de>,
Yazen Ghannam <yazen.ghannam@....com>
Cc: Tony Luck <tony.luck@...el.com>, linux-kernel@...r.kernel.org,
linux-next@...r.kernel.org, linux-edac@...r.kernel.org,
linux-acpi@...r.kernel.org, x86@...nel.org, rafael@...nel.org,
qiuxu.zhuo@...el.com, nik.borisov@...e.com,
Smita.KoralahalliChannabasappa@....com
Subject: Re: spurious mce Hardware Error messages in next-20250912
On Mon, Sep 15, 2025 at 11:43:26PM +0200, Bert Karwatzki wrote:
> After re-cloning linux-next I tested next-20250911 and I get no mce error messages
> even if I set the check_interval to 10.
Yazen, I've zapped everything from the handler unification onwards:
28e82d6f03b0 x86/mce: Save and use APEI corrected threshold limit
c8f4cea38959 x86/mce: Handle AMD threshold interrupt storms
5a92e88ffc49 x86/mce/amd: Define threshold restart function for banks
922300abd79d x86/mce/amd: Remove redundant reset_block()
9b92e18973ce x86/mce/amd: Support SMCA corrected error interrupt
fe02d3d00b06 x86/mce/amd: Enable interrupt vectors once per-CPU on SMCA systems
cf6f155e848b x86/mce: Unify AMD DFR handler with MCA Polling
53b3be0e79ef x86/mce: Unify AMD THR handler with MCA Polling
until this is properly sorted out, now this close to the merge window.
Thanks, Bert, for reporting!
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists