After profiling upower, this is actually not an issue in there, as the
only thing it is doing is getting the battery change event from the
kernel, updating the internal struct and sending another dbus message so
the clients could see the changes.
The main issue here is that the kernel is sending
** Changed in: canonical-devices-system-image
Milestone: ww11-ota = ww13-ota
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1420395
Title:
upower consuming over 17% cpu
Status in
** Changed in: canonical-devices-system-image
Milestone: ww11-2015 = ww13-ota
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1420395
Title:
upower consuming over 17% cpu
Status
** Changed in: upower (Ubuntu)
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Status: New = Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
Milestone: None = ww11-2015
It seems the problem relies more on the kernel side and with the amount
of events the battery driver sends to the userspace (even when there is
no change).
udevadm monitor is already enough to show the amount of kernel events
the battery driver sends to the userspace.
--
You received this bug
As an example, the amount of upower events when connecting/disconnecting the
usb cable (charger) on mako:
root@ubuntu-phablet:/sys# upower -m
Monitoring activity from the power daemon. Press Ctrl+C to cancel.
[03:54:38.613] device changed:
/org/freedesktop/UPower/devices/battery_battery
** Attachment added: upowerd-procs.ods
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420395/+attachment/4316529/+files/upowerd-procs.ods
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
7 matches
Mail list logo
