Re: weird udev behaviour
Here is some more data.
I attached the output of
"udevtest /class/input/mice"
from a box that shows this error, and from a box that does not.
(The configurations are completely different, but the package
versions and the relevant udev rules are the same.)
The relevant difference seems to be this:
Good run:
-------------------
udev_rules_get_name: rule applied, 'mice' becomes 'input/mice'
udev_node_add: creating device node '/dev/input/mice', major=13,
minor=63, mode=0660, uid=0, gid=0
--------------
Bad run:
------------------------
udev_rules_get_name: no node name set, will use kernel name ''
udev_node_add: creating device node '/dev/mice', major=13, minor=63, mode=0
---------------------------------------------------------------------------
It says that the kernel name is ''. It's strange. What is it not 'mice'?
And if it's '', then why is the node called /dev/mice?
udevinfo --export-db | grep mice gives this:
P: /class/input/mice
N: mice
It seems to me that this might be a problem in udev,
or in the communication between the kernel and udev.
Which is strange, since neither udev, nor the kernel was
updated lately. (libc6 was, but it should not introduce such
grave errors...)
Any ideas? How can I debug this further?
Kristof Csillag
Csillag Kristof wrote:
> Dear all,
>
>
> On some of my machines, udev started to act strangely lately.
>
>
> It created all the device files in the root of the /dev directory,
>
> instead of the normal places.
>
>
> (Instead of /dev/input/mice, I get /dev/mice; instead of /dev/snd/* I
> get /dev/*, etc.)
>
>
> Of course, this breaks a lot of things.
>
>
> I have no idea what caused this.
>
> I am running an etch/sid hybrid.
>
>
> I did not update udev lately.
>
>
> Unfortunately, I do not use apt-listchanges on this box, so I can not
> tell exactly
>
> which packages were upgradet lately, but I am sure the change happened
>
> in the last few (say, 3) days.
>
>
> I have never seen this problem before.
>
> Could you please give me some ideas what can be wrong?
>
>
> Thank you for your help:
>
>
> Kristof Csillag
>
>
>
>
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
parse_file: reading '/etc/udev/rules.d/020_permissions.rules' as rules file
parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file
parse_file: reading '/etc/udev/rules.d/025_libsane-extras.rules' as rules file
parse_file: reading '/etc/udev/rules.d/035_kino.rules' as rules file
parse_file: reading '/etc/udev/rules.d/11-hplj10xx.rules' as rules file
parse_file: reading '/etc/udev/rules.d/88-ltsp.rules' as rules file
parse_file: reading '/etc/udev/rules.d/libmtp7.rules' as rules file
parse_file: reading '/etc/udev/rules.d/udev.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z20_persistent-input.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z45_persistent-net-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z50_run.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z55_hotplug.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_hdparm.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_libsane.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_ltspfsd.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z75_cd-aliases-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z99_hal.rules' as rules file
main: looking at device '/class/input/mice' from subsystem 'input'
udev_rules_get_name: no node name set, will use kernel name ''
udev_db_get_device: found a symlink as db file
udev_device_event: device '/class/input/mice' already in database, cleanup
udev_node_add: creating device node '/dev/mice', major=13, minor=63, mode=0660, uid=0, gid=0
main: run: 'socket:/org/freedesktop/hal/udev_event'
This program is for debugging only, it does not run any program,
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
parse_file: reading '/etc/udev/rules.d/020_permissions.rules' as rules file
parse_file: reading '/etc/udev/rules.d/025_libgphoto2.rules' as rules file
parse_file: reading '/etc/udev/rules.d/025_logitechmouse.rules' as rules file
parse_file: reading '/etc/udev/rules.d/11-hplj10xx.rules' as rules file
parse_file: reading '/etc/udev/rules.d/libmtp7.rules' as rules file
parse_file: reading '/etc/udev/rules.d/udev.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z20_persistent-input.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z20_persistent.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z25_persistent-net.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z45_persistent-net-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z50_run.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z55_hotplug.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_alsa-utils.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z75_cd-aliases-generator.rules' as rules file
parse_file: reading '/etc/udev/rules.d/z99_hal.rules' as rules file
main: looking at device '/class/input/mice' from subsystem 'input'
udev_rules_get_name: rule applied, 'mice' becomes 'input/mice'
match_rule: set ENV 'ID_SERIAL=noserial'
run_program: 'path_id /class/input/mice'
run_program: '/lib/udev/path_id' (stdout) 'ID_PATH='
run_program: '/lib/udev/path_id' returned with status 1
udev_db_get_device: no db file to read /dev/.udev/db/\x2fclass\x2finput\x2fmice: No such file or directory
udev_node_add: creating device node '/dev/input/mice', major=13, minor=63, mode=0660, uid=0, gid=0
main: run: 'socket:/org/kernel/udev/monitor'
main: run: 'socket:/org/freedesktop/hal/udev_event'
Reply to: