Udev events failed
Noticed this on boot up the other day, but it doesn't seem to have a negative effect. Everything appears to be running just fine.
"Triggering udev events: /sbin/udevadm trigger --type=failed" Is this something that needs to be resolved or ignored? Thanks. :hattip: |
Did you even bother reading the udevadm man page?
|
Quote:
Thank you for your most helpful response... not. :rolleyes: |
I noticed this way back to 12.1 I bet if I followed it back on or more of the scripts that UDEV is supposed to load. And one of those was my pcmcia I turned it off on my desktop. check pkgtool run scripts it is just trying to load hardware that is not there no big deal leave it alone or play with it.
any way you look at it the program Failed to load that device. |
AFAIK the same message has appeared at boot since installation. At first it was alarming to see "failed" in a boot message but I figured it is a command parameter rather than a condition so never worried about it since.
|
IIRC, this is there to trigger any udev events that failed first time around in the boot process at /etc/rc.d/rc.S. The message is for info puposes.
|
That shows the second time that udev is run and is meant to find devices which were already plugged in at boot-time -it's called coldplugging as opposed to hotplugging which detects events as they happen.
Devices which are already plugged in when booting generate a kernel-event before udev is started and so udev is run a second time with '--type=failed' to detect any such events. udev is first started at the top of rc.S, but the line you are seeing is from late during rc.M. |
Thank you Drakeo, Catkin, Vdemuth, and, especially, Gnashley for your replies. Greatly appreciated!
:hattip: |
All times are GMT -5. The time now is 06:05 PM. |