All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Borislav Petkov <bp@amd64.org>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Tony Luck <tony.luck@intel.com>,
	EDAC devel <linux-edac@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Prarit Bhargava <prarit@redhat.com>,
	Nagananda Chumbalkar <Nagananda.Chumbalkar@hp.com>,
	Russ Anderson <rja@sgi.com>
Subject: Re: [PATCH -v2 2/2] x86, MCE: Drop the default decoding notifier
Date: Tue, 26 Apr 2011 09:42:38 +0200	[thread overview]
Message-ID: <20110426074238.GA22448@aftab> (raw)
In-Reply-To: <m1hb9mnmqs.fsf@fess.ebiederm.org>

On Mon, Apr 25, 2011 at 03:40:11PM -0400, Eric W. Biederman wrote:
> > From: Borislav Petkov <borislav.petkov@amd.com>
> > Date: Wed, 13 Apr 2011 14:32:06 +0200
> > Subject: [PATCH -v2.1 2/2] x86, MCE: Drop the default decoding notifier
> >
> > The default notifier doesn't make a lot of sense to call in the
> > correctable errors case. Drop it and emit the mcelog decoding hint only
> > in the uncorrectable errors case and when no notifier is registered.
> > Also, limit issuing the "mcelog --ascii" message in the rare case when
> > we dump unreported CEs before panicking.
> >
> > While at it, remove unused old x86_mce_decode_callback from the
> > header.
> 
> Can we please print something if we please log something in the
> case of a correctable error, when we only report it via mcelog?
> 
> I have a stupid recent intel cpu here that hits that case and without
> the default x86_mce_decode_callback I wouldn't have even known that I am
> getting something like 50 correctable errors an hour on one of my
> machines.  In particular I am it hits so often I am seeing:
> "mce_notify_irq: 2 callbacks suppressed".  I need to get those dimms
> replaced soon because in a new product I simply can't imagine that many
> correctable errors.

Isn't there a mcelog daemon or something that polls /dev/mcelog and
tells you about those DRAM ECCs in some log file where you're supposed
to look? :)

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-04-26  7:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18 14:00 [PATCH -v2 2/2] x86, MCE: Drop the default decoding notifier Borislav Petkov
2011-04-19 17:13 ` Ingo Molnar
2011-04-19 17:35   ` Borislav Petkov
2011-04-19 17:44     ` Ingo Molnar
2011-04-20 10:23       ` Borislav Petkov
2011-04-21 12:10         ` [tip:x86/mce] x86, mce: " tip-bot for Borislav Petkov
2011-04-25 19:40         ` [PATCH -v2 2/2] x86, MCE: " Eric W. Biederman
2011-04-26  7:42           ` Borislav Petkov [this message]
2011-04-26 21:06             ` Eric W. Biederman
2011-04-26 21:47               ` Borislav Petkov
2011-04-26 22:26                 ` Eric W. Biederman
2011-04-26 23:44                   ` Luck, Tony
2011-04-27 14:03                     ` Borislav Petkov
2011-04-26 22:32               ` Russ Anderson

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=20110426074238.GA22448@aftab \
    --to=bp@amd64.org \
    --cc=Nagananda.Chumbalkar@hp.com \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=prarit@redhat.com \
    --cc=rja@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.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 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.