[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SJ1PR11MB608353C84F69E8EC0D6744ECFC16A@SJ1PR11MB6083.namprd11.prod.outlook.com>
Date: Thu, 18 Sep 2025 21:04:53 +0000
From: "Luck, Tony" <tony.luck@...el.com>
To: Yazen Ghannam <yazen.ghannam@....com>, Nikolay Borisov
<nik.borisov@...e.com>
CC: Bert Karwatzki <spasswolf@....de>, Borislav Petkov <bp@...en8.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-edac@...r.kernel.org" <linux-edac@...r.kernel.org>,
"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>, "x86@...nel.org"
<x86@...nel.org>, "rafael@...nel.org" <rafael@...nel.org>, "Zhuo, Qiuxu"
<qiuxu.zhuo@...el.com>, "Smita.KoralahalliChannabasappa@....com"
<Smita.KoralahalliChannabasappa@....com>
Subject: RE: spurious mce Hardware Error messages in next-20250912
> 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
Powered by blists - more mailing lists