Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#630002: dbus-daemon consuming CPU
237 views
Skip to first unread message
Simon McVittie
May 15, 2013, 12:10:02 PM5/15/13
to
On 15/05/13 16:43, Alexander Mansurov wrote:
> If I run htop, the two most CPU consuming processes are dbus-daemon
> and udisks.
dbus-daemon transports messages. If it's using a lot of CPU time, it
is likely to be a bug in whatever process is causing those messages.
According to the clock_gettime() calls, your strace log took less than
0.2 seconds to record. During that time, two separate instances of
"/usr/lib/gvfs/gvfs-gdu-volume-mo" connected to the system bus and
communicated with what looks like udisks.
Please check whether gvfs-gdu-volume-monitor is crashing and
restarting repeatedly, and whether udisks is misbehaving. I suspect
that the high CPU usage from dbus-daemon is a side-effect of something
wrong with one of those packages.
S
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
> If I run htop, the two most CPU consuming processes are dbus-daemon
> and udisks.
dbus-daemon transports messages. If it's using a lot of CPU time, it
is likely to be a bug in whatever process is causing those messages.
According to the clock_gettime() calls, your strace log took less than
0.2 seconds to record. During that time, two separate instances of
"/usr/lib/gvfs/gvfs-gdu-volume-mo" connected to the system bus and
communicated with what looks like udisks.
Please check whether gvfs-gdu-volume-monitor is crashing and
restarting repeatedly, and whether udisks is misbehaving. I suspect
that the high CPU usage from dbus-daemon is a side-effect of something
wrong with one of those packages.
S
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Michael Biebl
May 15, 2013, 12:20:02 PM5/15/13
to
Am 15.05.2013 18:06, schrieb Simon McVittie:
> On 15/05/13 16:43, Alexander Mansurov wrote:
>> If I run htop, the two most CPU consuming processes are dbus-daemon
>> and udisks.
>
> dbus-daemon transports messages. If it's using a lot of CPU time, it
> is likely to be a bug in whatever process is causing those messages.
>
> According to the clock_gettime() calls, your strace log took less than
> 0.2 seconds to record. During that time, two separate instances of
> "/usr/lib/gvfs/gvfs-gdu-volume-mo" connected to the system bus and
> communicated with what looks like udisks.
>
> Please check whether gvfs-gdu-volume-monitor is crashing and
> restarting repeatedly, and whether udisks is misbehaving. I suspect
> that the high CPU usage from dbus-daemon is a side-effect of something
> wrong with one of those packages.
This is most likely a (known) gvfs bug.
> On 15/05/13 16:43, Alexander Mansurov wrote:
>> If I run htop, the two most CPU consuming processes are dbus-daemon
>> and udisks.
>
> dbus-daemon transports messages. If it's using a lot of CPU time, it
> is likely to be a bug in whatever process is causing those messages.
>
> According to the clock_gettime() calls, your strace log took less than
> 0.2 seconds to record. During that time, two separate instances of
> "/usr/lib/gvfs/gvfs-gdu-volume-mo" connected to the system bus and
> communicated with what looks like udisks.
>
> Please check whether gvfs-gdu-volume-monitor is crashing and
> restarting repeatedly, and whether udisks is misbehaving. I suspect
> that the high CPU usage from dbus-daemon is a side-effect of something
> wrong with one of those packages.
It most often happens with a shared /home (e.g. when using NFS), i.e.
multiple gvfs instances trying to write to the same files.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624507
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
0 new messages