Date: Thu, 22 Nov 2018 10:06:49 -0700 From: Warner Losh <imp@bsdimp.com> To: dan_partelly <dan_partelly@rdsor.ro> Cc: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Devd / devmatch(8) -- netif race 12-RC1 Message-ID: <CANCZdfqDUyn2cGLT2kgqhVBL0uQbFV8CbrDK7TpZknxjhQeWuw@mail.gmail.com> In-Reply-To: <798C848D-5F32-4BF9-87E0-ADD4F9B743AD@rdsor.ro> References: <A4074445-D442-4244-8E73-7F34DAA5E3FD@rdsor.ro> <CANCZdfqWq%2B2Lc1UrTdb8Fc9XkyL8cpaqAmS-Sh-vev_ZOQesDQ@mail.gmail.com> <873d8841484925a35cf8c751790659c1@rdsor.ro> <C019CAB7-20E7-4635-8AF5-8636237DDF48@lists.zabbadoz.net> <798C848D-5F32-4BF9-87E0-ADD4F9B743AD@rdsor.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 21, 2018, 11:43 PM Dan Partelly <dan_partelly@rdsor.ro wrote: > wireless lagg initialization is broken in this scenario, all-right. The > init/rc system as it is now can=E2=80=99t cope easily with a modern async= hronous > initialization sequence. Sure you could probably find an order which work= s, > only to find yourself in trouble next time you want add some modern > functionality . It shows it=E2=80=99s 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 . > No. Newbus doesn't currently support reprobing, though some preliminary support. I have it on my list. Warner Dan > > > > On Nov 20, 2018, at 15:26, Bjoern A. Zeeb < > bzeeb-lists@lists.zabbadoz.net> wrote: > > > > On 20 Nov 2018, at 8:17, dan_partelly@rdsor.ro wrote: > > > >>>> No, that's not what's happening. wlan0 isn't racing anything, becaus= e > 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 unt= il > firmware for the card is loaded and wlan0 is created, which takes place w= ay > 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=E2=80=99t the same as it w= as when > the driver was loaded and service netif start was called again. I have n= ot > had time to debug that any further. > > > > > >> Also, can you please tell me what happens that devmatch tries to load > uhidd multiple times ? > > > > That=E2=80=99s probably similar to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232782 ? > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqDUyn2cGLT2kgqhVBL0uQbFV8CbrDK7TpZknxjhQeWuw>