From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robby Workman Date: Thu, 03 Dec 2009 06:03:18 +0000 Subject: Re: [ANNOUNCE] udev 148 release Message-Id: <20091203000318.1244d470@liberty.rlwhome.lan> List-Id: References: <1259755885.2099.2.camel@yio.site> In-Reply-To: <1259755885.2099.2.camel@yio.site> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Wed, 02 Dec 2009 13:11:25 +0100 Kay Sievers wrote: > ID_INPUT_{KEYBOARD,KEY,MOUSE,TOUCHPAD,TABLET,JOYSTICK}. These are > determined by the new "input_id" prober now. Some devices, such as > touchpads, can have several classes. So if you previously had custom > udev rules which e. g. checked for ENV{ID_CLASS}="kbd", you need to > replace this with ENV{ID_INPUT_KEYBOARD}="?*". I just upgraded to 148 from 147, and the new input_id does not seem to be liked by either my main system or a vbox vm. In the virtual machine, I noticed this after upgrading and reloading the rules: top output: 20958 root 18 -2 6004 564 476 R 99.6 0.1 0:41.19 input_id ps output: root 20958 99.0 0.0 6004 564 ? R< 23:43 \ 1:04 /lib/udev/input_id /devices/virtual/input/mice After rebooting the machine, it hangs for a long time after the usb hubs are detected by the kernel, and then I get this: udevadm settle - timeout of 120 seconds reached, the event queue contains: /sys/devices/virtual/input/mice (1124) ... some other extraneous messages ... udevd[1145]: worker [1150] unexpectedly returned with status 0x0100 udevd[1145]: worker [1150] failed while handling '/devices/virtual/input/mice' Where do I start with debugging this?? -RW