[Userland-team] [OpenIndiana Distribution - Bug #1987] dbus taking 100% of cpu

illumos project devnull at illumos.org
Mon May 7 08:20:02 UTC 2012


Issue #1987 has been updated by Richard PALO.


not sure this is entirely related, but I notice another anomaly involving dbus.
Namely, when I  "ssh -X <host>" and run any gnome application, most frequently gedit, my session stalls,
that is simply exiting is blocked and needs to be abruptly stopped.

If I run a simple X program, like "xeyes", no problem.

Let me illustrate what is perfectly reproducible (here, anyway):
<pre>
richard at shuttleX:~$ ssh -X <hostname>
Last login: Mon May  7 10:02:51 2012 from <client>
OpenIndiana (powered by illumos)    SunOS 5.11    oi_151a3    March 2012
richard at smicro:~$ ps axuw | grep dbus
richard   4813  0.0  0.0 2080 1408 pts/1    S 10:04:13  0:00 grep dbus
root       358  0.0  0.0 3400 2076 ?        S 08:43:55  0:00 /usr/lib/dbus-daemon --system
gdm       3497  0.0  0.0 3508 1420 ?        S 08:44:18  0:00 /usr/bin/dbus-launch --exit-with-session
gdm       3498  0.0  0.0 3156 1976 ?        S 08:44:18  0:00 /usr/lib/dbus-daemon --fork --print-pid 6 --print-address 8 --session
richard at smicro:~$ xeyes 
richard at smicro:~$ ps axuw | grep dbus
richard   4821  0.0  0.0 2080 1408 pts/1    S 10:04:22  0:00 grep dbus
root       358  0.0  0.0 3400 2076 ?        S 08:43:55  0:00 /usr/lib/dbus-daemon --system
gdm       3497  0.0  0.0 3508 1420 ?        S 08:44:18  0:00 /usr/bin/dbus-launch --exit-with-session
gdm       3498  0.0  0.0 3156 1976 ?        S 08:44:18  0:00 /usr/lib/dbus-daemon --fork --print-pid 6 --print-address 8 --session
richard at smicro:~$ logout
Connection to <hostname> closed.
</pre>
up to here, no problem - but now:
<pre>
richard at shuttleX:~$ ssh -X <hostname>
Last login: Mon May  7 10:04:09 2012 from  <client>
OpenIndiana (powered by illumos)    SunOS 5.11    oi_151a3    March 2012
richard at smicro:~$ gedit 
richard at smicro:~$ ps axuw | grep dbus
richard   4850  0.0  0.0 2080 1408 pts/1    S 10:04:59  0:00 grep dbus
root       358  0.0  0.0 3400 2076 ?        S 08:43:55  0:00 /usr/lib/dbus-daemon --system
gdm       3497  0.0  0.0 3508 1420 ?        S 08:44:18  0:00 /usr/bin/dbus-launch --exit-with-session
gdm       3498  0.0  0.0 3156 1976 ?        S 08:44:18  0:00 /usr/lib/dbus-daemon --fork --print-pid 6 --print-address 8 --session
richard   4841  0.0  0.0 3516 1460 pts/1    S 10:04:35  0:00 dbus-launch --autolaunch 29cf1aac9c32865f9da7044b4cf27d81 --binary-syn
richard   4842  0.0  0.0 3068 1888 ?        S 10:04:35  0:00 /usr/lib/dbus-daemon --fork --print-pid 6 --print-address 8 --session
richard at smicro:~$ logout
^CInterrompu par le signal 2.

</pre>

is this a general problem, or is autolaunch omitting  --exit-with-session?
not too knowledgeable on dbus... if the session was VNC, could this be related to the problem?
----------------------------------------
Bug #1987: dbus taking 100% of cpu
https://www.illumos.org/issues/1987

Author: Jeffrey Baitis
Status: New
Priority: Normal
Assignee: OI Userland
Category: 
Target version: oi_151_stable
Difficulty: Medium
Tags: dbus


After my 151a machine had about 39 days of uptime with heavy X11 use, top noticed that dbus-daemon was taking 100% of the cpu time in one of my CPU cores. svcadm disable dbus did not seem to kill the rogue dbus-daemon; I had to kill it by pid manually.

I ran the Proc/dapptrace script from the DTrace toolkit. Here's the output that I got:

<pre>
CALL(args)               = return
-> check_babysit_events(0x2CF8, 0x20, 0x1)              
<- check_babysit_events = 177
-> _dbus_poll(0x8047490, 0x2, 0xFFFFFFFF)               
<- _dbus_poll = 47
-> check_babysit_events(0x2CF8, 0x20, 0x1)              
<- check_babysit_events = 177
-> _dbus_poll(0x8047490, 0x2, 0xFFFFFFFF)               
<- _dbus_poll = 47
-> check_babysit_events(0x2CF8, 0x20, 0x1)              
<- check_babysit_events = 177
-> _dbus_poll(0x8047490, 0x2, 0xFFFFFFFF)               
<- _dbus_poll = 47
-> check_babysit_events(0x2CF8, 0x20, 0x1)              
<- check_babysit_events = 177
-> _dbus_poll(0x8047490, 0x2, 0xFFFFFFFF)               
<- _dbus_poll = 47
-> check_babysit_events(0x2CF8, 0x20, 0x1)              
<- check_babysit_events = 177
-> _dbus_poll(0x8047490, 0x2, 0xFFFFFFFF)               
<- _dbus_poll = 47
</pre>
... ad nauseam



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://www.illumos.org/my/account



More information about the Userland-team mailing list