On Thu, 2019-02-28 at 10:37 +0200, Kalle Valo wrote: > > > Is this long delay after module and firmware load some expected effect > > that I need to code around or what? > > Usually these 60 second (or it's multiply) delays are caused by kernel > requesting a firmware image from user space but the corresponding user > space component is not replying and kernel waits for the reply until it > timeouts and continues. IIRC there's a kernel config option you can use > to disable this feature, or you could also try to fix the user space. Regardless though, fixing this will just make the race condition less likely, not fix it. Most wifi NICs these days will load firmware because they need to run it, and they will typically have to load the firmware *before* they register their wiphy/netdev. Due to technical considerations (built-in drivers etc.) the firmware load pretty much has to happen asynchronously. As a result, modprobe will return before the netdev exists. Now, in your case you likely have some sort of firmware problem like Kalle says, which causes it to take an excessive amount of time, perhaps by calling out to a userspace helper that doesn't work and thus doesn't answer negatively? However, the fact remains that you shouldn't assume that modprobe returning means anything - the netdev will exists when that happens, and you should trigger your networking startup on the event that says it exists now. johannes
