From: Rik van Riel <riel@surriel.com>
To: Borislav Petkov <bp@alien8.de>, "Luck, Tony" <tony.luck@intel.com>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-team@meta.com" <kernel-team@meta.com>,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] x86/mce: Restore rate limit on MCE logged message
Date: Mon, 09 Nov 2026 15:12:43 -0500 [thread overview]
Message-ID: <63ed91b49db00d7a601b8ae1625571ee0c46ffca.camel@surriel.com> (raw)
In-Reply-To: <20261109195216.GBavIkcPlh-HcT_7JW@fat_crate.local>
On Mon, 2026-11-09 at 11:52 -0800, Borislav Petkov wrote:
> On Mon, Nov 09, 2026 at 05:54:34PM +0000, Luck, Tony wrote:
> > mce_log() is called from the interrupt.
>
> Aha, through machine_check_poll(). Let's hear from Rik first tho.
Not only the poll path, but also the #MC exception
handler.
exc_machine_check
--> exc_machine_check_{kernel,user}
--> do_machine_check
--> mce_log
--> pr_info("Machine check events logged")
As for the dmesg, it is almost entirely filled
with "Machine check events logged" errors, at
a rate of about 100 million an hour.
There are a dozen or so "mce: MCE records pool full!"
lines, and then two of these:
"mce_gen_pool_add: <bignum> callbacks suppressed"
I suspect there isn't anything special about the
kernel here, we are just looking at some unusually
broken hardware, which will be present in a fleet
this size.
--
All Rights Reversed.
prev parent reply other threads:[~2026-11-09 20:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 19:37 Rik van Riel
2026-11-08 20:28 ` Borislav Petkov
2026-11-09 17:54 ` Luck, Tony
2026-11-09 19:52 ` Borislav Petkov
2026-11-09 20:12 ` Rik van Riel [this message]
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=63ed91b49db00d7a601b8ae1625571ee0c46ffca.camel@surriel.com \
--to=riel@surriel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qiuxu.zhuo@intel.com \
--cc=tglx@kernel.org \
--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
all inboxes | Powered by JetHome®