linux-kernel - Re: Suspend and resume on ASUS Laptops

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.1112021039460.1420-100000@iolanthe.rowland.org>
Date:	Fri, 2 Dec 2011 10:43:30 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
	Oliver Neukum <oneukum@...e.de>,
	"Rafael J. Wysocki" <rjw@...k.pl>, <linux-pm@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Len Brown <len.brown@...el.com>, Pavel Machek <pavel@....cz>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: Suspend and resume on ASUS Laptops

On Thu, 1 Dec 2011, Steven Rostedt wrote:

> On Thu, 2011-12-01 at 20:31 +0530, Srivatsa S. Bhat wrote:
> 
> > 
> > Hi Steven,
> > Since without the script your system refuses to suspend, you could also use the
> > 'pm_test' framework (documented in Documentation/power/basic-pm-debugging.txt)
> > to find out more about the failing step when suspend is attempted without using
> > the script. Trying 'echo devices > /sys/power/pm_test' might be helpful in your
> > case.
> 
> Interesting, all the pm_tests work. Even core. But when I switch it to
> 'none' it locks up.
> 
> If I just remove the ehci_hcd module, it suspends fine, so the issue is
> with this module (or some usb device). There seems to be two devices
> under ehci_hcd, and I played with the script to only unbind one at a
> time. If I only unbind one (either one) it still hangs. I need to unbind
> both for the suspend to work.

It's possible that this problem is related to wakeup settings.  Have 
you tried disabling wakeup for the EHCI controllers?

This certainly appears to be some sort of bug in the firmware.  Finding 
it and working around it isn't likely to be easy.  Unbinding (or 
unloading) ehci-hcd may indeed be the path of least resistance.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/