I have 3-5 PC, Laptop etc, and 5-6 different model USB Stick.
I plug a stick to USB, many times it's identified normally. Mount etc..
OK.
But, sometimes system don't identifiy USB stick. According to dmesg, its
can't read from device with error -110 (or -70, sometime but not
frequently).
I remov
David Brownell wrote:
>>> Looking at the usb_stor_transfer_partial() code, it looks to me
>>> like it expected to know it was in the middle of an abort, but
>>> didn't ... and so it gave a catch-all message and bypassed the
>>> abort processing, rather than knowing that the only reason it'd
>
Matthew Dharm wrote:
> Well, the semantic meaning of STALL really varies among the DWGs. STALL in
> usb-storage land is a pretty common occurance, actually. It's used to
> indicate a problem in a single phase of the transaction (which is multiple
> transfers) and keep synchronization between hos
At 01:27 PM 7/16/02 -0700, Matthew Dharm wrote:
>Well, the semantic meaning of STALL really varies among the DWGs. STALL in
>usb-storage land is a pretty common occurance, actually. It's used to
>indicate a problem in a single phase of the transaction (which is multiple
>transfers) and keep sync
Well, the semantic meaning of STALL really varies among the DWGs. STALL in
usb-storage land is a pretty common occurance, actually. It's used to
indicate a problem in a single phase of the transaction (which is multiple
transfers) and keep synchronization between host and target.
Matt
On Tue,
>>This particular usb-storage abort problem has been seen before.
>
> And is fixed in the 2.5 tree. But it doesn't really address the question
> of why the command lingered for so long...
Not fixed in 2.5.25, fwiw.
- Dave
---
This sf.net em
At 10:33 AM 7/16/02 -0700, Matthew Dharm wrote:
>That's what a clean unlink looks like under EHCI? Okay, then
>
>The only reason command_abort() gets called is that the command has been
>out for over 20 seconds. For that to occur during the data phase (and
>combined with the 'hang' at the CSW
On Tue, Jul 16, 2002 at 11:11:33AM -0700, David Brownell wrote:
> Matthew Dharm wrote:
> > That's what a clean unlink looks like under EHCI? Okay, then
>
> This particular usb-storage abort problem has been seen before.
And is fixed in the 2.5 tree. But it doesn't really address the questio
On Tue, Jul 16, 2002 at 11:18:22AM -0700, David Brownell wrote:
> Greg KH wrote:
> >On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote:
> >
> >>My -guess- is that the data toggle has been screwed up somewhere.
> >
> >
> >I know this is a problem in the current 2.4 stack, and sometimes i
Greg KH wrote:
> On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote:
>
>>My -guess- is that the data toggle has been screwed up somewhere.
>
>
> I know this is a problem in the current 2.4 stack, and sometimes in 2.5.
UHCI only though, yes?
While I wouldn't rule out bugs in OHCI or
Matthew Dharm wrote:
> That's what a clean unlink looks like under EHCI? Okay, then
According to the spec for usb_unlink_urb(), that's what an async
unlink should look like for *all* host controllers. (Modulo the
fact that -ECONNRESET may have different values on different
versions of Linux.
On Tue, Jul 16, 2002 at 10:33:18AM -0700, Matthew Dharm wrote:
>
> My -guess- is that the data toggle has been screwed up somewhere.
I know this is a problem in the current 2.4 stack, and sometimes in 2.5.
Seems to happen when we unlink a urb, and then go to submit it again
later. I've seen wor
That's what a clean unlink looks like under EHCI? Okay, then
The only reason command_abort() gets called is that the command has been
out for over 20 seconds. For that to occur during the data phase (and
combined with the 'hang' at the CSW stage) means that the HCD thinks that
the device is
On Mon, Jul 15, 2002 at 10:21:56PM -0700, Tom Collins wrote:
> There have been two posts recently to linux-usb-users regarding
> problems that I'm also experiencing. Perhaps someone on the
> developers list would like to pick this up and run with it.
These are three separate problems.
> At 12
There have been two posts recently to linux-usb-users regarding
problems that I'm also experiencing. Perhaps someone on the
developers list would like to pick this up and run with it.
Here are key parts of the recent messages, I can provide copies of
the full messages for those interested. T
15 matches
Mail list logo
