The latest krillin kernel suppresses unnecessary messages so this is
largely fixed.
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Changed in: upower (Ubuntu RTM)
Status: Confirmed => Fix Released
** Changed in: canonical-devices-system-image
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
This bug was fixed in the package ubuntu-system-settings -
0.3+15.04.20141210~rtm-0ubuntu1
---
ubuntu-system-settings (0.3+15.04.20141210~rtm-0ubuntu1) 14.09; urgency=low
[ Ken VanDine ]
* Support UPower 0.99 (LP: #1337200, #1390629)
[ Ubuntu daily release ]
* New rebuild for
** Changed in: ubuntu-system-settings (Ubuntu RTM)
Status: Invalid => In Progress
** Changed in: ubuntu-system-settings (Ubuntu RTM)
Assignee: (unassigned) => Ken VanDine (ken-vandine)
** Changed in: ubuntu-system-settings (Ubuntu RTM)
Importance: Undecided => High
** Branch linke
pitti: because the problem is the kernel sending way too much
uevents related with power
which makes upower to be quite a bit verbose, and dbus as well (on
krillin only)
rsalveti: that's then not really a duplicate
rsalveti: #1337200 is about queueing up d-bus signals while a process
is slee
Un-duplicating, as 1375152 is private. I rather made 1375152 a duplicate
of this one.
** This bug is no longer a duplicate of private bug 1375152
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337200
*** This bug is a duplicate of bug 1375152 ***
https://bugs.launchpad.net/bugs/1375152
** This bug has been marked a duplicate of private bug 1375152
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
** Changed in: canonical-devices-system-image
Importance: Undecided => High
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Milestone: None => r1
** Changed in: canonical-devices-system-image
Assignee: (unass
** Changed in: upower (Ubuntu RTM)
Importance: Undecided => High
** Changed in: upower (Ubuntu RTM)
Status: New => Confirmed
** Changed in: ubuntu-system-settings (Ubuntu RTM)
Status: New => Invalid
** Changed in: ubuntu-system-settings (Ubuntu)
Status: In Progress => Inv
I've confirmed the transition to upower 0.99 fixes this issue, really
nice improvement all around.
--
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 chang
I've built powerd, upowerd, indicator-power and ubuntu-system-settings
in rtm silo 16 for testing.
--
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 chang
> My new theory is dbus-daemon is spinning out of control because of
upower, probably because indicator-power is still subscribed to it.
That, and powerd as well for the record.
Thanks for the logs!
* udevadm.log doesn't look surprising: We get one event for each of the
four power_supply device
After attempting to work around this in ubuntu-system-settings, I don't
think it's possible. The problem seems to be upower pushing dbus-
daemon's load high enough that slows down or blocks dbus calls.
** Also affects: upower (Ubuntu)
Importance: Undecided
Status: New
** Package change
** Attachment added: "udevadm.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4260518/+files/udevadm.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "upower-monitor.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4260520/+files/upower-monitor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
** Attachment added: "dbus-monitor.log"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4260519/+files/dbus-monitor.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
I attached udevadm.log, upower-monitor.log and dbus-monitor.log which
was generated over a period with a number of suspend and resumes. This
was all with system-settings' battery plugin removed, so nothing from
settings listening for upower. I also never had system-settings
completely hang, but s
I checked wall charger yesterday and it seems the behavior is the same.
IMO this is a separate bug in that the device should be able to suspend
when on the wall charger as this is not an active usb data connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
My branch that disconnects from the signals on suspend and connect again
on resume doesn't really fix this. I did make the system-settings code
more efficient, but actually it doesn't connect to device-changed
signals. Only device-added and device-removed. There are some places
where we call som
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Incomplete => In Progress
--
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
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/lp1337200
** Branch linked: lp:~ken-vandine/ubuntu-system-settings/rtm-lp1337200
--
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:
OK, Pat's upower log also by and large just reflects the kernel events.
We discussed that on IRC, and we think that there's two different issues
here:
* The main problem is that system-settings subscribes to D-BUS signals
(from upower), and then goes to sleep. When it wakes back up, it
receives a
** Attachment added: "output of upower"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4260030/+files/up.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Update: turns out that the udevadm log from above is irrelevant -- it
was taken when system-settings was *not* spinning. So this is back to
being the most likely cause. Can you please do a monitoring event while
system-settings *is* spinning?
--
You received this bug notification because you are
That shows that the kernel sends us an update for all 4 power supplies
every 10 seconds, which doesn't sound "excessive". So I'm glad that we
at least ruled out this end.
So going one step up the stack, could you run "upower --monitor-detail"
when this happens? In theory this should exactly mirror
(It's not triaged for me -- I can't reproduce this at all, and I don't
have a Krillin)
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Triaged => Incomplete
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug n
** Tags added: ota-1 rtm14
--
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:
ht
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
** Changed in: ubuntu-system-settings (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
This is the output from "udevadm monitor -e" over the course of a little
over a minute
** Attachment added: "Output from udevadm monitor -e"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4259977/+files/upower.log
--
You received this bug notificati
dmesg from the same time as the udevadm output attached previously
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1337200/+attachment/4259990/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I think I've been seeing this bug too, but haven't looked into it in
detail. Basically, if I leave the phone idle overnight, it's extremely
slow when I try to use it in the morning... and dbus-daemon is
constantly pegging the CPU. 'top' generally shows that dbus-daemon has
a few hours worth of C
(I'm still subscribed, just unassigning while this is incomplete)
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
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
p
@martin would you mind looking at this and giving feedback
** Summary changed:
- U-S-S sluggish after some hours, high CPU
+ High CPU due to excessive device changed signals from upower
** Changed in: ubuntu-system-settings (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
--
You rec
34 matches
Mail list logo
