The default S3 delay is 30 seconds. If the machine isn't sleeping for 30 seconds then quite rightly it has failed to meet the S3 test standard and is marked as failed.
S3 cycle 1 of 5 pm-suspend returned 0 after 12 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 12 seconds, less than the expected 30 seconds. S3 cycle 2 of 5 pm-suspend returned 0 after 11 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 11 seconds, less than the expected 30 seconds. S3 cycle 3 of 5 pm-suspend returned 0 after 12 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 12 seconds, less than the expected 30 seconds. S3 cycle 4 of 5 pm-suspend returned 0 after 11 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 11 seconds, less than the expected 30 seconds. S3 cycle 5 of 5 pm-suspend returned 0 after 11 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 11 seconds, less than the expected 30 seconds. The log states the machine ONLY slept for 11 or 12 seconds. This could indicate either the wake alarm is broken or that it is being manually woken up. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1028797 Title: fwts - S3 test gets unexpected wake up failed To manage notifications about this bug go to: https://bugs.launchpad.net/fwts/+bug/1028797/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
