hardy : dbus use 100% cpu in waiting

Bug #183031 reported by Charles Perreault on 2008-01-15
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)

Bug Description

I have a laptop running hardy, with kernel 2.6.24-3-generic. After booting, cpu is reported by both gnome-system-monitor and top as 100% used, in the "waiting for i/o" state. Killing dbus / hald with "/etc/init.d/dbus stop" solves the issue, as killing the dbus-daemon. Maybe this isn't dbus' fault as the bug may be caused by a program using dbus, but I don't have the knowledge as how to debug this. Also, vmstat does not report high disk I/O.

Shane Blackett (shane-blackett) wrote :

I have a Compaq nc8430 which has the same problem with 2.6.24-16-generic, although it doesn't seem to start straight away but in the first few minutes making the machine very sluggish.
Killing dbus is an extreme response which also makes the machine unusable but I have found that signalling kjournald doesn't stop the kjournald process but seems to interrupt the problem....

Unfortunately there's not enough information here to debug why that might be the case, and I'm concious that this bug is 18 months old.

If you're still having problems, please open a new bug and we'll debug there

Changed in dbus (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers