From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Stern Subject: Re: ehci_hcd related S3 lockup on ASUS laptops, again Date: Fri, 20 Apr 2012 20:42:03 -0400 (EDT) Message-ID: References: <20120419214856.GC11484@belkar.wrar.name> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20120419214856.GC11484@belkar.wrar.name> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Andrey Rahmatullin Cc: jrnieder@gmail.com, linux-pm@lists.linux-foundation.org, USB list , Steven Rostedt List-Id: linux-pm@vger.kernel.org On Fri, 20 Apr 2012, Andrey Rahmatullin wrote: > > I'd like to see the dmesg log for the complete suspend/resume cycle > > (naturally you'll have to resume the system by hand after plugging in > > the USB device). Make sure that CONFIG_USB_DEBUG is enabled. > Attached. It looks quite normal. Evidently USB wakeup does _not_ work on your system when the controller isn't in D3 -- and the system crashes during suspend if the controller _is_ in D3! (Does anybody know if USB wakeup works on these machines under Windows?) What about runtime wakeup? You can test it easily enough. Write "auto" to the power/control attribute for the two controllers. This should cause the controllers (or at least one of them) to go into runtime suspend. Does it then wake up when you plug in a USB device? Alan Stern