[mako] upower consuming over 17% cpu when in idle
Bug #1420395 reported by
Pat McGowan
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Incomplete
|
Low
|
Canonical Phone Foundations | ||
upower (Ubuntu) |
Confirmed
|
Low
|
Ricardo Salveti |
Bug Description
From the meta battery bug # 1372413
mako running 191
As device was not suspending and battery level running down, upower is reported at 17%+ cpu by the cpustat tool
mpdecision and systemd-udevd also change their behavior.
The upower cpu consumption is just a side effect of the amount of battery related events the kernel send, and specific to mako.
Changed in upower (Ubuntu): | |
status: | New → Confirmed |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → ww11-2015 |
Changed in upower (Ubuntu): | |
assignee: | nobody → Ricardo Salveti (rsalveti) |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Ricardo Salveti (rsalveti) |
Changed in canonical-devices-system-image: | |
milestone: | ww11-2015 → ww13-ota |
Changed in canonical-devices-system-image: | |
milestone: | ww11-ota → ww13-ota |
Changed in canonical-devices-system-image: | |
milestone: | ww13-ota → ww15-2015 |
Changed in canonical-devices-system-image: | |
importance: | High → Low |
Changed in upower (Ubuntu): | |
importance: | High → Low |
Changed in canonical-devices-system-image: | |
milestone: | ww15-2015 → ww17-2015 |
Changed in canonical-devices-system-image: | |
assignee: | Ricardo Salveti (rsalveti) → Canonical Phone Foundations (canonical-phonedations-team) |
Changed in canonical-devices-system-image: | |
milestone: | ww17-2015 → ww21-2015 |
Changed in canonical-devices-system-image: | |
milestone: | ww21-2015 → none |
To post a comment you must log in.
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.