From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Pat LaVarre <p.lavarre@ieee.org>, Philippe Troin <phil@fifi.org>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
usb-storage@lists.one-eyed-alien.net
Subject: Re: [usb-storage] Re: iRiver H100 series and usb-storage issues
Date: 08 Jun 2004 10:52:12 -0500 [thread overview]
Message-ID: <1086709937.2105.8.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0406081019281.1222-100000@ida.rowland.org>
On Tue, 2004-06-08 at 09:24, Alan Stern wrote:
> sd doesn't receive any error indication other than positive residue, and
> it ignores the residue.
Erm, but sd doesn't expect a non zero residue (and producing one is
illegal) because it sets underflow to the exact size for all read and
write commands.
Usually HBAs ignore underflow, because it simply works correctly for all
SCSI devices I've ever come across. However, if you're going to be
getting these problems, you really should be checking the underflow.
The meaning of this field is supposed to be "return an error if you
transfer fewer than underflow bytes". The error's not specified, but
something like DID_ERROR with SUGGEST_RETRY should be fine.
James
next prev parent reply other threads:[~2004-06-08 15:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-29 23:42 Patch for iriver-mp3player Tobias Lieber
2004-06-06 14:48 ` James Bottomley
2004-06-06 22:32 ` Matthew Dharm
2004-06-07 14:36 ` Alan Stern
2004-06-28 19:42 ` Tobias Lieber
2004-06-07 14:47 ` iRiver H100 series and usb-storage issues Alan Stern
2004-06-07 19:43 ` Philippe Troin
2004-06-07 20:22 ` Alan Stern
2004-06-07 21:18 ` Philippe Troin
2004-06-07 22:27 ` [usb-storage] " Pat LaVarre
2004-06-08 14:24 ` Alan Stern
2004-06-08 15:52 ` James Bottomley [this message]
2004-06-08 16:10 ` Pat LaVarre
2004-06-08 16:16 ` James Bottomley
2004-06-08 17:01 ` Mike Anderson
2004-06-08 14:19 ` Alan Stern
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=1086709937.2105.8.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=p.lavarre@ieee.org \
--cc=phil@fifi.org \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@lists.one-eyed-alien.net \
/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