Comment 5 for bug 53042

Revision history for this message
Ram Yalamanchili (ramyinc) wrote :

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?