From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Olaf Dietsche <olaf+list.linux-acpi@olafdietsche.de>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [2.6.22-rc3][ACPI?] Resume from s2r doesn't work.
Date: Sat, 02 Jun 2007 09:31:54 +1000 [thread overview]
Message-ID: <1180740714.9412.73.camel@nigel.suspend2.net> (raw)
In-Reply-To: <200706020037.16615.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
Hi.
On Sat, 2007-06-02 at 00:37 +0200, Rafael J. Wysocki wrote:
> On Saturday, 2 June 2007 00:17, Olaf Dietsche wrote:
> > "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> >
> > > On Friday, 1 June 2007 23:12, Olaf Dietsche wrote:
> > >> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> > >>
> > >> > On Friday, 1 June 2007 22:27, Olaf Dietsche wrote:
> > >> >> When I resume, everything seems to come up (fan becomes busy, disk and
> > >> >> dvd spin up for a short time),
> > >> >
> > >> > Hmm, what about the screen?
> > >>
> > >> When the laptop is dead, screen remains black.
> > >>
> > >> When I skip acpi_enter_sleep_state(), the screen works like everything
> > >> else.
> > >
> > > I think you should try s2ram (http://en.opensuse.org/s2ram) as the first step.
> >
> > It doesn't work. I tried all options "s2ram -f (-s, -p, -m, -r, -a 1, -a 2,
> > -a 3)" one after the other.
> >
> > Since the screen (or any other device) works without problems, when I
> > skip acpi_enter_sleep_state(), I don't think it's screen related.
>
> No, it might be, actually. If you skip acpi_enter_sleep_state(), your machine
> doesn't really suspend, so in fact you only confirm that your drivers implement
> .suspend() and .resume() hooks correctly.
Actually, you don't even confirm that. Chips that would be powered down
by entering the sleep state will not be powered down in this scenario,
so failures to properly reinitialise them in resume routines won't be
noticed.
Regards,
Nige
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-01 23:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 20:27 [2.6.22-rc3][ACPI?] Resume from s2r doesn't work Olaf Dietsche
2007-06-01 20:37 ` Rafael J. Wysocki
2007-06-01 21:12 ` Olaf Dietsche
2007-06-01 21:40 ` Rafael J. Wysocki
2007-06-01 22:17 ` Olaf Dietsche
2007-06-01 22:37 ` Rafael J. Wysocki
2007-06-01 23:31 ` Nigel Cunningham [this message]
2007-06-02 11:08 ` Mitch Davis
2007-06-03 21:20 ` Olaf Dietsche
2007-06-04 8:13 ` Rafael J. Wysocki
2007-06-04 16:43 ` Olaf Dietsche
2007-06-04 21:02 ` Rafael J. Wysocki
2007-06-07 19:50 ` Olaf Dietsche
2007-06-08 13:07 ` Olaf Dietsche
2007-06-07 12:23 ` Pavel Machek
2007-06-07 19:54 ` Olaf Dietsche
2007-06-07 21:15 ` Pavel Machek
2007-06-02 0:07 ` Indan Zupancic
2007-06-12 15:31 ` Pavel Machek
2007-06-13 17:39 ` Norbert Preining
2007-06-13 21:42 ` Rafael J. Wysocki
2007-06-13 19:56 ` Olaf Dietsche
2007-06-14 19:56 ` Pavel Machek
2007-06-15 12:35 ` Richard Hughes
2007-06-15 15:55 ` Olaf Dietsche
2007-06-14 18:13 ` Norbert Preining
2007-07-22 9:10 ` Pavel Machek
2007-08-12 16:52 ` Norbert Preining
2007-08-14 10:09 ` Pavel Machek
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=1180740714.9412.73.camel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=olaf+list.linux-acpi@olafdietsche.de \
--cc=rjw@sisk.pl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox