Re: Hibernation considerations

Stefan Seyfried
2007-08-01T16:58:55Z

Hi,

Sorry for joining late, just a small annotation:

On Tue, Jul 17, 2007 at 01:18:13PM -0700, david@lang.hm wrote:

> non-ACPI hibernate
>
> since the box powers off
> it uses zero power while suspended
> another OS could be run before a resume
> hardware can be swapped, suspend image could be sent around the world to be restored on another system.
> restore makes no assumptions about the state of the hardware when it is restored
> restore is slower (full BIOS boot is required)
> should be able to work on just about any hardware (the limit is the ability to initialize the devices)
>
>
> ACPI suspends
>
> since the box never completely powers off:A

wrong

> a complete power failure breaks the suspend

wrong

> the OS must remain in control so other uses must be prevented.
> hardware must remain in the ACPI state from suspend until restore.
> restore can be faster (some initialization may be able to be skipped)
> requires ACPI hardware support
>
> under the catagory of ACPI suspends you have

ACPI S4 turns off the machine completely and you can remove the battery (this
is even required somewhere in the spec). Any state saving is done in CMOS RAM
or flash.

But for example many Notebooks resume much faster if they go through the
ACPI S4 hooks during suspend (less than one second from "lid open" to "grub"
while they need ~10 seconds through the BIOS on a "normal" boot.
My Toughbook resumes on "Lid Opened" after S4, it doesn't after a shutdown.

So there will be differences.
I'm not saying that they are too important, but 20% faster resume still is
a good saving for me.

No need to restart this thread btw ;-)

Have fun,

Stefan
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)