From: Greg KH <gregkh@suse.de>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Kurt Garloff <garloff@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: sysctl to allow panic on IOCK NMI error
Date: Tue, 30 Jun 2009 15:30:40 -0700 [thread overview]
Message-ID: <20090630223040.GA3802@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0906302324350.23134@eddie.linux-mips.org>
On Tue, Jun 30, 2009 at 11:27:57PM +0100, Maciej W. Rozycki wrote:
> On Wed, 24 Jun 2009, Greg KH wrote:
>
> > This patch introduces a sysctl /proc/sys/kernel/panic_on_io_nmi, which
> > defaults to 0 (off).
> >
> > When enabled, the kernel panics when the kernel receives an NMI caused
> > by an IO error.
> >
> > The IO error triggered NMI indicates a serious system condition, which
> > could result in IO data corruption. Rather than contiuing, panicing and
> > dumping might be a better choice, so one can figure out what's causing
> > the IO error.
> >
> > This could be especially important to companies running IO intensive
> > applications where corruption must be avoided, e.g. a banks databases.
>
> These days an IOCK NMI typically happens in response to a PCI SERR -- it
> may be useful to traverse PCI buses to find the offender and dump this
> information on this occasion too. The south bridge may have additional
> status too.
Sure, that would be great to have. Care to make a patch? :)
thanks,
greg k-h
next prev parent reply other threads:[~2009-06-30 22:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 21:32 [PATCH] x86: sysctl to allow panic on IOCK NMI error Greg KH
2009-06-25 9:16 ` [tip:x86/urgent] x86: Add " tip-bot for Kurt Garloff
2009-06-25 18:15 ` [PATCH] x86: " Eric W. Biederman
2009-06-25 20:07 ` Greg KH
2009-06-25 20:18 ` Ingo Molnar
2009-06-25 20:16 ` Greg KH
2009-06-25 20:06 ` [tip:x86/urgent] x86: Add " tip-bot for Kurt Garloff
2009-06-25 20:09 ` tip-bot for Kurt Garloff
2009-06-30 22:27 ` [PATCH] x86: " Maciej W. Rozycki
2009-06-30 22:30 ` Greg KH [this message]
2009-07-01 0:50 ` Maciej W. Rozycki
2009-07-01 11:10 ` Ingo Molnar
2009-07-01 17:30 ` Jesse Barnes
2009-07-01 17:37 ` Maciej W. Rozycki
2009-07-02 7:53 ` Ingo Molnar
2009-07-02 10:41 ` Borislav Petkov
2009-07-03 7:59 ` Ingo Molnar
2009-07-03 21:35 ` Maciej W. Rozycki
2009-07-03 9:19 ` Kurt Garloff
2009-07-03 9:24 ` Ingo Molnar
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=20090630223040.GA3802@suse.de \
--to=gregkh@suse.de \
--cc=garloff@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 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.