Syslog full of spam from alarm settings - is this draining battery?

Bug #1519543 reported by Neil McPhail on 2015-11-24
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu Clock App
Undecided
Unassigned

Bug Description

I have been trying to find the cause of excessive battery drain on my krillin device running OTA8. My syslog is full of entries like -

Nov 24 23:37:18 ubuntu-phablet powerd[974]: libsuspend: release_wake_lock: powerd_power_request
Nov 24 23:42:18 ubuntu-phablet powerd[974]: worker thread finished waiting for hw alarm
Nov 24 23:42:18 ubuntu-phablet powerd[974]: Emitting wakeup signal
Nov 24 23:42:18 ubuntu-phablet powerd[974]: worker thread is finished working; calling join()
Nov 24 23:42:18 ubuntu-phablet powerd[974]: worker thread is destroyed.
Nov 24 23:42:18 ubuntu-phablet powerd[974]: void {anonymous}::reset_alarm_clock() found 35 remaining wakeup requests
Nov 24 23:42:18 ubuntu-phablet powerd[974]: setting hardware wakeup time to 2015-11-25 07:00:00 for indicator-datetime
Nov 24 23:42:18 ubuntu-phablet powerd[974]: starting hardware alarm worker thread
Nov 24 23:42:18 ubuntu-phablet powerd[974]: calling wait_for_next_alarm

Running 'grep "Nov 24" /var/log/syslog | grep reset_alarm_clock | wc -l' gives > 1300 occurrences. Is this being called excessively and killing my battery? I'm not used to seeing such rapid battery drain on this device.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers