public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Yazen Ghannam <yazen.ghannam@amd.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Nikolay Borisov <nik.borisov@suse.com>,
	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 17:14:05 -0400	[thread overview]
Message-ID: <20250918211405.GA2180898@yaz-khff2.amd.com> (raw)
In-Reply-To: <SJ1PR11MB608353C84F69E8EC0D6744ECFC16A@SJ1PR11MB6083.namprd11.prod.outlook.com>

On Thu, Sep 18, 2025 at 09:04:53PM +0000, Luck, Tony wrote:
> > 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?
> 

Yes, the MCA_DESTAT register is cleared in a couple of places depending
on the scenario.

> If you are clearing, then it isn't working (or new junk values appear quickly).

Right, and MCi_STATUS has junk values in some of the affected banks.
They just happen to be ignored because they don't have the Valid bit
set.

And MCi_STATUS is cleared at Linux init time, so the junk values stick
or come back by the time Bert ran the script.

Thanks,
Yazen

  reply	other threads:[~2025-09-18 21:14 UTC|newest]

Thread overview: 27+ 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
2025-09-18 21:14                           ` Yazen Ghannam [this message]
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

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=20250918211405.GA2180898@yaz-khff2.amd.com \
    --to=yazen.ghannam@amd.com \
    --cc=Smita.KoralahalliChannabasappa@amd.com \
    --cc=bp@alien8.de \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nik.borisov@suse.com \
    --cc=qiuxu.zhuo@intel.com \
    --cc=rafael@kernel.org \
    --cc=spasswolf@web.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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