From: Pat LaVarre <p.lavarre@ieee.org>
To: Philippe Troin <phil@fifi.org>
Cc: linux-scsi@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
Alan Stern <stern@rowland.harvard.edu>,
James Bottomley <James.Bottomley@steeleye.com>
Subject: Re: [usb-storage] Re: iRiver H100 series and usb-storage issues
Date: 07 Jun 2004 16:27:44 -0600 [thread overview]
Message-ID: <1086647263.3137.134.camel@patibmrh9> (raw)
In-Reply-To: <87y8mzukwk.fsf@ceramic.fifi.org>
Philippe T:
> I was pointing out I am mostly clueless
> w.r.t. USB. ... what about:
>
> usb-storage: usb_stor_transfer_partial(): xfer 512 bytes
> usb-storage: usb_stor_bulk_msg() returned 0 xferred 0/512
> usb-storage: Bulk data transfer result 0x1
> usb-storage: Attempting to get CSW...
> ^^^^^^^^^^^^^^^^^^^^^^^^
> usb-storage: clearing endpoint halt for pipe 0xc0011e80
> usb-storage: usb_stor_clear_halt: result=0
> usb-storage: Attempting to get CSW (2nd try)...
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> usb-storage: Bulk status result = 0
> usb-storage: Bulk status Sig 0x53425355 T 0x945 R 512 Stat 0x0
> usb-storage: -- unexpectedly short transfer
> usb-storage: Issuing auto-REQUEST_SENSE
Knowing only SCSI over USB, not Linux or USB, I'd guess ...
This is a completely ordinary trace of two popular design choices made
by this SCSI over USB device. First, this device chose to copy less
than the expected count of bytes in. Second, this device chose to
STALL, rather than copying the bytes in and trusting the host to notice
nonzero dCSWDataResidue.
What's ironic here is that the Linux USB layer understands entirely that
the STALL redundantly with the "CSW" "R 512" means "unexpectedly short
transfer" ... but we're told the layers above don't get it, all the
same.
The op x03 "REQUEST SENSE" here is inappropriate - it is unsolicited -
the "CSW" "Stat" was not x01 AutoSenseMe, it was x00 Passed, expressed
here as "Stat 0x0".
I'm thinking usb-storage has to remove that inappropriate "REQUEST
SENSE", else usb-storage cannot be passing correct status back up?
usb-storage cannot correctly say that it autosensed SK ASC ASCQ zero,
because usb-storage only fetched unsolicited sense, not auto sense.
usb-storage cannot say it saw a failure without sense, because
usb-storage did think it auto sensed.
Yes?
But after all that, maybe sd still will ignore the error and miscompare?
Pat LaVarre
next prev parent reply other threads:[~2004-06-07 22:27 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 ` Pat LaVarre [this message]
2004-06-08 14:24 ` [usb-storage] " Alan Stern
2004-06-08 15:52 ` James Bottomley
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=1086647263.3137.134.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-scsi@vger.kernel.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