Date: Tue, 20 Nov 2018 13:26:38 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: dan_partelly@rdsor.ro Cc: "Warner Losh" <imp@bsdimp.com>, "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: Devd / devmatch(8) -- netif race 12-RC1 Message-ID: <C019CAB7-20E7-4635-8AF5-8636237DDF48@lists.zabbadoz.net> In-Reply-To: <873d8841484925a35cf8c751790659c1@rdsor.ro> References: <A4074445-D442-4244-8E73-7F34DAA5E3FD@rdsor.ro> <CANCZdfqWq%2B2Lc1UrTdb8Fc9XkyL8cpaqAmS-Sh-vev_ZOQesDQ@mail.gmail.com> <873d8841484925a35cf8c751790659c1@rdsor.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20 Nov 2018, at 8:17, dan_partelly@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 ?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C019CAB7-20E7-4635-8AF5-8636237DDF48>