A couple of years back I wrote a simple shared library for a usb missile
launcher. At the time I was running Fedora 8 and I can't remember that I had
the problem I'm about to describe. If I plug in my missile launcher and run
my program it works just fine. However, the second time I run the program I
get ETIMEOUT [-110] from usb_control_msg(). If I disconnect/connect the
device it works again. But just one time. I've tried doing all the cleanup I
could think of, but it doesn't seem to help. A difference between the first
time and the second time is that I (successfully) detach the kernel driver
for my device. This is not necessary the second time. Anyway, in both cases
the program successfully claims the interface.
I'm running some CentOS (can't really remember which version :) If you think
the code can help you help me, I can post it for you.
View this message in context: http://old.nabble.com/usb_control_msg%28%29-returns-ETIMEOUT-tp26485296p26485296.html
Sent from the LibUSB Dev mailing list archive at Nabble.com.
From: Daniel Drake <dan@re...> - 2009-11-26 19:06:07
> Hi all!
> After posting I found a similar problem at
> However it didn't seem to be resolved, so I might as well post this. The
> post I referred talks about the configuration of the device. I don't set any
> configuration at all in my program. What effect does the setting or
> non-setting of configs have?
Some versions of Linux do a soft-reset when you release an interface (or
close a device, I can't remember which). It's possible that your missile
launcher (!?) has a firmware bug and this is causing the device to crash.