From: Tyler Hicks <email@example.com>
To: Borislav Petkov <firstname.lastname@example.org>
Cc: wangglei <email@example.com>,
"Lei Wang (DPLAT)" <Wang.Lei@microsoft.com>,
Hang Li <firstname.lastname@example.org>,
Brandon Waller <email@example.com>
Subject: Re: [EXTERNAL] Re: [PATCH] EDAC: update edac printk wrappers to use printk_ratelimited.
Date: Wed, 5 May 2021 17:43:57 -0500 [thread overview]
Message-ID: <20210505224357.GG4967@sequoia> (raw)
On 2021-05-05 17:16:11, Tyler Hicks wrote:
> On 2021-05-06 00:02:44, Borislav Petkov wrote:
> > On Wed, May 05, 2021 at 04:48:46PM -0500, Tyler Hicks wrote:
> > > The thought was that the full stream of log messages isn't necessary to
> > > notice that there's a problem when they are being emitted at such a high
> > > rate (500 per second). They're just filling up disk space and/or wasting
> > > networking bandwidth at that point.
> > I already asked about this but lemme point it out again: have you guys
> > looked at drivers/ras/cec.c ?
> We'll have a closer look. Thanks for the pointer!
This is x86-specific and not applicable in our situation.
> > With that there won't be *any* error reports in dmesg and it will even
> > poison and offline pages which generate excessive errors so that ...
> > > Of course, the best course of action here is to service the machine
> > > but there's still a period of time between the CE errors popping up
> > > and the machine being serviced.
> > ... you'll have ample time to service the machine.
> > --
> > Regards/Gruss,
> > Boris.
> > https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-05-05 22:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 17:30 [PATCH] EDAC: update edac printk wrappers to use printk_ratelimited Lei Wang
2021-05-05 18:01 ` Borislav Petkov
2021-05-05 19:02 ` [EXTERNAL] " Lei Wang (DPLAT)
2021-05-05 19:45 ` Borislav Petkov
2021-05-05 20:23 ` Tyler Hicks
2021-05-05 21:04 ` Borislav Petkov
2021-05-05 21:48 ` Tyler Hicks
2021-05-05 22:02 ` Borislav Petkov
2021-05-05 22:16 ` Tyler Hicks
2021-05-05 22:43 ` Tyler Hicks [this message]
2021-05-05 22:55 ` Borislav Petkov
2021-05-05 23:01 ` Tyler Hicks
2021-05-05 23:13 ` Luck, Tony
2021-05-06 7:16 ` Mauro Carvalho Chehab
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).