From: Breno Leitao <leitao@debian.org>
To: Rik van Riel <riel@surriel.com>
Cc: Tony Luck <tony.luck@intel.com>, Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@meta.com
Subject: Re: [PATCH] x86/mce: Restore rate limit on MCE logged message
Date: Wed, 11 Nov 2026 08:35:38 -0800 [thread overview]
Message-ID: <avSZTQatplYDfHk9@gmail.com> (raw)
In-Reply-To: <20261108143751.3af49e48@fangorn>
On Sun, Nov 08, 2026 at 02:37:51PM -0500, Rik van Riel wrote:
> FCommit ea324444ece9f moved the "Machine check events logged"
> print from mce_notify_irq() into mce_log() and dropped its
> two-per-minute rate limit as a side effect.
>
> A particularly unhappy system can spew out around 100 million
> of those "Machine check events logged" messages every hour,
> without that rate limit. A large fleet may have several unhappy
> systems, leaving the netcons infrastructure somewhat flustered.
>
> Reinstate the rate limit we had before.
>
> Fixes: ea324444ece9f ("x86/mce: Restore MCA polling interval halving")
> Cc: stable@vger.kernel.org
> Signed-off-by: Rik van Riel <riel@surriel.com>
Reviewed-by: Breno Leitao <leitao@debian.org>
prev parent reply other threads:[~2026-11-11 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 19:37 [PATCH] x86/mce: Restore rate limit on MCE logged message 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
2026-11-09 21:49 ` Borislav Petkov
2026-11-10 1:25 ` Qiuxu (Leo) Zhuo
2026-11-11 16:35 ` Breno Leitao [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=avSZTQatplYDfHk9@gmail.com \
--to=leitao@debian.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qiuxu.zhuo@intel.com \
--cc=riel@surriel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.