From: Pat LaVarre <p.lavarre@ieee.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-scsi@vger.kernel.org, usb-storage@one-eyed-alien.net,
Matthew Dharm <mdharm-scsi@one-eyed-alien.net>,
David Brownell <david-b@pacbell.net>,
Alex Sanks <alex@netchip.com>, Julian Back <jback@mpc-data.co.uk>
Subject: Re: usb storage traces
Date: 19 Dec 2003 09:21:29 -0700 [thread overview]
Message-ID: <1071850889.6191.26.camel@patibmrh9> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0312190945170.805-100000@ida.rowland.org>
> The URL for my traces is:
> http://www.win.tue.nl/~aeb/linux/usb/traces/winme/
Thank you!
> ... doesn't show up in the default directory listing ...
> http://www.win.tue.nl/~aeb/linux/usb/traces/winme/README.txt
To the wish list for RMB please add:
Traces of disk absent (not just traces of disk present).
> One interesting thing about Windows ME
> stands out from reading the files:
> It seems to think the right way to recover
> from a "device was reset" response is to reset the device twice!
On my second reading I guess we here mean to be speaking of sk asc x 6
29. I agree, silly to respond to a notification of reset received by
sending another reset.
On my first reading I wrongly guessed we here were speaking of some
other kind of trouble, to which I answered:
Why should this surprise us?
Reset, like any i/o operation, may fail. Hosts that live by
"be liberal in what you accept" time out and retry resets, yes. In
particular, by trying twice we more liberally tolerate those apparently
generic devices that in fact occasionally choose to scramble the status
phase data toggle at the end of a class-specific reset. Naive hosts see
that as indefinite NAK.
Pat LaVarre
http://plavarre.blog-city.com/index.cfm?d=19&m=12&y=2003
next prev parent reply other threads:[~2003-12-19 16:21 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031219091450.GC828@one-eyed-alien.net>
2003-12-19 14:51 ` usb storage traces Alan Stern
2003-12-19 16:21 ` Pat LaVarre [this message]
2003-12-20 23:56 ` Matthew Dharm
2003-12-21 2:26 ` Alan Stern
[not found] <1070649445.12411.347.camel@patibmrh9>
2003-12-05 19:27 ` Alan Stern
2003-12-05 20:27 ` Pat LaVarre
2003-12-04 18:30 Alan Stern
2003-12-04 18:44 ` Matthew Dharm
2003-12-04 20:59 ` Alan Stern
2003-12-04 21:27 ` Matthew Dharm
2003-12-04 21:33 ` Pat LaVarre
2003-12-04 21:34 ` Pat LaVarre
2003-12-04 21:37 ` Pat LaVarre
2003-12-04 21:38 ` Pat LaVarre
2003-12-04 22:24 ` Pat LaVarre
2003-12-04 22:28 ` Pat LaVarre
2003-12-05 15:01 ` Alan Stern
2003-12-05 17:19 ` Pat LaVarre
2003-12-05 18:22 ` Alan Stern
2003-12-05 5:08 ` Patrick Mansfield
2003-12-05 16:01 ` Alan Stern
2003-12-05 16:11 ` Pat LaVarre
2003-12-05 17:14 ` David Brownell
2003-12-05 17:35 ` Pat LaVarre
2003-12-05 18:21 ` Alan Stern
2003-12-05 18:41 ` Pat LaVarre
2003-12-05 18:24 ` David Brownell
2003-12-16 17:00 ` Randy.Dunlap
2003-12-16 17:07 ` Pat LaVarre
2003-12-05 4:31 ` Douglas Gilbert
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 16:13 Pat LaVarre
2003-11-10 22:04 Pat LaVarre
2003-11-11 21:59 ` Pat LaVarre
2003-11-13 18:42 ` Pat LaVarre
2003-09-22 23:07 [linux-usb-devel] Re: USB storage problems on OHCI Andries.Brouwer
2003-09-22 23:25 ` usb storage traces Pat LaVarre
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=1071850889.6191.26.camel@patibmrh9 \
--to=p.lavarre@ieee.org \
--cc=alex@netchip.com \
--cc=david-b@pacbell.net \
--cc=jback@mpc-data.co.uk \
--cc=linux-scsi@vger.kernel.org \
--cc=mdharm-scsi@one-eyed-alien.net \
--cc=stern@rowland.harvard.edu \
--cc=usb-storage@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