Bugzilla – Bug 605177
udevd: can not read '/etc/udev/rules.d/79-yast2-drivers.rules'
Last modified: 2010-05-12 14:01:22 UTC
with 11.3-factory with xen dom0 kernel I getplenty of these messages below. /etc/udev/rules.d/79-yast2-drivers.rules does exist but it's empty: # ll /etc/udev/rules.d/79-yast2-drivers.rules -rw-r--r-- 1 root root 0 Apr 13 16:13 /etc/udev/rules.d/79-yast2-drivers.rules why does udevd complain about an existing (but empty) file ? os4:/etc/xen # uname -a Linux os4 2.6.34-rc6-7-xen #1 SMP 2010-05-04 23:21:35 +0200 x86_64 x86_64 x86_64 GNU/Linux os4:/etc/xen # rpm -qf /sbin/udevd udev-153-1.2.x86_64 one reason that there are so many of these messages (~10/sec after boot) is related to some USB problems with the usb keyboard from the IPMI interface on this main board: May 12 14:55:23 os4 kernel: klogd 1.4.1, log source = /proc/kmsg started. May 12 14:55:23 os4 kernel: [ 10.576518] usb 1-7: new high speed USB device using ehci_hcd and address 40 May 12 14:55:23 os4 kernel: [ 10.648293] hub 1-0:1.0: unable to enumerate USB device on port 7 May 12 14:55:23 os4 kernel: [ 10.896029] usb 1-7: new high speed USB device using ehci_hcd and address 41 May 12 14:55:23 os4 kernel: [ 10.964286] hub 1-0:1.0: unable to enumerate USB device on port 7 May 12 14:55:23 os4 kernel: [ 11.208022] usb 1-7: new high speed USB device using ehci_hcd and address 42 May 12 14:55:23 os4 kernel: [ 11.280305] hub 1-0:1.0: unable to enumerate USB device on port 7 after resetting the IMPI board those usb messages stopped (and the ipmi console keyboard support starts working), but even now without any usb problems I get some few to tens of those udev messages er minute: May 12 15:07:59 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:07:59 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:07:59 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:07:59 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:07:59 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:00 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' May 12 15:08:01 os4 udevd[481]: can not read '/etc/udev/rules.d/79-yast2-drivers.rules' grep /etc/udev/rules.d/79-yast2-drivers.rules /var/log/messages| cut -d: -f-2| uniq -c | less 75 May 12 14:55 276 May 12 14:56 176 May 12 14:57 28 May 12 14:59 443 May 12 15:00 636 May 12 15:01 614 May 12 15:02 662 May 12 15:03 771 May 12 15:04 658 May 12 15:05 674 May 12 15:06 699 May 12 15:07 612 May 12 15:08 559 May 12 15:09 459 May 12 15:10 391 May 12 15:11 25 May 12 15:12 4 May 12 15:13 13 May 12 15:14 4 May 12 15:15 3 May 12 15:19 2 May 12 15:20 1 May 12 15:25 4 May 12 15:30 1 May 12 15:35 2 May 12 15:36 10 May 12 15:37 12 May 12 15:38 57 May 12 15:40 35 May 12 15:41 8 May 12 15:45 6 May 12 15:46 14 May 12 15:47 21 May 12 15:48 2 May 12 15:49 56 May 12 15:50 12 May 12 15:51 3 May 12 15:52 2 May 12 15:54 1 May 12 15:55
This problem was reported previously in bug #601723 and is already fixed. The fix should reach Factory soon. Anyway, thanks for taking the time to report! *** This bug has been marked as a duplicate of bug 601723 ***