Your message dated Thu, 4 Dec 2014 10:22:03 +0100 (CET)
with message-id <alpine.DEB.2.11.1412041020390.16214@hier>
and subject line Re: are you still experiencing the reported bug?
has caused the Debian Bug report #606414,
regarding upowerd runs at high %CPU constantly
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
606414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606414
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: upower
Version: 0.9.5-5
Severity: grave
Justification: renders package unusable
I'm seeing this in top:
top - 14:35:10 up 19:05, 4 users, load average: 0.38, 0.52, 0.70
Tasks: 144 total, 1 running, 143 sleeping, 0 stopped, 0 zombie
Cpu(s): 7.4%us, 1.6%sy, 0.0%ni, 90.4%id, 0.5%wa, 0.0%hi, 0.1%si
Mem: 3113732k total, 1341884k used, 1771848k free, 210376k buffers
Swap: 3903752k total, 0k used, 3903752k free, 651100k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24317 root 20 0 35988 27m 2664 D 49 0.9 3:05.42 upowerd
Typically, I'm seeing upowerd at >50% and up to >90%.
Running strace shows very frequent updates to files in /var/lib/upower.
A typical example is:
rename("/var/lib/upower/history-charge-DELL_0M7879-46-628.dat.6GSMNV",
"/var/lib/upower/history-charge-DELL_0M7879-46-628.dat") = 0
It is not clear that is enough to show this high of a load, but the updates
are far more frequent than I can imagine are needed.
This started to occur after a recent update. I generally use "apt-get -t
testing dselect-upgrade" so maybe I've mixed things up too much.
I have searched the upower pages but see no way to control update frequencies.
Or if it is event driven, something is generating events too frequently.
Any help appreciated.
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (900, 'stable'), (500, 'testing'), (100, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages upower depends on:
ii dbus 1.2.24-3 simple interprocess messaging syst
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.24-3 simple interprocess messaging syst
ii libdbus-glib-1-2 0.88-2 simple interprocess messaging syst
ii libglib2.0-0 2.24.2-1 The GLib library of C routines
ii libgudev-1.0-0 164-2 GObject-based wrapper library for
ii libimobiledevice1 1.0.2-1 Library for communicating with the
ii libplist1 1.3-2 Library for handling Apple binary
ii libpolkit-gobject-1-0 0.96-4 PolicyKit Authorization API
ii libupower-glib1 0.9.5-5 abstraction for power management -
ii libusb-1.0-0 2:1.0.8-2 userspace USB programming library
ii udev 164-2 /dev/ and hotplug management daemo
Versions of packages upower recommends:
ii pm-utils 1.3.0-3 utilities and scripts for power ma
ii policykit-1 0.96-4 framework for managing administrat
upower suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Since both Stuart and Paolo confirmed that the bug is gone, I'm closing
it herewith.
*t
---------- Forwarded message ----------
Date: Thu, 4 Dec 2014 10:09:54 +0800
From: Paolo Scarabelli
To: Tomas Pospisek
Subject: Re: are you still experiencing the reported bug?
Hi Tomas,
I confirm that the problem is solved for me.
Have a nice day,
Paolo
On Thu, Dec 4, 2014 at 6:15 AM, Tomas Pospisek wrote:
Hello Stuart, Tshepang and Paolo,
you reported bug http://bugs.debian.org/606414 against a version of
upower from Debian squeeze, respectively a version before wheezy.
I think everyone of you is running Debian wheezy or jessie by now. Does
any of you still experience that problem with either wheezy's or jessie's
version of upower?
It would be nice if you could test and reply, so this bug could be marked
as fixed in wheezy/jessie and closed.
Thanks,
*t
--- End Message ---
