On Sun, 12 Dec 2010 06:43:34 +1300 (NZDT) "Fred Zinsli" <fred.zinsli@xxxxxxxxxxxxx> wrote: > I note there is a boot messages alert. Below is a short piece of that > message. > > I don't have a clue what they mean or how to fix it. > > Any comments would be most helpful. > Boot Messages: > > ION match 'add'(plain) > > udevd-work[460]: M ATTRS match 'idVendor' '0638'(plain) > > udevd-work[460]: got 'idVendor' ((null)) from cache > > udevd-work[460]: forward to rule: 13398 > > udevd-work[460]: * RULE /lib/udev/rules.d/65-libsane.rules:1166, > token: 13398, count: 4, label: '', flags: 0x00 > > udevd-work[460]: M ATTRS match 'idVendor' '0638'(plain) > > udevd-work[460]: parent: '/sys/devices/pci0000:00/0000:00:02.1/usb3' > > udevd-work[460]: M ATTRS match 'idVendor' '0638'(plain) > > udevd-work[460]: got 'idVendor' (1d6b) from cache It looks like udev, the system piece that sets up hardware at boot, is spinning its wheels on something called an ION. When you interrupt, it somehow is able to take a path that eventually ends at boot. What happens if you remove that piece of hardware (ION)? Is boot then normal? It would be good to open a bugzilla for the problem as well as it shouldn't do this. udev should either reject or accept, not get into an infinite loop. -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
