On Mon, 26 Oct 2009, John Faith wrote: > Hello, > I have a custom board much like the OMAP3530 EVM, but with a ISP1507B > USB transceiver. For my 2.6.29rc3 kernel, I get this console output > when I plug in a powered hub: > > usb 1-1: new high speed USB device using musb_hdrc and address 2 > usb 1-1: device descriptor read/64, error -71 > usb 1-1: device descriptor read/64, error -71 > usb 1-1: new high speed USB device using musb_hdrc and address 3 > usb 1-1: device descriptor read/64, error -71 > usb 1-1: device descriptor read/64, error -71 > ... > > and this is the usbmon dump around the "80 06" descriptor request and > the subsequent error -71 (EPROTO?): > > c671f8a0 1662538668 S Co:1:001:0 s 23 03 0004 0001 0000 0 > c671f8a0 1662538760 C Co:1:001:0 0 0 > c671f8a0 1662594851 S Ci:1:001:0 s a3 00 0000 0001 0004 4 < > c71ca140 1662594942 C Ii:1:001:1 0:2048 1 D > c71ca140 1662594973 S Ii:1:001:1 -115:2048 4 < > c671f8a0 1662595064 C Ci:1:001:0 0 4 = 03051200 > c671f8a0 1662657351 S Co:1:001:0 s 23 01 0014 0001 0000 0 > c671f8a0 1662657412 C Co:1:001:0 0 0 > c671f8a0 1662663393 S Ci:1:000:0 s 80 06 0100 0000 0040 64 < > c671f8a0 1662663485 C Ci:1:000:0 -71 0 > c671f8a0 1662663607 S Ci:1:000:0 s 80 06 0100 0000 0040 64 < > c671f8a0 1662663821 C Ci:1:000:0 -71 0 > > The same hub on an EVM board using the same kernel returns the > descriptor and works fine (can use USB mass storage), so I'm wondering > what type of failure this might indicate or how best to proceed. I > assume that the transceiver is mostly ok since some packets do make it > in and out before the descriptor request. They do? What packets are those? Certainly nothing in the extract above. > Does it seem possible that > shorter messages make it across but that longer messages would fail > due to timing or similar hardware issues? It seems unlikely, but I'm not at all familiar with the hardware so my opinion doesn't count for much. Alan Stern -- 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
