john smith wrote:
>
> Hi,
>
> This is a continuation my previous post a few weeks ago, (BTW, I was
> never to resolve that problem), I read the manual many time and read
> all the related post, I believe I did everything right, now I am
> running my on Linux (Ubutu 11), this time, it did not crash but the
> behavior is very similar, the READ and WRITE did not return and
> finally the app bail out. would anyone please tell me what I did
> anything wrong here?
>
>
> I am not doing any hot plug here. I do not understand why it is show
> the following:
>
> _[44.690983] [0000266b] libusbx: debug [handle_bulk_completion] device
> removed_
>
Your log shows you get these errors, in this order:
-121 EREMOTEIO
-104 ECONNRESET
-108 ESHUTDOWN (repeatedly).
The libusbx code handles ESHUTDOWN by printing the "device removed"
message. EREMOTEIO indicates that the endpoint had been disabled
because of a previous error. ECONNRESET usually means the URB was
canceled while in progress. ESHUTDOWN indicates that something in the
device's path is shutting down (controller, hub, device).
My guess, based on the limited evidence, is that you have a device
problem that is causing the host controller to raise error conditions on
your endpoint. Is this a device you are developing? Do you have a USB
analyzer, so you can watch the traffic when this happens and see if
there are any unusual packets?
--
Tim Roberts, t...@probo.com
Providenza & Boekelheide, Inc.
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
