From: Jeff Garzik <jeff@garzik.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Mark Lord <liml@rtr.ca>, Tejun Heo <htejun@gmail.com>,
Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: libata fails to recover from HSM violation involving DRQ status
Date: Sat, 28 Apr 2007 17:38:47 -0400 [thread overview]
Message-ID: <4633BEE7.8020005@garzik.org> (raw)
In-Reply-To: <20070428222502.26fc9bbc@the-village.bc.nu>
Alan Cox wrote:
>> I am reluctant to do anything about this.
>
> This one does need dealing with. It happens in the real world and the old
> IDE paths for this do get triggered and used now and then (we know this
> because bugs in them were found). All it takes is a device and a
> controller disagreeing about the length of a data transfer to get in a
How would they disagree (excluding human error)?
> mess. In theory resetting the bus should get you out of this, I'm
> suprised we didn't get out that way.
Indeed.
>> All manner of things can go wrong, if the taskfile protocol specified
>> disagrees with the taskfile contents.
>
> True but at the point you are trying to do error recovery and DRQ is
> wedged on its a good idea to pull remaining data out of the fifo.
It's not really a good idea for SATA. The "FIFO" often co-emulated by
the SATA controller and SATA phy. You just want to kick SATA really
hard (i.e. bus reset and friends).
Jeff
next prev parent reply other threads:[~2007-04-28 21:38 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-28 20:15 libata fails to recover from HSM violation involving DRQ status Mark Lord
2007-04-28 20:18 ` Mark Lord
2007-04-28 20:30 ` Alan Cox
2007-04-28 20:37 ` Jeff Garzik
2007-04-28 20:44 ` Mark Lord
2007-04-28 20:50 ` Jeff Garzik
2007-04-28 21:25 ` Alan Cox
2007-04-28 21:35 ` Mark Lord
2007-04-28 21:38 ` Jeff Garzik [this message]
2007-04-28 21:41 ` Mark Lord
2007-04-29 3:17 ` Tejun Heo
2007-04-29 3:46 ` Jeff Garzik
2007-04-29 7:45 ` Tejun Heo
2007-04-29 3:51 ` Tejun Heo
2007-04-29 11:56 ` Mark Lord
2007-04-29 12:59 ` Mark Lord
2007-04-29 13:13 ` Mark Lord
2007-04-29 16:42 ` Tejun Heo
2007-04-29 16:47 ` Mark Lord
2007-04-29 18:49 ` Mark Lord
2007-04-29 19:05 ` Mark Lord
2007-04-30 0:59 ` Tejun Heo
2007-04-29 19:07 ` Mark Lord
2007-04-30 0:54 ` Tejun Heo
2007-04-30 3:42 ` Mark Lord
2007-04-30 3:58 ` Tejun Heo
2007-04-30 17:47 ` Mark Lord
2007-05-01 0:23 ` Mark Lord
2007-05-01 2:47 ` Tejun Heo
2007-05-01 13:00 ` Mark Lord
2007-05-11 3:33 ` Mark Lord
2007-05-11 3:35 ` Mark Lord
2007-04-29 12:07 ` Mark Lord
2007-04-29 16:36 ` Tejun Heo
2007-04-28 23:56 ` Alan Cox
2007-04-28 22:09 ` Mark Lord
2007-04-29 3:04 ` 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=4633BEE7.8020005@garzik.org \
--to=jeff@garzik.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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.