[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0707151914450.28934-100000@netrider.rowland.org>
Date: Sun, 15 Jul 2007 19:15:47 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: david@...g.hm
cc: "Rafael J. Wysocki" <rjw@...k.pl>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Huang, Ying" <ying.huang@...el.com>,
Jeremy Maitin-Shepard <jbms@....edu>,
Kyle Moffett <mrmacman_g4@....com>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Pavel Machek <pavel@....cz>,
pm list <linux-pm@...ts.linux-foundation.org>,
Al Boldi <a1426z@...ab.com>
Subject: Re: Hibernation considerations
On Sun, 15 Jul 2007 david@...g.hm wrote:
> >> for a pure hibernate mode, you will be powering off the box after saving
> >> the suspend image. why are there any special ACPI modes involved?
> >
> > Because, for example, on my machine the status of power supply (present
> > vs not present) is not updated correctly after the restore if ACPI callbacks
> > aren't used during the hibernation. That's just experience and it's in line
> > with the ACPI spec.
>
> so if a machine is actually powered off the /dev/suspend process won't
> work?
>
> remember that the system may run a different OS between the hibernate and
> the resume, makeing any assumptions about what state the hardware is in
> when you start the resume is a problem.
As I understand it, running a different OS between the hibernate and
the resume would violate the ACPI spec.
Alan Stern
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists