public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Brent Casavant <bcasavan@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 2.6.13 0/7] MCA/INIT: summary
Date: Tue, 30 Aug 2005 15:45:47 +0000	[thread overview]
Message-ID: <20050830103831.A39952@chenjesu.americas.sgi.com> (raw)
In-Reply-To: <20050830050414.7997.92549.sendpatchset@kao2.melbourne.sgi.com>

On Tue, 30 Aug 2005, Keith Owens wrote:

> Now that MCA/INIT is recoverable, we will have to address the SCSI
> timeouts that occur if interrupts are disabled for long periods.  MCA
> can disable interrupts for up to 20 seconds while it does the
> rendezvous.  On resume, the timer code tries to bring jiffies in sync
> with itc, time runs too fast and we get spurious timeouts.  There is no
> point in recovering from MCA if the disk dies as a side effect of the
> lost interrupts.

I believe you'll find a similar problem with IEEE 1394, at 10 seconds.
See drivers/ieee1394/ieee1394_core.c, the hpsb_send_packet() routine
in particular.  There we find:

	if (!packet->no_waiter || packet->expect_response) {
		atomic_inc(&packet->refcnt);
		/* Set the initial "sendtime" to 10 seconds from now, to
		   prevent premature expiry.  If a packet takes more than
		   10 seconds to hit the wire, we have bigger problems :) */
		packet->sendtime = jiffies + 10 * HZ;
		skb_queue_tail(&host->pending_packet_queue, packet->skb);
	}

Brent

-- 
Brent Casavant                          If you had nothing to fear,
bcasavan@sgi.com                        how then could you be brave?
Silicon Graphics, Inc.                    -- Queen Dama, Source Wars

  reply	other threads:[~2005-08-30 15:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30  5:04 [PATCH 2.6.13 0/7] MCA/INIT: summary Keith Owens
2005-08-30 15:45 ` Brent Casavant [this message]
2005-08-31 11:20 ` Robin Holt
2005-09-01  2:31 ` Keith Owens

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=20050830103831.A39952@chenjesu.americas.sgi.com \
    --to=bcasavan@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