From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Stern Subject: Re: linux-next: Tree for Apr 24 [ PM: Device 1-1.2 failed to resume async: error -32 ] Date: Thu, 25 Apr 2013 11:44:58 -0400 (EDT) Message-ID: References: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from iolanthe.rowland.org ([192.131.102.54]:39195 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757820Ab3DYPo7 (ORCPT ); Thu, 25 Apr 2013 11:44:59 -0400 In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: Sedat Dilek Cc: Stephen Rothwell , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Linux PM List , "Rafael J. Wysocki" , linux-usb@vger.kernel.org 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