[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <426097525d5f9e88a3f7e96ce93f24ca27459f90.camel@web.de>
Date: Mon, 15 Sep 2025 23:43:26 +0200
From: Bert Karwatzki <spasswolf@....de>
To: Yazen Ghannam <yazen.ghannam@....com>
Cc: Borislav Petkov <bp@...en8.de>, Tony Luck <tony.luck@...el.com>,
linux-kernel@...r.kernel.org, linux-next@...r.kernel.org,
linux-edac@...r.kernel.org, linux-acpi@...r.kernel.org, x86@...nel.org,
rafael@...nel.org, qiuxu.zhuo@...el.com, nik.borisov@...e.com,
Smita.KoralahalliChannabasappa@....com, spasswolf@....de
Subject: Re: spurious mce Hardware Error messages in next-20250912
Am Montag, dem 15.09.2025 um 23:03 +0200 schrieb Bert Karwatzki:
> Am Montag, dem 15.09.2025 um 13:55 -0400 schrieb Yazen Ghannam:
>
> > >
> > > As these messages do not appear in v6.17-rc5 I bisected the issue
> > > (from v6.17-rc5 to next-20250912) and found this as the first bad commit:
> > >
> > > cf6f155e848b ("x86/mce: Unify AMD DFR handler with MCA Polling")
> >
> > Could you try another recent linux-next build without the MCA updates?
> >
> >
> >
> > It looks like 'next-20250911' doesn't include the commit above.
> > >
>
> Somehow I cannot find next-20250911 in my linux-next git:
>
> $ git checkout next-202509(TAB TAB)
> next-20250901 next-20250902 next-20250905 next-20250908 next-20250912
>
> I'm currently re-cloning linux-next.
>
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.
Bert Karwatzki
> >
Powered by blists - more mailing lists