From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Dave Jones <davej@redhat.com>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Add mem_nmi_panic enable system to panic on hard error
Date: Tue, 13 Dec 2005 12:23:37 +0000 [thread overview]
Message-ID: <1134476618.11732.7.camel@localhost.localdomain> (raw)
In-Reply-To: <20051213064800.GB7401@redhat.com>
On Maw, 2005-12-13 at 01:48 -0500, Dave Jones wrote:
> On Tue, Dec 13, 2005 at 03:38:16PM +0900, Hidetoshi Seto wrote:
> > Some x86 server fires NMI with reason 0x80 up if a parity error
> > occurs on its PCI-bus system or DIMM module.
>
> Hmm, are you sure this isn't a bios error misconfiguring
> some northbridge register perhaps ? Some chipsets offer
> such reporting as a feature. Could be your server has this
> on by default.
This is done deliberately on some systems and is why we have the patches
I submitted to Andrew Morton which are in his tree and allow you to set
"panic_on_unrecovered_nmi" to halt on a memory error.
See the -mm tree. The functionality is there. Also see the various
x86-64 logging tools which can parse out MCE based reports.
> (I believe the EDAC code has also triggered similar cases
> on certain cards which is why it too disables this checking
> by default).
EDAC has it enabled by default at the moment, although it needs to clear
left over flags and possibly a small blacklist first.
> The sysctl seems pointless too. If this is needed at all,
> why would you ever want to turn it off ?
Debugging and stressing systems for one.
next prev parent reply other threads:[~2005-12-13 12:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-13 6:38 [PATCH] Add mem_nmi_panic enable system to panic on hard error Hidetoshi Seto
2005-12-13 6:48 ` Dave Jones
2005-12-13 8:56 ` Hidetoshi Seto
2005-12-13 12:23 ` Alan Cox [this message]
2005-12-14 8:49 ` Hidetoshi Seto
2005-12-14 11:05 ` Alan Cox
2005-12-15 1:53 ` Hidetoshi Seto
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=1134476618.11732.7.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=seto.hidetoshi@jp.fujitsu.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