From: Pavel Machek <pavel@ucw.cz>
To: Olaf Dietsche <olaf+list.linux-acpi@olafdietsche.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
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: Thu, 7 Jun 2007 12:23:04 +0000 [thread overview]
Message-ID: <20070607122303.GA8938@ucw.cz> (raw)
In-Reply-To: <87wsykpweu.fsf@goat.bogus.local>
Hi!
> > Second, you can use PM_TRACE (Documentation/power/s2ram.txt) to find the
> > place where it really fails.
>
> First I augmented my minimal config kernel with some TRACE_RESUME()s:
>
> --- a/kernel/power/main.c 2007-05-27 23:48:05.000000000 +0200
> +++ b/kernel/power/main.c 2007-06-03 22:28:46.000000000 +0200
> @@ -223,6 +223,7 @@
> pr_debug("PM: Finishing wakeup.\n");
> suspend_finish(state);
> Unlock:
> + TRACE_RESUME(error);
> mutex_unlock(&pm_mutex);
> return error;
> }
> @@ -303,6 +304,7 @@
> error = enter_state(state);
> else
> error = -EINVAL;
> + TRACE_RESUME(error);
> return error ? error : n;
> }
...
> I got alternating
> hash matches drivers/base/power/resume.c:58
> and
> hash matches kernel/power/main.c:307
>
> > First, you can check if the patch
> >
> > http://www.sisk.pl/kernel/hibernation_and_suspend/2.6.22-rc3/patches/20-ACPI-preserve-the-ebx-value-in-acpi_copy_wakeup_routine.patch
>
> Then I applied this patch, but it doesn't change anything.
>
> But either way the script never reaches "shutdown -rn now". So, it
> seems, that my laptop does a full resume every other reboot, but it
> never returns to userspace.
But it returns to kernel... can you use more trace points to figure
out where it hangs?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-06-07 12:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070613173925.GA20628@gamma.logic.tuwien.ac.at>
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
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 [this message]
2007-06-07 19:54 ` Olaf Dietsche
2007-06-07 21:15 ` Pavel Machek
2007-06-02 0:07 ` Indan Zupancic
2007-06-02 4:36 ` Andrey Borzenkov
2007-06-12 15:31 ` Pavel Machek
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=20070607122303.GA8938@ucw.cz \
--to=pavel@ucw.cz \
--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