public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.10-rc2] Drop SALINFO_TIMER_DELAY to one minute
Date: Wed, 01 Dec 2004 16:36:46 +0000	[thread overview]
Message-ID: <200412010836.46983.jbarnes@sgi.com> (raw)
In-Reply-To: <10903.1101872210@kao2.melbourne.sgi.com>

On Wednesday, December 01, 2004 5:29 am, Jack Steiner wrote:
> On Wed, Dec 01, 2004 at 02:36:50PM +1100, Keith Owens wrote:
> > Experience with recoverable MCA events shows that a poll interval of 5
> > minutes for new MCA/INIT records is a bit too long.  Drop the poll
> > interval to one minute.
>
> I'm not convinced that shortening the delay is the right solution.

Seems like it can't hurt though.

> It seems to me that either the OS or SAL should do something (ex.,
> interrupt, ...) to cause the MCA error to logged/cleared as quickly
> as possible.  Waiting for the next poll interval does not seem like
> the right solution. If too many MCAs (recovered or not) occur
> before the next poll interval, error state will be lost.

I agree that we should also be clearing records for corrected events.  In the 
I/O error handling patch I'm testing, I actually added a call in the recovery 
path to clear the error before we return to SAL, and that seems to be working 
so far, but you say there are potential deadlocks there (note that I'm not 
logging the error at all, just clearing it, seems like there should be a way 
to promote the error from MCA to CMC or something).

Jesse

  parent reply	other threads:[~2004-12-01 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  3:36 [PATCH 2.6.10-rc2] Drop SALINFO_TIMER_DELAY to one minute Keith Owens
2004-12-01 13:29 ` Jack Steiner
2004-12-01 16:36 ` Jesse Barnes [this message]
2004-12-01 16:44 ` Jack Steiner
2004-12-01 17:03 ` Jesse Barnes

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=200412010836.46983.jbarnes@sgi.com \
    --to=jbarnes@sgi.com \
    --cc=linux-ia64@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox