From: Jason Baron <jbaron@akamai.com>
To: Borislav Petkov <bp@alien8.de>,
Raymond Bennett <raymond.bennett@gmail.com>
Cc: linux-edac@vger.kernel.org
Subject: Re: Constant output in syslog of EDAC message
Date: Mon, 19 Oct 2020 17:25:43 -0400 [thread overview]
Message-ID: <e0fda286-d8e3-dabb-6cf5-fcd974e048b5@akamai.com> (raw)
In-Reply-To: <20201019205658.GI24325@zn.tnic>
On 10/19/20 4:56 PM, Borislav Petkov wrote:
> On Mon, Oct 19, 2020 at 01:37:16PM -0700, Raymond Bennett wrote:
>> Hi,
>>
>> I am seeing the constant output of the following messages in syslog,
>> wondering what I can do to resolve this:
>>
>> Oct 19 13:19:30 hostname kernel: EDAC DEBUG: ie31200_check: MC0
> Looks like a debugging leftover. I'll remove it soon unless Jason (CCed)
> screams.
>
> Leaving in the rest for him.
Hi,
Yes, I likely was just following what was in other edac drivers at
the time - for example, i3200_check() has a similar debug. I guess
it could have a higher level. But if we remove this one, we may
want to audit some of the other edac drivers as well.
Thanks,
-Jason
>
>> It outputs about once every second.
>>
>> uname -a
>> Linux hostname 5.9.0-991.native #1 SMP Mon Oct 12 08:10:54 PDT 2020
>> x86_64 GNU/Linux
>>
>> /proc/cpuinfo
>> processor : 7
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 158
>> model name : Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz
>> stepping : 9
>> microcode : 0xd6
next prev parent reply other threads:[~2020-10-19 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 20:37 Constant output in syslog of EDAC message Raymond Bennett
2020-10-19 20:56 ` Borislav Petkov
2020-10-19 21:25 ` Jason Baron [this message]
2020-10-20 9:19 ` Borislav Petkov
2020-10-26 12:04 ` [PATCH] EDAC: Do not issue useless debug statements in the polling routine Borislav Petkov
2020-10-26 17:47 ` Constant output in syslog of EDAC message Jason Baron
2020-10-26 18:10 ` Borislav Petkov
2020-10-26 20:52 ` Jason Baron
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=e0fda286-d8e3-dabb-6cf5-fcd974e048b5@akamai.com \
--to=jbaron@akamai.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=raymond.bennett@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).