Public bug reported:
current build number: 256
device name: krillin
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2015-03-22 22:01:56
version version: 256
version ubuntu: 20150312
version device: 20150310-3201c0a
version custom: 20150216-561-29-186
While debugging the suspend process with my krillin, I noticed that
sometimes ubuntu-push-client holds a powerd sysstate for too long
(minutes), blocking the suspend process entirely.
Follows the log I got from powerd:
Mar 22 23:09:21 ubuntu-phablet powerd[964]: handle_requestSysState from :1.92
(ubuntu push client) - ACTIVE (1)
Mar 22 23:09:21 ubuntu-phablet powerd[964]: name_watch_add: looking for :1.92
Mar 22 23:09:21 ubuntu-phablet powerd[964]: watching :1.92 to see when it
disappears on dbus
Mar 22 23:09:21 ubuntu-phablet powerd[964]: libsuspend: acquire_wake_lock:
powerd_power_request
Mar 22 23:09:21 ubuntu-phablet powerd[964]: handle_requestSysState - SUCCESS
Mar 22 23:09:21 ubuntu-phablet powerd[964]: Enqueue state change to ACTIVE
Mar 22 23:09:21 ubuntu-phablet powerd[964]: exiting suspend
Mar 22 23:09:21 ubuntu-phablet powerd[964]: libsuspend: calling exit_suspend
Mar 22 23:09:21 ubuntu-phablet kernel: [ 1397.544062]PM: suspend exit
2015-03-23 02:09:21.573597769 UTC
Mar 22 23:09:21 ubuntu-phablet kernel: [ 1397.544113]active wakeup source:
MT662x
Mar 22 23:09:21 ubuntu-phablet kernel: [ 1397.544129]active wakeup source: alarm
Mar 22 23:09:21 ubuntu-phablet kernel: [
1397.554088][Ker_PM][request_suspend_state]wakeup (3->0) at 1397540686404
(2015-03-23 02:09:21.583610000 UTC)
Mar 22 23:09:21 ubuntu-phablet powerd[964]: calling wait_for_next_alarm
Mar 22 23:09:21 ubuntu-phablet kernel: [
1397.563938][WMT-CTRL][W]wmt_ctrl_rx:wmt_ctrl_rx be signaled, but no rx
data(200)
Mar 22 23:09:22 ubuntu-phablet powerd[964]: libsuspend: exit_suspend succeeded
Mar 22 23:09:22 ubuntu-phablet powerd[964]: Emitting signal for transition to
state ACTIVE (1)
Mar 22 23:09:22 ubuntu-phablet powerd[964]: Transition to ACTIVE complete
Mar 22 23:09:22 ubuntu-phablet powerd[964]: libsuspend: release_wake_lock:
powerd_power_request
Mar 22 23:09:22 ubuntu-phablet powerd[964]: handle_requestWakeup from :1.70 -
indicator-datetime, 1427119200
Mar 22 23:09:22 ubuntu-phablet powerd[964]: void
{anonymous}::reset_alarm_clock() found 3 remaining wakeup requests
Mar 22 23:09:22 ubuntu-phablet powerd[964]: setting hardware wakeup time to
2015-03-23 11:00:00 for indicator-datetime
Mar 22 23:12:10 ubuntu-phablet powerd[964]: handle_requestWakeup from :1.92 -
ubuntu push client, 1427077030
Mar 22 23:12:10 ubuntu-phablet powerd[964]: void
{anonymous}::reset_alarm_clock() found 4 remaining wakeup requests
Mar 22 23:12:10 ubuntu-phablet powerd[964]: setting hardware wakeup time to
2015-03-22 23:17:10 for ubuntu push client
Mar 22 23:12:10 ubuntu-phablet powerd[964]: handle_clearSysState from :1.92,
cookie: a840fa3a-fdcf-4178-8efe-d4d3aca46eb2
Mar 22 23:12:10 ubuntu-phablet powerd[964]: clear_sys_request: ubuntu push
client - :1.92
Mar 22 23:12:10 ubuntu-phablet powerd[964]: name_watch_remove: looking for :1.92
Mar 22 23:12:10 ubuntu-phablet powerd[964]: name_watch: ref_count for :1.92 is
now 0
Mar 22 23:12:10 ubuntu-phablet powerd[964]: no longer watching :1.92, there are
no more requests
Mar 22 23:12:10 ubuntu-phablet powerd[964]: libsuspend: acquire_wake_lock:
powerd_power_request
Mar 22 23:12:10 ubuntu-phablet powerd[964]: Enqueue state change to SUSPEND
Mar 22 23:12:10 ubuntu-phablet powerd[964]: libsuspend: prepare_suspend.
Mar 22 23:12:10 ubuntu-phablet powerd[964]: Emitting signal for transition to
state SUSPEND (0)
Mar 22 23:12:10 ubuntu-phablet powerd[964]: entering suspend
Mar 22 23:12:10 ubuntu-phablet powerd[964]: libsuspend: calling enter_suspend
Mar 22 23:12:10 ubuntu-phablet powerd[964]: libsuspend: enter_suspend succeeded
Mar 22 23:12:10 ubuntu-phablet powerd[964]: Transition to SUSPEND complete
Mar 22 23:12:10 ubuntu-phablet powerd[964]: libsuspend: release_wake_lock:
powerd_power_request
It took ubuntu-push-client 169 seconds to release the sysstate from
powerd, and that probably only happened after powerd triggered the alarm
that was scheduled by ubuntu-push-client.
** Affects: canonical-devices-system-image
Importance: Undecided
Status: New
** Affects: ubuntu-push (Ubuntu)
Importance: Undecided
Status: New
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1435109
Title:
Push-client frequently blocking phone suspend
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435109/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
