This is really just a POC to highlight the problem. The private log was interesting in my case:
Sat Jul 15 10:07:10 CEST 2006: acpi: sleep.sh: Starting suspend Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Completed resume Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Starting suspend Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Was called too soon (0 seconds ago), exiting Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Starting suspend Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Was called too soon (0 seconds ago), exiting Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Starting suspend Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Was called too soon (0 seconds ago), exiting Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Starting suspend Sat Jul 15 10:07:34 CEST 2006: acpi: sleep.sh: Was called too soon (0 seconds ago), exiting You can see 4 consecutive acpi sleep requests immediately after resume. If they weren't ignored the laptop would possible go thru the routine 4 times at the minimum. Can we get someone from power management to take a look at this? -- Avoid acpi button event jitter by having a ignore-event timer https://launchpad.net/bugs/53042 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
