All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <lkml@rtr.ca>
Cc: Tejun Heo <htejun@gmail.com>,
	auxsvr@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: ata command timeout
Date: Tue, 20 Feb 2007 10:37:38 -0500	[thread overview]
Message-ID: <45DB15C2.7020206@garzik.org> (raw)
In-Reply-To: <45DB114B.4020903@rtr.ca>

Mark Lord wrote:
> I don't believe that.  Command timeouts never happen on healthy systems,
> unless we have a driver bug.  Okay, so I can imagine a pathological case
> of a full queue (NCQ) with all 32 commands taking longer than usual due
> to ECC retries in the firmware..

It's not quite so black and white.  There have definitely been interrupt 
delivery problems that cause command timeouts.  Also, Intel PIIX BMDMA 
(all standard PCI IDE, I think?) is defined to /not/ send an interrupt, 
when a DMA error occurs.  The driver is instructed to time out the 
transaction, and start recovery by deducing the state of things from the 
DMA status bits.

Nonetheless, I mostly agree with your statement.  The two most common 
causes of timeouts that I see are interrupt delivery problems, and 
driver bugs.

	Jeff



  reply	other threads:[~2007-02-20 15:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19 19:19 ata command timeout auxsvr
2007-02-20  4:07 ` Tejun Heo
2007-02-20  4:37   ` Marc Marais
2007-02-20 15:18   ` Mark Lord
2007-02-20 15:37     ` Jeff Garzik [this message]
2007-02-21  7:03       ` Tejun Heo

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=45DB15C2.7020206@garzik.org \
    --to=jeff@garzik.org \
    --cc=auxsvr@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    /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.