Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 547942 - net-misc/netifrc does not wait for udev to initialize network devices
Summary: net-misc/netifrc does not wait for udev to initialize network devices
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: netifrc (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: netifrc Team
Whiteboard: netifrc:udev
Depends on:
Reported: 2015-04-28 01:03 UTC by arabesc
Modified: 2022-12-03 21:25 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

emerge --info; lspci -v -k; (rc.log; udevmonitor.log) without 'rootdelay'; (rc.log; udevmonitor.log) with 'rootdelay=3' (logs.txt,92.53 KB, text/plain)
2015-04-28 01:03 UTC, arabesc

Note You need to log in before you can comment on or make changes to this bug.
Description arabesc 2015-04-28 01:03:37 UTC
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:
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2016-10-24 22:37:04 UTC
Is this being fired manually or via the 90-network.rules?
SUBSYSTEM=="net", ACTION=="add",    RUN+=" $name start"

If it's manually, it should only be happening AFTER udev settle has completed.
Comment 2 BigBug 2020-10-21 11:25:57 UTC
Got same bug with latest (5.4.66 and higher) kernel update.

Can be resolved with "need udev-settle"...