From: Bert Karwatzki <spasswolf@web.de>
To: Mario Limonciello <mario.limonciello@amd.com>,
Yazen Ghannam <yazen.ghannam@amd.com>
Cc: Nikolay Borisov <nik.borisov@suse.com>,
spasswolf@web.de, Borislav Petkov <bp@alien8.de>,
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,
Smita.KoralahalliChannabasappa@amd.com
Subject: Re: spurious (?) mce Hardware Error messages in v6.19
Date: Fri, 20 Feb 2026 19:24:32 +0100 [thread overview]
Message-ID: <290ee50cbe68d246a9899b03d5c7ddebc549f0bf.camel@web.de> (raw)
In-Reply-To: <8530d765-6676-4ba4-98b5-07326c8dc924@amd.com>
Am Freitag, dem 20.02.2026 um 10:49 -0600 schrieb Mario Limonciello:
>
> On 2/19/2026 9:43 AM, Bert Karwatzki wrote:
> > Am Donnerstag, dem 19.02.2026 um 09:33 -0500 schrieb Yazen Ghannam:
> > > On Mon, Feb 16, 2026 at 03:25:46PM -0500, Yazen Ghannam wrote:
> > > > On Thu, Feb 12, 2026 at 01:50:05PM +0100, Bert Karwatzki wrote:
> > >
> > > [...]
> > >
> > > > >
> > > > > 2026-02-10T16:15:01.001203+01:00 lisa kernel: [ C0] smca_should_log_poll_error: 1
> > > > > 2026-02-10T16:15:01.001815+01:00 lisa kernel: [T45426] mce: [Hardware Error]: Machine check events logged
> > > > > 2026-02-10T16:15:01.001818+01:00 lisa kernel: [T45426] [Hardware Error]: Deferred error, no action required.
> > > > > 2026-02-10T16:15:01.001819+01:00 lisa kernel: [T45426] [Hardware Error]: CPU:0 (19:50:0) MC14_STATUS[-|-|-|AddrV|PCC|-|-|Deferred|-|-]: 0x8700900800000000
> > >
> > > Hi Bert,
> > >
> > > The CPU stepping indicates that this isn't a production model.
> > >
> > > Can you please share more info on your system? Is it a production laptop
> > > or a pre-production sample?
> > >
> > > Thanks,
> > > Yazenit
> >
> > As far as I know is a production Laptop, a MSI Alpha 15 B5EEK/MS-158L model with
> > bios version "BIOS E158LAMS.10F 11/11/2024" (the newest version available at
> > https://de.msi.com/Laptop/Alpha-15-B5EX/support?sku_id=89840) and without
> > preinstalled Windows which I bought in December 2021 at www.alternate.de (a shop
> > which MSI lists as a "trusted partner": https://de.msi.com/service/bzq)
> >
> > Bert Karwatzki
>
> Do you know if it was purchased "right around" when it launched? I'm
> wondering if it's possible they used pre-production parts for some
> reason with their initial systems.
>
> The reason for this line of inquiry is if this is what we would have
> considered pre-production silicon, it might be more appropriate to flag
> the CPU accordingly and ignore these MCEs.
Yes, I bought right when it became available.
Bert Karwatzki
next prev parent reply other threads:[~2026-02-20 18:24 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
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 [this message]
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=290ee50cbe68d246a9899b03d5c7ddebc549f0bf.camel@web.de \
--to=spasswolf@web.de \
--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=mario.limonciello@amd.com \
--cc=nik.borisov@suse.com \
--cc=qiuxu.zhuo@intel.com \
--cc=rafael@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@kernel.org \
--cc=yazen.ghannam@amd.com \
/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