From: Borislav Petkov <bp@amd64.org>
To: Tobias Karnat <tobias.karnat@googlemail.com>
Cc: linux-edac <linux-edac@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Doug Thompson <norsk5@yahoo.com>,
"Arvind R." <arvind@acarlab.com>
Subject: Re: edac_core: crashes on shutdown
Date: Fri, 3 Dec 2010 12:58:42 +0100 [thread overview]
Message-ID: <20101203115842.GB3169@aftab> (raw)
In-Reply-To: <1291329254.8869.66.camel@Tobias-Karnat>
On Thu, Dec 02, 2010 at 05:34:14PM -0500, Tobias Karnat wrote:
> I thought as you wrote later, that this would be an option to use an
> interrupt instead of polling for edac in general.
>
> But as far as I understand this, it is used for PCI bus errors?
Yep, reportedly, memory parity errors can be reported through an NMI.
However, I don't know whether all chipset vendors still do that since
this is legacy and all.
> And should be replaced for detection of PCI SERR and/or PCIE AER,
> are these the same as PCI bus errors?
Yep, this all pertains to PCI/PCIe error reporting but don't
ask me about specifics. You might get some more info from
http://lwn.net/Articles/193468/ - it is not in the current kernel
sources though. Also, EDAC has a generic polling routine for PCI errors,
see <drivers/edac/edac_pci_sysfs.c:edac_pci_dev_parity_test()>
> > 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.
>
> From Intel Architectures Software Developer's Manual Part 3A:
>
> "Starting with 45nm Intel 64 processor with CPUID signature
> DisplayFamily_DisplayModel encoding of 06H_1AH (...), the processor can
> report information on corrected machine-check errors and deliver a
> programmable interrupt for software to respond to MC errors, referred to
> as corrected machine-check error interrupt (CMCI)."
>
> Seems to be unlikely for me on an Intel 975X Mainboard.
Hmm, I don't know, let's ask the driver author :)
Arvind?
--
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
next prev parent reply other threads:[~2010-12-03 11:58 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
2010-12-02 22:34 ` Tobias Karnat
2010-12-03 11:58 ` Borislav Petkov [this message]
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=20101203115842.GB3169@aftab \
--to=bp@amd64.org \
--cc=arvind@acarlab.com \
--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