Fn-F3 is labelled for video, but it is doing a suspend :-/. It generates the 'button/sleep' event :-o. I have obviously misread it, or something in the BIOS is clearly AWOL. But as suspend wasn't suspending, just blanking the screen, that might explain why both screens blanked and I wondered what was (not) going on.
The suspend & hibernate delays seem to be process related. If I suspend/hibernate immediately after a resume, it happens normally. Given that suspend unhooks all the interrupts, and hibernate does likewise, I switched on logging in acpid and groped in the logs to see a time difference such as this
[QUOTE]Dec 21 15:22:51 harriet acpid: received input layer event "button/screenlock SCRNLCK 00000080 00000000"
Dec 21 15:22:51 harriet acpid: rule from 1541[82:82] matched
Dec 21 15:22:51 harriet acpid: notifying client 1541[82:82]
Dec 21 15:22:51 harriet acpid: rule from /etc/acpi/events/screenlock matched
Dec 21 15:22:51
harriet acpid: executing action "/etc/acpi/Decpower.sh"
Dec 21 15:23:59
harriet kernel: PM: Syncing filesystems ... done./QUOTE]
The first line is the event. There is an unexplained delay of over a minute that time (in bold). Once I have the sync, all happens quickly. Decpower.sh is as follows:
# Hopefully Manage to suspend/hibernate to disk
# Skip if we just in the middle of resuming.
test -f /var/lock/acpisleep && exit 0
sync; echo disk > /sys/power/state
Hardly a complicated or ambitious effort. Taking out the 'test' line doesn't improve things.
Any ideas Now?