Firmware Test Suite

FWTS does not provide time to suspend when testing s3

Bug #1522292 reported by Pierre Equoy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Firmware Test Suite
Fix Released
Medium
Colin Ian King

Bug Description

Title: FWTS does not provide time to suspend when testing s3

Summary:
FWTS can be used to test S3 (suspend). However, it looks like only "time to resume" is provided. I tried on 2 different laptops and the "time to suspend" is never provided. E.g.:
Suspend/Resume Timings:
  Could not determine time to suspend.
  Resume: 2.070 seconds.

Steps:
1. Install latest version of fwts
2. Launch a S3 test such as:
fwts --s3-min-delay=60 --s3-max-delay=90 --s3-sleep-delay=90 --s3-multiple=3 s3

Expected results: Result logfile contains time to suspend and time to resume

Actual results: Result log file only contains time to suspend. It says it cannot determine time to suspend.

CPU: Intel(R) Core(TM) i5-4200U CPU @ 1.60GHz (4x)

GPU: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09)

Manufacturer: Dell Inc.

ProductName: Latitude E7440

BiosVersion: A10

See original description
Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Changed in fwts:
status: New → Confirmed
Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

Automatically attached

Revision history for this message
Pierre Equoy (pieq) wrote :

In addition to the attached logs, here are the logs from the two different laptops running the same command:

    fwts --s3-min-delay=60 --s3-max-delay=90 --s3-sleep-delay=90 --s3-multiple=3 s3

Revision history for this message
Pierre Equoy (pieq) wrote :
description: updated
Pierre Equoy (pieq)
Changed in fwts:
status: Confirmed → New
Colin Ian King (colin-king)
Changed in fwts:
importance: Undecided → Medium
assignee: nobody → Colin Ian King (colin-king)
status: New → In Progress
Revision history for this message
Colin Ian King (colin-king) wrote :

So it seems that the special tag marker that fwts inserts into the log sometimes gets dropped without making it into the kernel message log when a S3 is being triggered almost immediately afterwards for some reason. I'll add some more smarts into the kernel log scanner to pick up other messages that are written before/after this tag so we can at least work around this.

Revision history for this message
Colin Ian King (colin-king) wrote :

Fix sent to the fwts-devel mailing list for review: https://lists.ubuntu.com/archives/fwts-devel/2015-December/007100.html

Revision history for this message
Jeff Lane  (bladernr) wrote :

I'm just curious, so fwts times the "time to suspend" and "time to resume" by putting marker messages into the system logs (via syslog or klog?) and then does some math on the timestamps of the marker messages? (I have no other interest in this bug, it doesn't affect me, I just saw it mentioned and was curious).

Revision history for this message
Colin Ian King (colin-king) wrote :

@Jeff, basically, yes, it's the only simple way without making fwts + kernel interactions more difficult - if you really want *very* detailed stats then the best tool to use is using a suspend/resume analyse by Intel. I've blogged about it here:

http://smackerelofopinion.blogspot.co.uk/2015/08/identifying-suspendresume-delays.html

Revision history for this message
Pierre Equoy (pieq) wrote :

@Colin: Thanks for the quick fix!

Funny thing: the method used by FWTS is actually what we implemented at a higher level to do our testing with Checkbox. Since it looks like it will be fixed in the next FWTS release, we can drop our own implementation to rely on yours. Thanks again!

Colin Ian King (colin-king)
Changed in fwts:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.