From: Borislav Petkov <bp@alien8•de>
To: Bert Karwatzki <spasswolf@web•de>, Yazen Ghannam <yazen.ghannam@amd•com>
Cc: Tony Luck <tony.luck@intel•com>,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
linux-edac@vger•kernel.org, linux-acpi@vger•kernel.org,
x86@kernel•org, rafael@kernel•org, qiuxu.zhuo@intel•com,
nik.borisov@suse•com, Smita.KoralahalliChannabasappa@amd•com
Subject: Re: spurious mce Hardware Error messages in next-20250912
Date: Tue, 16 Sep 2025 11:10:55 +0200 [thread overview]
Message-ID: <20250916091055.GAaMkpn72GrFnsueCF@fat_crate.local> (raw)
In-Reply-To: <426097525d5f9e88a3f7e96ce93f24ca27459f90.camel@web.de>
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
next prev parent reply other threads:[~2025-09-16 9:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 1:00 spurious mce Hardware Error messages in next-20250912 Bert Karwatzki
2025-09-15 17:55 ` Yazen Ghannam
2025-09-15 21:03 ` Bert Karwatzki
2025-09-15 21:43 ` Bert Karwatzki
2025-09-16 9:10 ` Borislav Petkov [this message]
2025-09-16 14:07 ` Yazen Ghannam
2025-09-16 20:27 ` Bert Karwatzki
2025-09-17 7:13 ` Bert Karwatzki
2025-09-17 14:41 ` Yazen Ghannam
2025-09-17 15:33 ` Bert Karwatzki
2025-09-17 19:26 ` Yazen Ghannam
2025-09-17 21:15 ` Yazen Ghannam
2025-09-17 22:01 ` Bert Karwatzki
2025-09-18 10:20 ` Nikolay Borisov
2025-09-18 21:00 ` Yazen Ghannam
2025-09-18 21:04 ` Luck, Tony
2025-09-18 21:14 ` Yazen Ghannam
2025-09-18 22:07 ` Bert Karwatzki
2025-10-09 13:20 ` Yazen Ghannam
2026-02-12 12:50 ` spurious (?) mce Hardware Error messages in v6.19 Bert Karwatzki
2026-02-13 12:45 ` Bert Karwatzki
2026-02-16 20:25 ` Yazen Ghannam
2026-02-19 14:33 ` Yazen Ghannam
2026-02-19 15:43 ` Bert Karwatzki
2026-02-20 16:49 ` Mario Limonciello
2026-02-20 18:24 ` Bert Karwatzki
2026-02-23 21:53 ` Yazen Ghannam
2026-04-03 14:05 ` Borislav Petkov
2026-04-05 8:47 ` Bert Karwatzki
2026-04-05 10:46 ` Borislav Petkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250916091055.GAaMkpn72GrFnsueCF@fat_crate.local \
--to=bp@alien8$(echo .)de \
--cc=Smita.KoralahalliChannabasappa@amd$(echo .)com \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-edac@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nik.borisov@suse$(echo .)com \
--cc=qiuxu.zhuo@intel$(echo .)com \
--cc=rafael@kernel$(echo .)org \
--cc=spasswolf@web$(echo .)de \
--cc=tony.luck@intel$(echo .)com \
--cc=x86@kernel$(echo .)org \
--cc=yazen.ghannam@amd$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox