From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alan Stern <stern@rowland.harvard.edu>
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 23:00:21 +0100 [thread overview]
Message-ID: <201002222300.21557.rjw@sisk.pl> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1002221623430.1264-100000@iolanthe.rowland.org>
On Monday 22 February 2010, Alan Stern wrote:
> 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?
Not without adding some debug code to the driver.
Which version of the kernel is this?
> > > 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.
This only means both will be enabled at the same time.
> Furthermore, these values are not properly tied to the values in sysfs.
They are independent and the sysfs values probably don't matter for these
devices. What are the contents of /proc/acpi/wakeup after writing PS2K to it?
Rafael
next prev parent reply other threads:[~2010-02-22 22:00 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201002212139.39746.rjw@sisk.pl>
2010-02-22 16:33 ` Two problems with system sleep Alan Stern
2010-02-22 16:33 ` Alan Stern
2010-02-22 18:45 ` Rafael J. Wysocki
2010-02-22 18:45 ` Rafael J. Wysocki
2010-02-22 21:33 ` Alan Stern
2010-02-22 22:00 ` Rafael J. Wysocki [this message]
2010-02-22 22:17 ` Alan Stern
2010-02-22 22:35 ` Rafael J. Wysocki
2010-02-22 22:35 ` Rafael J. Wysocki
2010-02-23 16:12 ` Alan Stern
2010-02-23 21:02 ` Rafael J. Wysocki
2010-02-23 21:35 ` Alan Stern
2010-02-23 23:08 ` Rafael J. Wysocki
2010-02-24 16:59 ` Alan Stern
2010-02-23 21:49 ` Dmitry Torokhov
2010-02-24 15:39 ` Alan Stern
2010-03-02 20:13 ` [RFC] Wakeup for PNP Alan Stern
2010-03-02 20:41 ` Bjorn Helgaas
2010-03-02 20:41 ` Bjorn Helgaas
2010-03-02 21:08 ` Alan Stern
2010-03-02 21:08 ` Alan Stern
2010-03-02 21:31 ` Dmitry Torokhov
2010-03-02 21:31 ` Dmitry Torokhov
2010-03-03 15:29 ` Alan Stern
2010-03-03 15:29 ` Alan Stern
2010-03-09 7:45 ` Dmitry Torokhov
2010-03-09 7:45 ` Dmitry Torokhov
2010-02-12 20:46 Two problems with system sleep Alan Stern
2010-02-13 0:13 ` Rafael J. Wysocki
2010-02-13 0:21 ` Greg KH
2010-02-14 18:36 ` Alan Stern
2010-02-14 21:47 ` Rafael J. Wysocki
2010-02-16 16:52 ` Alan Stern
2010-02-16 21:22 ` Rafael J. Wysocki
2010-02-17 18:10 ` Alan Stern
2010-02-17 20:43 ` Rafael J. Wysocki
2010-02-18 20:16 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201002222300.21557.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-pm@lists.linux-foundation.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.