From: Andi Kleen <ak@suse.de>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, iod00d@hp.com,
ishii.hironobu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
Date: Wed, 28 Jan 2004 20:01:32 +0000 [thread overview]
Message-ID: <20040128210132.2b0e5a96.ak@suse.de> (raw)
In-Reply-To: <16408.4597.123125.788631@napali.hpl.hp.com>
On Wed, 28 Jan 2004 11:48:05 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Wed, 28 Jan 2004 20:39:15 +0100, Andi Kleen <ak@suse.de> said:
>
> >> Yet they are a good indicator that something is wrong (not performing
> >> properly) or may be failing soon. I don't think putting on blinders
> >> for such problems is a good idea. Though I agree that the question of
>
> Andi> Most server class hardware should log it somewhere and allow
> Andi> to read the event log in the firmware. This even works for
> Andi> unhandleable errors unlike what the OS could do.
>
> And you'd want to reboot your server just so you can check on the soft
> failure rate? ;-)
Yep, I reboot my machines all the time ;-)
Seriously you can count it somewhere and present it in sysfs or /proc.
Or log it somewhere else and supply a special utility to show them
that makes it clear that the events are hardware and not software related.
I suppose if your server vendor is serious they will supply a tool
to read the firmware log from a running system.
But printks enabled by default are a bad idea (and a bug too BTW - printk called from
MCE handlers can randomly deadlock)
-Andi
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <ak@suse.de>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, iod00d@hp.com,
ishii.hironobu@jp.fujitsu.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [RFC/PATCH, 1/4] readX_check() performance evaluation
Date: Wed, 28 Jan 2004 21:01:32 +0100 [thread overview]
Message-ID: <20040128210132.2b0e5a96.ak@suse.de> (raw)
In-Reply-To: <16408.4597.123125.788631@napali.hpl.hp.com>
On Wed, 28 Jan 2004 11:48:05 -0800
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> >>>>> On Wed, 28 Jan 2004 20:39:15 +0100, Andi Kleen <ak@suse.de> said:
>
> >> Yet they are a good indicator that something is wrong (not performing
> >> properly) or may be failing soon. I don't think putting on blinders
> >> for such problems is a good idea. Though I agree that the question of
>
> Andi> Most server class hardware should log it somewhere and allow
> Andi> to read the event log in the firmware. This even works for
> Andi> unhandleable errors unlike what the OS could do.
>
> And you'd want to reboot your server just so you can check on the soft
> failure rate? ;-)
Yep, I reboot my machines all the time ;-)
Seriously you can count it somewhere and present it in sysfs or /proc.
Or log it somewhere else and supply a special utility to show them
that makes it clear that the events are hardware and not software related.
I suppose if your server vendor is serious they will supply a tool
to read the firmware log from a running system.
But printks enabled by default are a bad idea (and a bug too BTW - printk called from
MCE handlers can randomly deadlock)
-Andi
next prev parent reply other threads:[~2004-01-28 20:01 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 1:54 [RFC/PATCH, 1/4] readX_check() performance evaluation Hironobu Ishii
2004-01-28 1:54 ` Hironobu Ishii
2004-01-28 17:20 ` Grant Grundler
2004-01-28 17:20 ` Grant Grundler
2004-01-28 17:41 ` Andi Kleen
2004-01-28 17:41 ` Andi Kleen
2004-01-28 18:31 ` David Mosberger
2004-01-28 18:31 ` David Mosberger
2004-01-28 18:52 ` Andi Kleen
2004-01-28 18:52 ` Andi Kleen
2004-01-28 19:24 ` David Mosberger
2004-01-28 19:24 ` David Mosberger
2004-01-28 19:39 ` Andi Kleen
2004-01-28 19:39 ` Andi Kleen
2004-01-28 19:48 ` David Mosberger
2004-01-28 19:48 ` David Mosberger
2004-01-28 20:01 ` Andi Kleen [this message]
2004-01-28 20:01 ` Andi Kleen
2004-01-28 23:35 ` David Mosberger
2004-01-28 23:35 ` David Mosberger
2004-02-16 10:19 ` Pavel Machek
2004-02-16 10:19 ` Pavel Machek
2004-01-28 19:09 ` Grant Grundler
2004-01-28 19:09 ` Grant Grundler
2004-01-28 19:17 ` Andi Kleen
2004-01-28 19:17 ` Andi Kleen
2004-01-28 21:14 ` Grant Grundler
2004-01-28 21:14 ` Grant Grundler
2004-01-28 21:39 ` Andi Kleen
2004-01-28 21:39 ` Andi Kleen
2004-01-29 8:23 ` Matthias Fouquet-Lapar
2004-01-29 8:23 ` Matthias Fouquet-Lapar
2004-01-29 19:28 ` David Mosberger
2004-01-29 19:28 ` David Mosberger
2004-01-29 20:16 ` Matthias Fouquet-Lapar
2004-01-29 20:16 ` Matthias Fouquet-Lapar
2004-01-29 21:09 ` David Mosberger
2004-01-29 21:09 ` David Mosberger
2004-01-29 22:20 ` Matthias Fouquet-Lapar
2004-01-29 22:20 ` Matthias Fouquet-Lapar
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=20040128210132.2b0e5a96.ak@suse.de \
--to=ak@suse.de \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=iod00d@hp.com \
--cc=ishii.hironobu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.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.