Created attachment 271741 [details] emerge --info Following the Baselayout and OpenRC Migration Guide[1] is straightforward but after reboot I am having problems with a one minute delay waiting for uevents being processed. The message is udevadm settle - timeout of 60 seconds reached, the event queue contains /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0/ieee80211/phy0/rfkill0 /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0/ieee80211/phy0/rfkill0 /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0/ieee80211/phy0/rfkill0 [1]<http://www.gentoo.org/doc/en/openrc-migration.xml>
Created attachment 271743 [details] Boot messages
Created attachment 271747 [details] Kernel config
After some testing and evaluation I found it is related to my rfkill script and udev rule: /etc/udev/rfkill.sh ------------------- #!/bin/bash if [ "${RFKILL_STATE}" == 1 ]; then /etc/init.d/net.wlan0 start rc else # state is 0 or 2 /etc/init.d/net.wlan0 stop fi /etc/udev/rules.d/40-rfkill.rules --------------------------------- SUBSYSTEM=="rfkill", ATTR{type}=="wlan", RUN+="/etc/udev/rfkill.sh" Problem is still not solved :-(
(In reply to comment #3) > After some testing and evaluation I found it is related to my rfkill script and > udev rule: > > /etc/udev/rfkill.sh > ------------------- > #!/bin/bash > if [ "${RFKILL_STATE}" == 1 ]; then > /etc/init.d/net.wlan0 start > rc > else # state is 0 or 2 > /etc/init.d/net.wlan0 stop > fi > I suggest you have a look at how /lib/udev/net.sh runs init-scripts. Maybe setting IN_HOTPLUG does improve things for you? I also think your udev rule is a bit generic. At how many different sysfs nodes does it match?
Why do you call "rc" at all?
There has been no activity in over a year on this bug. Please upgrade to at least openrc-0.11.8 and udev-197-r8, then report back to the bug and let us know whether or not you are still having issues.
