From: Rik van Riel <riel@surriel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Luck, Tony" <tony.luck@intel.com>,
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 16:29:32 -0500 [thread overview]
Message-ID: <a799adc77dc325f5e3cd9f806dae684f198efd38.camel@surriel.com> (raw)
In-Reply-To: <20261109212305.GDavI5uXK066CxHoNA@fat_crate.local>
On Mon, 2026-11-09 at 13:23 -0800, Borislav Petkov wrote:
> On Mon, Nov 09, 2026 at 03:12:43PM -0500, Rik van Riel wrote:
> > There are a dozen or so "mce: MCE records pool full!"
> > lines, and then two of these:
> > "mce_gen_pool_add: <bignum> callbacks suppressed"
>
> Sounds to me like you getting errors logged and there's no userspace
> consumer
> at all.
>
> What is your fleet policy about collecting and logging hw errors?
>
> Do you even care about them?
We definitely care about them. Errors are used
to figure out which hosts need to be repaired.
I do not know how exactly memory errors are getting
collected. There are some tools that watch netcons,
some that collect data on the host, and some that
grab data off the BMC. I have no idea which of
those paths the memory error collection uses.
--
All Rights Reversed.
next prev parent reply other threads:[~2026-11-09 21:29 UTC|newest]
Thread overview: 8+ 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
2026-11-09 21:23 ` Borislav Petkov
2026-11-09 21:29 ` Rik van Riel [this message]
2026-11-09 21:49 ` Borislav Petkov
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=a799adc77dc325f5e3cd9f806dae684f198efd38.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®