On Thu, Apr 25, 2013 at 5:44 PM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Wed, 24 Apr 2013, Sedat Dilek wrote: > >> With CONFIG_USB_DEBUG=y I do not see a PM/async line. >> >> Might you have a look at the logs? > > They look quite normal. Except for one thing: The built-in hubs appear > to have gotten reset during the suspend/resume, for no apparent reason. > That's probably the reason why the Logitech mouse needed a reset. > > I don't know why the mouse reset worked this time but not before, > unless it's a subtle timing issue (the extra debugging output causes > the resume to go a little more slowly). > Thanks for your patience, help, hints and explanations. You want me to send a patch against usb-next to clarify a bit on the kernel-config options to be enabled as prereqs in case of usbmon-tracing. If you think it's worth or not let me know. - Sedat - > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
