Re: Two problems with system sleep

From: Alan Stern <stern@rowland.harvard.edu>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Alan <alan@lxorguk.ukuu.org.uk>
Subject: Re: Two problems with system sleep
Date: Mon, 22 Feb 2010 16:33:05 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.44L0.1002221623430.1264-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <201002221945.25891.rjw@sisk.pl>

On Mon, 22 Feb 2010, Rafael J. Wysocki wrote:

> On Monday 22 February 2010, Alan Stern wrote:
> > On Sun, 21 Feb 2010, Rafael J. Wysocki wrote:
> > 
> > > > > Anyway, we need to check if control gets back to acpi_suspend_enter().
> > 
> > Would PM_TRACE_RTC help?
> 
> In my opinion that's worth doing.

Here's what I got:

[    3.349334] PM: Resume from disk failed.
[    3.350060]   Magic number: 0:141:321
[    3.352583]   hash matches drivers/base/power/main.c:477
[    3.355144] tty tty46: hash matches
[    3.357742] i915 0000:00:02.0: hash matches

So it appears that the video driver is indeed the culprit.  Is there 
any way to narrow it down further?

> > By concentrating on the video drivers, you may be missing part of 
> > the problem.  Have you considered why pressing a key on the keyboard 
> > doesn't wake the system up?  Nothing happens -- the power LED on the 
> > desktop case just keeps on blinking.
> 
> We may just not set up the keyboard as a wakeup device.  The other option is
> that the BIOS has a problem with resume handling, in which case I have no
> idea what to do.

Here's my /proc/acpi/wakeup:

Device	S-state	  Status   Sysfs node
P0P4	  S4	 disabled  pci:0000:00:1e.0
MC97	  S4	 disabled  
USB1	  S4	 disabled  pci:0000:00:1d.0
USB2	  S4	 disabled  pci:0000:00:1d.1
USB3	  S4	 disabled  pci:0000:00:1d.2
USB4	  S4	 disabled  pci:0000:00:1d.3
EUSB	  S4	 disabled  pci:0000:00:1d.7
PS2K	  S4	 disabled  pnp:00:09
PS2M	  S4	 disabled  pnp:00:0a
GBEN	  S4	 disabled  

It appears that PS2K is the keyboard.  If I write "PS2K" to 
/proc/acpi/wakeup, I get:

ACPI: 'PS2M' and 'PS2K' have the same GPE, can't disable/enable one seperately

Apart from the misspelling, this doesn't bode well for making the
keyboard a wakeup device.  Furthermore, these values are not
properly tied to the values in sysfs.  For example, after

	echo enabled >/sys/devices/pci0000:00/0000:00:1d.7/power/wakeup

the EUSB line in /proc/acpi/wakeup still says disabled.

What next?

Alan Stern