Hi, The device has displayed the XactErr problem on a different x86 machine. Have also tested 3 different hardware of the device. The machine itself does not exhibit any problems, the device and other USB devices works without issues running Windows. We can sometimes run 2000+ cycles of remote wakup without any problem, it is just sometimes (when we hit some sweet spot) we trigger this XactErr and the device detects USB reset. The logs only displays the last unsuccessful cycle. BR, Rickard -----Original Message----- From: Alan Stern [mailto:stern@xxxxxxxxxxxxxxxxxxx] Sent: den 17 november 2009 03:22 To: Rickard Bellini Cc: Oliver Neukum; linux-usb@xxxxxxxxxxxxxxx Subject: RE: additional debug output for autosuspend in cdc-ether On Tue, 17 Nov 2009, Rickard Bellini wrote: > Hi, > > Issue occurred again after some hours, too early to say whether the change have made any difference. > Any suggestions? > > Attached is usbmon log and below is the actual log: Interestingly, the log showed one example where remote wakeup worked and another example where it didn't. The usbmon log seems to indicate that the port gets disabled when the failure occurs. This could be caused by a bug in the device or a bug in the computer's EHCI hardware. Have you tested this device on a different computer? And have you tested a different device (such as a high-speed hub) on your computer, to see if it can do a remote wakeup okay? 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
