DJA wrote:
A suspend should NEVER result in a failure upon restart.
Should, but does. Often.
Suspend is supposed to stop all running processes, write the contents
of memory to disk (including video memory), and shutdown the system
(or put it in a very low power mode - I use suspend here to cover all
versions of stopping the computer outside of turning it off).
I believe (too lazy to look it up) that what you describe is called
Hibernate (save to disk). Suspend is save to RAM.
It depends upon the system and discussion. I've seen suspend, hibernate
and sleep to name three (all in reference to laptops and desktops). In
any case, even given the case where memory contents are not written to
disk, the system should still NEVER fail upon restart. All pending
operations should be stopped, write caches flushed, files closed, and no
disk access allowed until the system wakes up again.
[SNIP complicated explanation]
I don't care how fsck'd up ACPI is or anything else. I still assert that
a suspend/hibernate/sleep should NEVER result in a failure upon a
restart. The case where power fails before the suspend/hibernate/sleep
is completed does not count because in this case the operation never
completed (the system didn't actually suspend/hibernate/sleep).
If the hardware is too fsck'd up to do it properly, then it should not
be implemented at all. If the developer can't make the supporting
software work properly, then the software should not be released until
the developer can.
Of course, we all know it's a Wintel world and everything is supposed to
be broken, at least partially if not completely. ;)
PGA
--
Paul G. Allen, BSIT/SE
Owner, Sr. Engineer
Random Logic Consulting
http://www.randomlogic.com
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
