Devd / devmatch(8) -- netif race 12-RC1

[Dan Partelly]

wireless lagg initialization is broken in this scenario, all-right. The init/rc system as it is now can’t cope easily with a modern asynchronous initialization sequence. Sure you could probably find an order which works, only to find yourself in trouble next time you want  add some modern functionality  . It shows it’s age 

@Warner

Could you tell me please if devmatcher supports taking over a PCI device which is attached by a generic driver already ? vga attaching modern GPUs comes to mind .

Dan


> On Nov 20, 2018, at 15:26, Bjoern A. Zeeb <bzeeb-lists at lists.zabbadoz.net> wrote:
> 
> On 20 Nov 2018, at 8:17, dan_partelly at rdsor.ro wrote:
> 
>>>> No, that's not what's happening. wlan0 isn't racing anything, because it's no longer listed in ifconfig
>> 
>> 
>> But when is created lagg0 ? Acording rc output on screen , creation of cloned interface lagg0 takes place before wlan0 is created. Then this  means SIOCLAGPORT will fail with Invalid argument.  Also lagg0 is started at netif time as far as I know.
>> Firmware for the wireless card is loaded later, and only even later wlan0 is created. So the way I see it, lagg0 cannot have a wlan0 port until firmware for the card is loaded and wlan0 is created, which takes place way after the system attempts to configure lagg0  ? Am I missing something ?
> 
> lagg might be a problem.
> 
> 
> While we are on the topic: I also noticed on a fixed 10G card that the network startup it went through strangely wasn’t the same as it was when the driver was loaded and service netif start was called again.  I have not had time to debug that any further.
> 
> 
>> Also, can you please tell me what happens that devmatch tries to load  uhidd multiple times ?
> 
> That’s probably similar to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232782 ?