On Wed, Mar 28, 2012 at 7:50 PM, Sarah Sharp wrote: > On Tue, Mar 27, 2012 at 04:06:57PM +0530, shashank chaturvedi wrote: >> hi sarah >> I am testing the USB3.0 enumeration with new kernel 3.0.0-16. > > Why that kernel in particular? Why not the latest stable kernel, 3.3? > >> I >> am using ubuntu 11.10 OS and testing device is PLDA spartan6 family board. >> Issue is the Host is sending the string descriptor request with index >> 238.When i Check the kern.log it shows me some different kind of >> error.Please check this error which is highlighted. > > Highlighted...where? I don't see an attachment or anything. Please > communicate in plain text, not HTML. > >> What is this error? Please look after this. >> >> kernel: [ 4714.883928] usb 4-2: USB disconnect, device number 10 >> kernel: [ 4715.531807] hub 4-0:1.0: unable to enumerate USB device on port 2 >> kernel: [ 4717.255563] usb 4-2: new SuperSpeed USB device number 12 using >> xhci_hcd >> kernel: [ 4717.272906] usb 4-2: Isoc endpoint with wBytesPerInterval of >> 4096 in config 1 interface 0 altsetting 0 ep 3: setting to 2048 >> kernel: [ 4717.272913] usb 4-2: Isoc endpoint with wBytesPerInterval of >> 4096 in config 1 interface 0 altsetting 0 ep 131: setting to 2048 >> *kernel: [ 4718.399386] usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd >> mtp-probe rqt 128 rq 6 len 1024 ret -110* BTW, I wonder why there is "len 1024" there if this is the string descriptor request, since string descriptors are maximum 255 bytes long (the first _byte_ gives the length, and in the case of 16-bit unicode 254 bytes would be the highest). As noted in libusb/descriptor.c "Some devices choke on size > 255". Tormod > > So you're saying the USB device is choking on the get string descriptor > request? Hmm, this is the second report I've received about that > particular string descriptor. Maybe some userspace program changed its > behavior? What are using to communicate with the device? > > Sarah Sharp -- 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
