[Libusbx-devel] libusbx: error [cache_config_descriptors] could not access configuration descriptor

[Qian Peng]

Hi all :)

We're using spice USB redirect function and find USB devices can't be
redirected sometimes.

When plug a USB device, spice client(in XP) can sense and call
libusb_get_device_list()

libusb log is as follows:
2014-09-02 10:44:31:[000008f8]
os/windows_usb.c:1465:windows_get_device_list: PRO:
\\.\USB#VID_0930&PID_6544#7E5BE265445FCD90E3AA4DEE
2014-09-02 10:44:31:[000008f8]
os/windows_usb.c:1510:windows_get_device_list: extra GUID:
{F301EA50-83E7-461E-A909-630FB2A1C2A6}
2014-09-02 10:44:31:[000008f8]
os/windows_usb.c:1574:windows_get_device_list: allocating new device for
session [24F]
2014-09-02 10:44:31:[000008f8] os/windows_usb.c:1166:init_device: found 1
configurations (active conf: 1)
libusbx: error [cache_config_descriptors] could not access configuration
descriptor (actual) for
'\\.\USB#VID_0930&PID_6544#7E5BE265445FCD90E3AA4DEE': [995]
ԉԚПԌ΋ԶܲӊԃԌѲȫȳìӑ؅Ǻ I/O әطc
(block about 5s)

At the beginning the device can be redirected, but we open and close spice
client process several times, this problem will occur. After re-plug the
usb device, the problem disappears.

the issue looks like
http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/1349577786.68914.1354005550176.JavaMail.open-xchange%40com4.strato.de/#msg30149384

How do we avoid or solve the problem?

Thanks in advance!

[Pete Batard]

Post by Qian Peng
libusbx: error

Looks like you are using libusbx, which has been superseded by libusb.
Can you try with the latest libusb (Please visit http://libusb.info), in
case it fixed that issue.

Post by Qian Peng
the issue looks like
http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/1349577786.68914.1354005550176.JavaMail.open-xchange%40com4.strato.de/#msg30149384
How do we avoid or solve the problem?

As advised in the thread you point out, you may want to have a look at
what USBView reports.

Also, the device you are trying to access appears to be a "Kingston
DataTraveler 2.0 Stick (2GB)" (http://www.linux-usb.org/usb.ids ->
0930:6544), which is a mass storage device.

Can you clarify why you are trying to access a regular mass storage
device using libusb on Windows? This means having to replace the default
Mass Storage driver with WinUSB and losing native access to device as a
flash drive, which seems like an odd thing to try to do...

Regards,

/Pete

[Qian Peng]

Sorry for late response.
We have tried the lastest libusb and tested, the problem still exists.
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?

Thanks

Post by Pete Batard

Post by Qian Peng
libusbx: error

Looks like you are using libusbx, which has been superseded by libusb.
Can you try with the latest libusb (Please visit http://libusb.info), in
case it fixed that issue.

Post by Qian Peng
the issue looks like

http://sourceforge.net/p/libusbx/mailman/libusbx-devel/thread/1349577786.68914.1354005550176.JavaMail.open-xchange%40com4.strato.de/#msg30149384

Post by Qian Peng
How do we avoid or solve the problem?

As advised in the thread you point out, you may want to have a look at
what USBView reports.
Also, the device you are trying to access appears to be a "Kingston
DataTraveler 2.0 Stick (2GB)" (http://www.linux-usb.org/usb.ids ->
0930:6544), which is a mass storage device.
Can you clarify why you are trying to access a regular mass storage
device using libusb on Windows? This means having to replace the default
Mass Storage driver with WinUSB and losing native access to device as a
flash drive, which seems like an odd thing to try to do...
Regards,
/Pete
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
libusbx-devel mailing list
https://lists.sourceforge.net/lists/listinfo/libusbx-devel

[Tim Roberts]

Post by Qian Peng
We have tried the lastest libusb and tested, the problem still exists.

libusb or libusbx?

Post by Qian Peng
We found not only in the device enumeration phase will be stuck,
sometimes also occur in the bulk transfer phase 995 error code
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.