Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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).

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




[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux