high cpu usage after update.

snookerzysta · #1 2009-10-15, 04:26 AM CDT

Hello,
yesterday I updated over 30 packages, and today I have over 50% cpu usage all the time.
I'm not sure if it's connected with yesterday update, but I didn't have that cpu usage before.

logs:

yum : http://pastebin.com/m70220f22

top : http://pastebin.com/m58a8871e

any1 can help?

parish · #2 2009-10-15, 09:05 AM CDT

Any particular process using most/all of the cpu cycles?

Daniel

snookerzysta · #3 2009-10-16, 04:09 AM CDT

these 3 processes use over 30% together:
dbus-daemon
devkit-disks-da
gvfs-gdu-volume

I thought that dbus-daemon caused it so I ran dbus-monitor --system, and I got this message spamming all the time:

Quote:

signal sender=:1.57 -> dest=(null destination) serial=38740 path=/org/freedesktop/DeviceKit/Disks/devices/sr0; interface=org.freedesktop.DeviceKit.Disks.Device; member=Changed
signal sender=:1.57 -> dest=(null destination) serial=38741 path=/org/freedesktop/DeviceKit/Disks; interface=org.freedesktop.DeviceKit.Disks; member=DeviceChanged
object path "/org/freedesktop/DeviceKit/Disks/devices/sr0"

when I eject cd/dvd tray, cpu usage decreases almost to 0, but for less than second only...

snookerzysta · #4 2009-10-16, 10:22 AM CDT

I found out that that process udevd was responsible for that, after killing it everything went to normal.
But I need it :P

With udev daemon running, when I run 'udevmonitor' I get spammed with such messages:

"KERNEL[1255710047.933265] change /devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sr0 (block)
UDEV [1255710047.933328] change /devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0 (scsi)
KERNEL[1255710047.973338] change /devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0 (scsi)
UDEV [1255710047.997501] change /devices/pci0000:00/0000:00:1f.2/host1/target1:0:0/1:0:0:0/block/sr0 (block)
"

any1 can help?

//edit :

after downgrading udev to 141.3, it went back to normal. I still get these messages but less frequently.

pinhighwedge · #5 2009-10-30, 03:29 AM CDT

I have the same issue after upgrading to udev-141-7.fc11

I added a bug report to the Fedora bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=532011

After downgrading to udev-141-3.fc11 everything went back to normal.