public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Tobias Karnat <tobias.karnat@googlemail.com>
Cc: "linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Doug Thompson <norsk5@yahoo.com>
Subject: Re: edac_core: crashes on shutdown
Date: Thu, 2 Dec 2010 19:37:24 +0100	[thread overview]
Message-ID: <20101202183724.GH27263@aftab> (raw)
In-Reply-To: <1291313101.5563.13.camel@Tobias-Karnat>

On Thu, Dec 02, 2010 at 01:05:01PM -0500, Tobias Karnat wrote:
> This patch fixed it.
> I have rebooted five times and it does not crash anymore.
> 
> Thank you.

Thanks for testing and taking pictures :). I'll send it to Linus before
.37 is out.

> Btw, are there any information available regarding the NMI option?
> 
> parm:	edac_op_state:EDAC Error Reporting state: 0=Poll,1=NMI (int)
> 
> In edac.txt NMI is listed under FUTURE HARDWARE SCANNING.

Well, looking at <arch/x86/kernel/traps.c:mem_parity_error()> this
should already work. But it is kinda of a hack, if I'm reading Doug
correctly: http://lkml.org/lkml/2010/9/21/144

And yes, using some kind of an interrupt is much better than polling but
I don't know whether there's a single interrupt source for the error
types all edac drivers can decode and report. In the amd64_edac case,
we're piggybacking on MCE, for example. This was actually the initial
reason for 00740c58541b6087d78418cebca1fcb86dc6077d and dropping polling
from that driver.

Doug, any additions?

-- 
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:[~2010-12-02 18:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-01 11:01 edac_core: crashes on shutdown Tobias Karnat
2010-12-01 12:39 ` Borislav Petkov
2010-12-01 13:24   ` Tobias Karnat
2010-12-01 14:33     ` Borislav Petkov
2010-12-01 17:46       ` Tobias Karnat
2010-12-01 19:35         ` Borislav Petkov
2010-12-02  9:03           ` Tobias Karnat
2010-12-02 14:51             ` Florian Mickler
2010-12-02 14:52               ` Florian Mickler
2010-12-02 15:21             ` Borislav Petkov
2010-12-02 16:21               ` Tobias Karnat
2010-12-02 17:02                 ` Florian Mickler
2010-12-02 17:07                   ` Borislav Petkov
2010-12-02 17:06                 ` Borislav Petkov
2010-12-02 18:05                   ` Tobias Karnat
2010-12-02 18:37                     ` Borislav Petkov [this message]
2010-12-02 22:34                       ` Tobias Karnat
2010-12-03 11:58                         ` Borislav Petkov
2010-12-03 21:23                       ` Doug Thompson
2010-12-02 18:14                   ` Florian Mickler
2010-12-02 18:51                     ` Borislav Petkov
2010-12-02 19:54                       ` Florian Mickler

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=20101202183724.GH27263@aftab \
    --to=bp@amd64.org \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.com \
    --cc=tobias.karnat@googlemail.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