From: Andi Kleen <ak@linux.intel.com>
To: Chen Gong <gong.chen@linux.intel.com>
Cc: x86@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/MCE: don't let EDAC bypass the handle from MCE
Date: Thu, 25 Nov 2010 10:41:44 +0100 [thread overview]
Message-ID: <4CEE2F58.3090506@linux.intel.com> (raw)
In-Reply-To: <1290674793-8346-1-git-send-email-gong.chen@linux.intel.com>
> entry = rcu_dereference_check_mce(mcelog.next);
> for (;;) {
> - /*
> - * If edac_mce is enabled, it will check the error type
> - * and will process it, if it is a known error.
> - * Otherwise, the error will be sent through mcelog
> - * interface
> - */
> - if (edac_mce_parse(mce))
> - return;
> + edac_mce_parse(mce);
The other problem with the current code is that it prints the misleading
KERN_EMERG fallback message
for every corrected error.
-Andi
prev parent reply other threads:[~2010-11-25 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-25 8:46 [PATCH] x86/MCE: don't let EDAC bypass the handle from MCE Chen Gong
2010-11-25 9:41 ` Andi Kleen [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=4CEE2F58.3090506@linux.intel.com \
--to=ak@linux.intel.com \
--cc=gong.chen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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