Also, if I wake it up before it wake itself up automatically with fwts, this issue won't happen
ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 05:17:01 AM EDT -0.234698 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. (Wake it up manually after 1 minute) S4 hibernate/resume test. 4 passed, 1 failed Tue 24 Jun 2014 05:19:45 AM EDT -0.437938 seconds ubuntu@201401-14542:~$ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device-check-delay=45 --s4-sleep-delay=120; sleep 3 ;sudo hwclock -r Tue 24 Jun 2014 05:20:33 AM EDT -0.812936 seconds Running 1 tests, results appended to results.log Test: S4 hibernate/resume test. (Let it wake itself up) S4 hibernate/resume test. 4 passed, 1 failed hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory
Also, if I wake it up before it wake itself up automatically with fwts, this issue won't happen
ubuntu@ 201401- 14542:~ $ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device- check-delay= 45 --s4-sleep- delay=120; sleep 3 ;sudo hwclock -r 201401- 14542:~ $ sudo hwclock -r ; sleep 3;sudo fwts -P s4 --s4-device-check --s4-device- check-delay= 45 --s4-sleep- delay=120; sleep 3 ;sudo hwclock -r
Tue 24 Jun 2014 05:17:01 AM EDT -0.234698 seconds
Running 1 tests, results appended to results.log
Test: S4 hibernate/resume test.
(Wake it up manually after 1 minute)
S4 hibernate/resume test. 4 passed, 1 failed
Tue 24 Jun 2014 05:19:45 AM EDT -0.437938 seconds
ubuntu@
Tue 24 Jun 2014 05:20:33 AM EDT -0.812936 seconds
Running 1 tests, results appended to results.log
Test: S4 hibernate/resume test.
(Let it wake itself up)
S4 hibernate/resume test. 4 passed, 1 failed
hwclock: select() to /dev/rtc to wait for clock tick timed out: No such file or directory