Hi, Oncaphillis wrote: > The stack trace looks like: > > #0 0x00007f7b9e415563 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=60000) at ../sysdeps/unix/sysv/linux/poll.c:87 > #1 0x00007f7b9ee87434 in ?? () from /usr/lib/libusb-1.0.so.0 > #2 0x00007f7b9ee8772f in libusb_handle_events_timeout_completed () from /usr/lib/libusb-1.0.so.0 > #3 0x00007f7b9ee87866 in libusb_handle_events_completed () from /usr/lib/libusb-1.0.so.0 > #4 0x00007f7b9ee88522 in ?? () from /usr/lib/libusb-1.0.so.0 > #5 0x00007f7b9ee886e7 in libusb_interrupt_transfer () from /usr/lib/libusb-1.0.so.0 > #6 0x000000000041fe55 in ?? () > #7 0x0000000000420320 in ?? () Please answer all these questions: What version of libusb are you using? Did you wait for more than 60 seconds for the "deadlock" to clear? Please try the libusb.git code, with --enable-debug-log during configure. Post the log to the libusb-devel mailing list. See http://libusb.org/wiki/MailingList Thank you //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
