public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alberto Gonzalez <alberto6674@gmail.com>
To: linux-hotplug-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Kernel 2.6.30 and udevd problem
Date: Sun, 28 Jun 2009 07:53:44 +0200	[thread overview]
Message-ID: <200906280753.44805.info@gnebu.es> (raw)

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 
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 
'/devices/pci0000:00/0000:00:02.0/drm/card0'
[22657] udev_device_read_db: device 0x2040320 filled with db symlink data 
'/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-udev-
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 
'/devices/pci0000:00/0000:00:02.0'
[22657] udev_device_new_from_syspath: device 0x2040a80 has devpath 
'/devices/pci0000:00'
[22657] udev_rules_apply_to_event: RUN 
'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=226:0, 
mode=0660, uid=0, gid=91
[22657] udev_node_mknod: preserve file '/dev/dri/card0', because it has correct 
dev_t
[22657] update_link: '/dev/char/226:0' with target '/dev/dri/card0' has the 
highest priority 0, create it
[22657] node_symlink: preserve already existing symlink '/dev/char/226:0' to 
'../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 seconds 
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 help 
is appreciated.

My system is a Dell Studio desktop with Intel graphics (G45). I run a standard 
distro kernel (Arch Linux). Please ask me for any other relevant info.

Thanks,
Alberto.

             reply	other threads:[~2009-06-28  5:53 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28  5:53 Alberto Gonzalez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-06-28  6:21 Kernel 2.6.30 and udevd problem Alberto Gonzalez
2009-06-28 10:37 ` Kay Sievers
2009-06-28 12:37   ` Alberto Gonzalez
2009-06-28 12:49     ` Kay Sievers
2009-06-28 14:22       ` Alberto Gonzalez
2009-06-28 14:28         ` Kay Sievers
2009-06-30  3:40           ` Alberto Gonzalez
2009-06-30  3:46             ` Dave Airlie
2009-06-30 16:08               ` Jesse Barnes
2009-07-01  7:09                 ` Alberto Gonzalez
2009-07-01 17:22                   ` Jesse Barnes
2009-07-02  6:18                     ` Alberto Gonzalez
2009-07-02 16:35                       ` Jesse Barnes
2009-07-02 19:37                         ` Alberto Gonzalez
2009-07-02 22:00                           ` Michal Soltys
2009-07-04 22:10                             ` Alberto Gonzalez
2009-07-20 18:10                               ` Jesse Barnes
2009-07-20 21:06                                 ` Alberto Gonzalez
2009-07-20 22:48                                   ` Alberto Gonzalez
2009-07-22 13:25                                     ` Alberto Gonzalez
2009-07-22 16:08                                       ` Jesse Barnes
2009-07-22 16:51                                         ` Alberto Gonzalez
2009-07-22 17:12                                           ` Jesse Barnes
2009-07-22 18:43                                             ` Alberto Gonzalez
2009-07-22 19:17                                               ` Jesse Barnes
2009-07-22 19:44                                               ` Jesse Barnes
2009-07-22 20:00                                                 ` Alberto Gonzalez
2009-07-23  0:06                                                   ` Alberto Gonzalez
2009-08-06 13:53                                                     ` Alberto Gonzalez
2009-08-06 21:30                                                       ` Jesse Barnes
2009-08-06 22:17                                                         ` Alberto Gonzalez

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200906280753.44805.info@gnebu.es \
    --to=alberto6674@gmail.com \
    --cc=linux-hotplug-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox