On Fri, 2007-05-04 at 10:51 -0400, Alan Stern wrote: > Exactly because we are waffling on this issue. If we settled the matter > once and for all (devices must ALWAYS be reinitialized after the snapshot > is restored) then we wouldn't have those problems. (We might have other > problems though...) From what I've understood so far, ACPI is very unhappy on some machines if you go to S5 after hiberation. I still don't understand why, if the ACPI code would properly re-initialise itself (treat ACPI as a device and apply your "devices must ALWAYS be reinitialized after the snapshot is restored") then this shouldn't be possible to happen. And at that point I agree that the issue becomes completely orthogonal. (btw, it's always possible right now to go to S5 instead of S4 when doing hibernation simply by changing /sys/power/disk to "shutdown") johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
