Re: spurious mce Hardware Error messages in next-20250912

[Yazen Ghannam]

On Tue, Sep 16, 2025 at 11:10:55AM +0200, Borislav Petkov wrote:
> 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!
> 

No problem, thanks Boris.

Bert, can you please try the following patch on next-20250912?

I expect that you will see the "debug" message, but the regular MCA
logging should be gone.

Also, we haven't been able to reproduce this issue yet. So thank you for
your help. It's much appreciated.

Thanks,
Yazen