Messages in this thread | | | Date | Sat, 21 Jul 2007 12:35:50 -0700 (PDT) | From | david@lang ... | Subject | Re: Hibernation considerations |
| |
On Sat, 21 Jul 2007, Pavel Machek wrote:
> Hi! > >> Pavel Machek <pavel@ucw.cz> writes: >> >> [snip] >> >>> So it will be break at least battery status and "AC plugged in" >>> status, because those are handled by ACPI and we do not know how to >>> control them by hand. >> >> It seems that it should be possible to initialize ACPI as if the system >> just booted up normally. Then battery status and such should be >> correct, since they are correct after normal initialization. >> >> It should be possible to make hibernate look just like a reboot to all >> of the devices, including ACPI stuff. > > Patch to make that work with swsusp/shutdown method would be indeed > welcome. It does not work today.
is this a problem in the restore path?
with the kexec approach (and ignoring suspend to ram and disk for the moment) the system will actually get shutdown completely after the image is written. on resume it gets cold booted. at this point the ACPI stuff should have no problem
now if the ACPI drivers are storing something in ram about the battery status and AC power status, but don't re-check after the resume, it seems to me that they can't possibly be reliable anyway. if they do re-check after the resume then where's the problem?
David Lang - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |