From: Jeff Garzik <jgarzik@pobox.com>
To: Jim Ramsay <jim.ramsay@gmail.com>
Cc: linux-ide@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: sata_promise driver and 2.6.11 on a MIPS board
Date: Mon, 06 Jun 2005 16:49:21 -0400 [thread overview]
Message-ID: <42A4B6D1.9010402@pobox.com> (raw)
In-Reply-To: <4789af9e05060613394b1809c3@mail.gmail.com>
Jim Ramsay wrote:
> The driver then waits via a wait_for_completion apparently waiting for
> the PCI card to throw an interrupt so it can continue. However, I
> never see this interrupt generated, and the driver code waits forever.
This is a known bug that definitely needs fixing:
(to ATA developers)
Any time an ATA command is issued outside of the SCSI layer, we need to
employ a timer to time out commands.
Since most commands are done within the SCSI layer, which provides a lot
of error handling apparatus, most commands properly time out. The ones
during probe - IDENTIFY DEVICE, set xfer mode, etc. - do not have such a
timer.
Jeff
next prev parent reply other threads:[~2005-06-06 20:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 20:39 sata_promise driver and 2.6.11 on a MIPS board Jim Ramsay
2005-06-06 20:49 ` Jeff Garzik [this message]
2005-06-06 21:58 ` Jim Ramsay
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=42A4B6D1.9010402@pobox.com \
--to=jgarzik@pobox.com \
--cc=jim.ramsay@gmail.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).