From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alberto Gonzalez Date: Sun, 28 Jun 2009 06:21:58 +0000 Subject: Kernel 2.6.30 and udevd problem Message-Id: <200906280821.58631.info@gnebu.es> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: linux-kernel@vger.kernel.org Cc: linux-hotplug@vger.kernel.org, Alberto Gonzalez [Sorry, wrong udev list in previous message.] Hello, I have recently upgraded my kernel to 2.6.30 and I've noticed that at some = point (randomly), udevd would start using a lot of CPU time. Killing the=20 process and starting it with --debug option prints these messages when the = problem starts: [22652] event_queue_insert: seq 168515 queued, 'change' 'drm' [22657] udev_device_new_from_syspath: device 0x2040320 has devpath=20 '/devices/pci0000:00/0000:00:02.0/drm/card0' [22657] udev_device_read_db: device 0x2040320 filled with db symlink data=20 '/dev/dri/card0' [22657] udev_rules_apply_to_event: LINK 'char/226:0' /lib/udev/rules.d/50- udev-default.rules:5 [22657] udev_rules_apply_to_event: NAME 'dri/card0' /lib/udev/rules.d/50-ud= ev- default.rules:38 [22657] udev_rules_apply_to_event: GROUP 91 /lib/udev/rules.d/50-udev- default.rules:42 [22657] udev_device_new_from_syspath: device 0x2040790 has devpath=20 '/devices/pci0000:00/0000:00:02.0' [22657] udev_device_new_from_syspath: device 0x2040a80 has devpath=20 '/devices/pci0000:00' [22657] udev_rules_apply_to_event: RUN=20 'socket:@/org/freedesktop/hal/udev_event' /etc/udev/rules.d/90-hal.rules:2 [22657] udev_device_update_db: create db link (dri/card0 char/226:0) [22657] udev_node_add: creating device node '/dev/dri/card0', devnum"6:0,=20 mode=0660, uid=3D0, gid=91 [22657] udev_node_mknod: preserve file '/dev/dri/card0', because it has cor= rect=20 dev_t [22657] update_link: '/dev/char/226:0' with target '/dev/dri/card0' has the= =20 highest priority 0, create it [22657] node_symlink: preserve already existing symlink '/dev/char/226:0' t= o=20 '../dri/card0' [22657] udev_monitor_send_device: passed 230 bytes to monitor 0x2040320 [22657] udev_monitor_send_device: passed -1 bytes to monitor 0x2036150 [22657] event_fork: seq 168515 exit with 0 [22652] event_fork: seq 168515 forked, pid [22657], 'change' 'drm', 0 secon= ds=20 old [22652] udev_done: seq 168515 cleanup, pid [22657], status 0, 0 seconds old This sequence repeats ad infinitum. I have no clue what it means, so any he= lp=20 is appreciated. My system is a Dell Studio desktop with Intel graphics (G45). I run a stand= ard=20 distro kernel (Arch Linux). Please ask me for any other relevant info. Thanks, Alberto.