From: David Brownell <david-b@pacbell.net>
To: Alan Stern <stern@rowland.harvard.edu>,
"Tomita, Haruo" <haruo.tomita@toshiba.co.jp>
Cc: USB development list <linux-usb-devel@lists.sourceforge.net>,
SCSI development list <linux-scsi@vger.kernel.org>,
"Tomita, Haruo" <htomita@pcs.pc.ome.toshiba.co.jp>
Subject: Re: usb-starge not working in the latest kernel 2.4
Date: Fri, 29 Aug 2003 07:50:23 -0700 [thread overview]
Message-ID: <3F4F682F.3010707@pacbell.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0308290958190.824-100000@ida.rowland.org>
Alan Stern wrote:
> On Fri, 29 Aug 2003, Tomita, Haruo wrote:
>
>>usb-storage: Command READ_10 (10 bytes)
>>usb-storage: 28 00 00 02 e5 24 00 00 3f 00 00 00
>>usb-storage: Bulk command S 0x43425355 T 0x7862f8 Trg 0 LUN 0 L 129024 F 128 CL 12
>>usb-storage: command_abort() called
>
>
> It stopped working here. The driver tried to send the next command but
> the drive never acknowledged receiving it.
It might also be useful to find just how many of those 126 KBytes
were successfully transferred before the abort.
Also: is this one of those cases where 2.6 works and 2.4 doesn't?
The i/o patterns are very different ...
> Did you said that the device works well when connected through a high
> speed hub, but it fails when connected directly to the computer? That's a
> big clue, but I don't know what it means.
I don't either.
- Dave
next prev parent reply other threads:[~2003-08-29 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 1:42 usb-starge not working in the latest kernel 2.4 Tomita, Haruo
2003-08-29 14:09 ` Alan Stern
2003-08-29 14:50 ` David Brownell [this message]
2003-08-29 15:12 ` Alan Stern
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 11:05 Tomita, Haruo
2003-09-01 11:05 Tomita, Haruo
2003-09-05 11:14 Tomita, Haruo
2003-09-05 15:31 ` 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=3F4F682F.3010707@pacbell.net \
--to=david-b@pacbell.net \
--cc=haruo.tomita@toshiba.co.jp \
--cc=htomita@pcs.pc.ome.toshiba.co.jp \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=stern@rowland.harvard.edu \
/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