Created attachment 402130 [details] emerge --info; lspci -v -k; (rc.log; udevmonitor.log) without 'rootdelay'; (rc.log; udevmonitor.log) with 'rootdelay=3' There are two different wireless network adapters in my system. First wlp0s4 uses Ath9k driver and the second wlp0s3 uses Ath10k driver. wlp0s4 successfully initialized during a system boot, but wlp0s3 failed with the errors: * Bringing up interface wlp0s3 * ERROR: interface wlp0s3 does not exist * Ensure that you have loaded the correct kernel module for your hardware * ERROR: net.wlp0s3 failed to start * ERROR: cannot start netmount as net.wlp0s3 would not start But wlp0s3 becomes accessible after the full startup sequence, I can use it from the command line. It seems that startup scripts don't wait for interface renaming or udev renames it too late. There's workaround: one can use kernel option 'rootdelay=X', where X is some delay. One more such issue from another user: http://lists.freedesktop.org/archives/systemd-devel/2014-May/019127.html
Is this being fired manually or via the 90-network.rules? SUBSYSTEM=="net", ACTION=="add", RUN+="net.sh $name start" If it's manually, it should only be happening AFTER udev settle has completed.
Got same bug with latest (5.4.66 and higher) kernel update. Can be resolved with "need udev-settle"...
