Oliver, I have been investigating the reasons why our device does not work well with USB Autosuspend while using ECM. I used a USB Analyzer to trace the USB activity and found out that after the SetFeature(Device Remote-Wakeup) transfer that precedes USB Suspend, an IN token is received on EP6 which is the Bulk IN used by ECM. We know there is a bug in the USB PHY we use that puts our system in a locked state when NAK is sent prior to enter USB Suspend. In any case, the IN EP6 IN token should not be sent after the host sends SetFeature(Device Remote-Wakeup). Do you have any idea where this additional IN EP6 IN could come from? And if it would be easy to patch? This would allow us to move forward to validate the CDC-ECM autosuspend feature. Thanks a lot. Nicolas. -----Original Message----- From: Oliver Neukum [mailto:oliver@xxxxxxxxxx] Sent: 10 September 2009 16:38 To: Greg Heinrich Cc: Nicolas Chevillot; linux-usb@xxxxxxxxxxxxxxx; Carl Nordbeck; Martin Chabot Subject: Re: [rft]aggressive autosuspend for cdc-ether Am Donnerstag, 10. September 2009 16:18:00 schrieb Greg Heinrich: > Hi Oliver, > thanks for your message. Resume from suspend works fine on the ACM > channels. The problem I am having at the moment is only on the ECM one. > > I could not unload ehci-hcd as we only really support USB2. That is a problem. You are getting these errors: ehci_hcd 0000:00:1d.7: detected XactErr len 0/1536 retry 1 They are consistent with data lost due to an ehci error which then don't reach cdc-ether. Do these errors happen on a specific system? Can you test what happens if you enable autosuspend only after dhclient has run? Regards Oliver -- ****************************************************************************************** This e-mail (including any attachments) is intended only for the recipient(s) named above. It may contain confidential or privileged information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender by telephone (+44-1454-284800) and destroy the original message. Any statement and/or opinion not related to this company's business and expressed in this message is that of the author and does not necessarily reflect those of Icera. This company does not take any responsibility for the views of the author in any matter not related to the company's objective. ****************************************************************************************** -- 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