On a device/in a situation which reproduces this, can you please run
udevadm monitor -e
I expect that there is a high frequency of uevents related to the
battery from the kernel's battery driver. These get relayed through udev
and upower to U-S-S. In particular we need to see if there are any
properties which actually change, i. e. whether the battery goes crazy
or the bat driver has a bug to fire a ginormous amount of uevents (which
keeps significant parts of the system busy). It's of course possible
that there are no uevents but upower manages to get stuck in some kind
of loop. But that's less probable as it never happened on other systems.
The recent "dmesg" output would also be interesting, in case that the
driver reports some error there.
Thanks!
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337200
Title:
High CPU due to excessive device changed signals from upower
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
