phone clock resets to Jan 1 2010 or 2014 during power tests

Bug #1475542 reported by Selene ToyKeeper
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-touch-session (Ubuntu)
New
Undecided
Unassigned

Bug Description

I'm not quite sure where to file this bug, but I've noticed that the phone's time/date reset to what appear to be manufacturer defaults sometimes while power tests are running This even happens sometimes after I force ntpdate to set the correct time.

On arale devices, the clock resets to 2010-01-01. On krillin devices, it resets to 2014-01-01. I don't think the bug is hardware-specific, but the symptoms are.

I've seen this symptom happen...
  - 3 times post-test on krillin
  - 12 times post-test on arale
  - 65 times pre-test on arale
  - 78 times pre-test on krillin

The tests generally do some setup (get online, install deps, configure the device, force the correct date via ntpdate), disconnect USB, measure performance for a while, reconnect, then collect additional logs and data. Most date-related errors are before the test runs, and are corrected before proceeding, but it's especially interesting when it happens during or after the test.

I see these date symptoms mostly during certain tests...
     89 power_usage_bt_on_wifi_disconnected
     52 power_usage_flight_mode_on
      2 power_usage_idle

Notably absent is the power_usage_display_on test, which suggests the issue probably does not occur when the screen is on with wifi enabled. It seems to happen during the tests where network access is turned off.

Power test logs are kept here: http://people.canonical.com/~platform-qa/power-results/?C=M;O=D
Each test set and test run there includes quite a bit of data and logs to help with debugging.

The specific recent test runs with this symptom are:
Arale tests:
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/1
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/5
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/6
2015-07-14_20:33:23-arale-58-power_usage_flight_mode_on/7
2015-07-15_03:02:28-arale-60-power_usage_flight_mode_on/3
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-15_03:33:10-arale-60-power_usage_bt_on_wifi_disconnected/4
2015-07-15_06:17:21-arale-59-power_usage_flight_mode_on/3
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/2
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/3
2015-07-15_07:09:48-arale-59-power_usage_bt_on_wifi_disconnected/4
2015-07-15_12:12:39-arale-60-power_usage_flight_mode_on/2
2015-07-15_12:12:39-arale-60-power_usage_flight_mode_on/3
2015-07-16_01:03:47-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-16_01:03:47-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-16_03:27:59-arale-61-power_usage_flight_mode_on/2
2015-07-16_13:26:50-arale-60-power_usage_idle/6
2015-07-16_13:26:50-arale-60-power_usage_idle/8
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/2
2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/3
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/2
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/3
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/4
2015-07-16_16:55:11-arale-60-power_usage_bt_on_wifi_disconnected/5
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/2
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/3
2015-07-16_19:32:27-arale-61-power_usage_bt_on_wifi_disconnected/4
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/2
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/3
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/4
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/5
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/6
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/7
2015-07-17_00:28:56-arale-61-power_usage_bt_on_wifi_disconnected/8

... and some on krillin last time I tested one:
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/2
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/3
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/4
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/5
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/6
2015-07-13_17:52:04-krillin-65-power_usage_flight_mode_on/7
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/1
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/2
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/3
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/4
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/5
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/6
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/7
2015-07-13_19:15:15-krillin-65-power_usage_bt_on_wifi_disconnected/8
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/2
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/3
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/6
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/7
2015-07-13_23:05:48-krillin-132-power_usage_flight_mode_on/8
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/1
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/2
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/3
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/4
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/6
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/7
2015-07-14_00:38:10-krillin-132-power_usage_bt_on_wifi_disconnected/8

Is there enough data in the logs there to identify the cause of this issue? I can collect more logs or command output if necessary, to include with future test runs.

Tags: power-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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