Hi,
>>We still have issues with USB communication for our
>>particular device, but the kernel seems to do just fine.
So now it seems I have to rain on my own parade
and pull back my initial praise. As I said we still have issues
with our application and devices and we mosty blamed it on
the fact that we might have deadlock/race conditions in threads
which independently read/write from/to the devices, but it turned
out that all seems to be find if we return to the previous simple
patch. The patched 3.4 kernel sometimes seems to block usb
communication from time to time.
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 ?? ()
--
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
