Qian Peng wrote: > > We have tried the lastest libusb and tested, the problem still exists.
libusb or libusbx? > We found not only in the device enumeration phase will be stuck, > sometimes also occur in the bulk transfer phase 995 error code > Related log is as follows: > 2014-09-24 14:17:05:[00000a28] > os/windows_usb.c:2067:windows_transfer_callback: handling I/O > completion with errcode 995, size 0 > 2014-09-24 14:17:05:[00000a28] > os/windows_usb.c:2090:windows_transfer_callback: detected operation > aborted > > Errcode 995 always haunts us, we couldn't find the real cause of the > problem. > Could you please give us some ideas or tips to find the cause of the > problem? You're going to need to use a bus analyzer. Your hardware is broken, and you need to figure out why. You can try a software analyzer first (like usblyzer), but I'm guessing you'll need a hardware analyzer to get to the bottom of this. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
