From: "Luck, Tony" <tony.luck@intel•com>
To: Yazen Ghannam <yazen.ghannam@amd•com>,
Nikolay Borisov <nik.borisov@suse•com>
Cc: Bert Karwatzki <spasswolf@web•de>, Borislav Petkov <bp@alien8•de>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-next@vger•kernel.org" <linux-next@vger•kernel.org>,
"linux-edac@vger•kernel.org" <linux-edac@vger•kernel.org>,
"linux-acpi@vger•kernel.org" <linux-acpi@vger•kernel.org>,
"x86@kernel•org" <x86@kernel•org>,
"rafael@kernel•org" <rafael@kernel•org>,
"Zhuo, Qiuxu" <qiuxu.zhuo@intel•com>,
"Smita.KoralahalliChannabasappa@amd•com"
<Smita.KoralahalliChannabasappa@amd•com>
Subject: RE: spurious mce Hardware Error messages in next-20250912
Date: Thu, 18 Sep 2025 21:04:53 +0000 [thread overview]
Message-ID: <SJ1PR11MB608353C84F69E8EC0D6744ECFC16A@SJ1PR11MB6083.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20250918210005.GA2150610@yaz-khff2.amd.com>
> For the current issue, it does seem that the registers contain junk
> values. And we are only now seeing this with the recent rework.
Do you try to clear these registers after logging? Or just rely on clearing
the MCi_STATUS register?
If you are clearing, then it isn't working (or new junk values appear quickly).
-Tony
next prev parent reply other threads:[~2025-09-18 21:04 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
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 [this message]
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=SJ1PR11MB608353C84F69E8EC0D6744ECFC16A@SJ1PR11MB6083.namprd11.prod.outlook.com \
--to=tony.luck@intel$(echo .)com \
--cc=Smita.KoralahalliChannabasappa@amd$(echo .)com \
--cc=bp@alien8$(echo .)de \
--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=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