On Sat, Apr 15, 2006 at 02:28:59AM -0400, Chaskiel M Grundman wrote: > I am unfortunately encountering frequent usb errors with the > itsec-p and 5/2048. ifd_usb_control is failing with EOVERFLOW, > which apparently means that a usb condition known as 'babble' has > been detected. I don't really know what this means or if it's the > fault of openct, linux, or the hardware
Babble is an error condition where a USB device (the ITSEC token) continues talking longer than it is allowed to. The hub it is connected to is responsible for detecting this and preventing it from propagating up to the host. Hubs are complex USB devices, I've had bad luck with some hubs not working properly. If you have a hub between the host (PC) and the device (token) when you see the error perhaps you could try connecting the device directly to the host? Also, which HC(s) did you see this with? EHCI and UHCI both have the mapping of babble->EOVERFLOW, but on OHCI EOVERFLOW is used only for some quirk error during HC startup.. Did you get any other errors on the OHCI controller that could provide more clues? //Peter _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
