From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
pm list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH -mm] Hibernation: Check if ACPI is enabled during restore in the right place
Date: Thu, 6 Sep 2007 01:56:03 +0000 [thread overview]
Message-ID: <20070906015603.GA5097@ucw.cz> (raw)
In-Reply-To: <200709020021.37881.rjw@sisk.pl>
On Sun 2007-09-02 00:21:37, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki <rjw@sisk.pl>
>
> The following scenario leads to total confusion of the platform firmware on
> some boxes (eg. HPC nx6325):
> * Hibernate with ACPI enabled
> * Pass "acpi=off" to the boot kernel
>
> To prevent this from happening it's necessary to check if ACPI is enabled (and
> enable it if that's not the case) _right_ _after_ control has been transfered
> from the boot kernel to the image kernel, before device_power_up() is called
> (ie. with interrupts disabled). Enabling ACPI after calling device_power_up()
> turns out to be insufficient.
>
> For this reason, introduce new hibernation callback ->leave() that will be
> executed before device_power_up() by the restored image kernel. To make it
> work, it also is necessary to move swsusp_suspend() from swsusp.c to disk.c
> (it's name is changed to "create_image", which is more up to the point).
>
> Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
ACK.
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2007-09-06 9:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-01 22:21 [PATCH -mm] Hibernation: Check if ACPI is enabled during restore in the right place Rafael J. Wysocki
2007-09-06 1:56 ` Pavel Machek [this message]
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=20070906015603.GA5097@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--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