Can not finish suspend test

[Jerry Kao]

fwts, Version V14.08.00, 2014-08-21 12:52:46

Can not run s3 test with fwts v14.08. (fwts s3 --s3-multiple=5)
System can enter/resume suspend once, then stuck with terminal message
u@u-HP-340-G2:~$ test. (Suspending) : 0.0% \

When set --pm-method=utils, can finish s3 test.

This issue still can be seen on fwts 14.07
Can reproduced on BSW, HSW, BTM platforms.

[Alberto Milone (albertomilone)]

The log shows the following problem:

Error from Logind: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Did not
receive a reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

How are you testing fwts? Are you using ssh?

[Jerry Kao (jerry.kao)]

@Alberto

No, we just test on the local.

test steps
1. bootup system
2. run s3 test in console "sudo fwts s3 --s3-multiple=5"

[Alberto Milone (albertomilone)]

what Ubuntu release are you using? 14.04?

[Jerry Kao (jerry.kao)]

@Alberto
yes, 14.04

[Alberto Milone (albertomilone)]

This looks like a problem in Logind.

Detecting the power method.
Response to CanSuspend is yes
User allowed to execute the CanSuspend action
Using logind as the default power method.
Requesting Suspend action
Error from Logind: Timeout was reached
Suspend status: true

What I can do is catch the error and make sure that we switch back to the sysfs backend as a fallback.

[kaxing (kaxing)]

As a reference. fwts 14.08 on another system does not have the same issue.

[Gabriel Zhi Chen (gabrielzchen)]

I could reproduce the issue on Lenovo P700-SN9 (Messi-1) in Beijing QA lab.

I tried 3 fwts version on the machine, 14.03, 14.08 and 14.12.

For fwts 14.03, executing successful;

For fwts 14.08 and 14.12, after system resume back, it is still in suspending, can not finish.

Command:
u@Messi-1:~$ sudo fwts s3 --s3-multiple=1
u@Messi-1:~$ test. (Suspending) : 0.0% \

[Alberto Milone (albertomilone)]

What happens if you reproduce the error ("sudo fwts s3 --s3-multiple=5"), then (without rebooting) you call fwts in the following way? (please attach the log)

sudo fwts --pm-method=sysfs --s3-multiple=5 s3

[Gabriel Zhi Chen (gabrielzchen)]

I try to reproduce the issue with fwts 15.07.00 on test machine https://certification.canonical.com/hardware/201412-16288/

***************
A
u@Sting2-3:~$ sudo fwts s3 --s3-multiple=30
[sudo] password for u:
Running 1 tests, results appended to results.log
Test: S3 suspend/resume test.
   S3 suspend/resume test. 6 passed, 30 failed

Please refer to results-1.log

*****************
B
Then I execute another S3 30 cycle following:
u@Sting2-3:~$ sudo fwts s3 --s3-multiple=1 --s3-min-delay=30 --s3-max-delay=30
[sudo] password for u:
Running 1 tests, results appended to results.log
Test: S3 suspend/resume test.
   S3 suspend/resume test. (Suspending) : 0.0% \

The cycle blocked at the 8th S3;
System under suspend, the power LED blink, and never wake up;
I wait about 5 minutes and press power button;
System resume back but it is blocked here, please refer to screenshot.jpg;
I canceled the cycle by pressing Ctrl+c. Can not get any fwts result log here :(

******************
C
Then I use command from Alberto to try again:
u@Sting2-3:~$ sudo fwts --pm-method=sysfs --s3-multiple=5 s3
[sudo] password for u:
Running 1 tests, results appended to results.log
Test: S3 suspend/resume test.
   S3 suspend/resume test. (Suspending) : 0.0% \

System get the same result with B at the 1th S3.
I wait a while and press power button;
System resume back and goes to the 2nd S3.
Please refer to results-2.log

[Alberto Milone (albertomilone)]

just to confirm, if you reboot, and run only the following command (i.e. only with --pm-method=sysfs), can you still reproduce the problem? (please attach the log)

sudo fwts --pm-method=sysfs --s3-multiple=5 s3

[Colin Ian King (colin-king)]

Any more updates on this bug? If not, I will close it in Jan 2016.

[Alex Hung (alexhung)]

I don't think we are experiencing this anymore