Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Nov 2018 08:43:49 +0200
From:      Dan Partelly <dan_partelly@rdsor.ro>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc:        Warner Losh <imp@bsdimp.com>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Devd / devmatch(8) -- netif race 12-RC1
Message-ID:  <798C848D-5F32-4BF9-87E0-ADD4F9B743AD@rdsor.ro>
In-Reply-To: <C019CAB7-20E7-4635-8AF5-8636237DDF48@lists.zabbadoz.net>
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>

next in thread | previous in thread | raw e-mail | index | archive | help
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 =
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=E2=80=99s age=20

@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@lists.zabbadoz.net> wrote:
>=20
> On 20 Nov 2018, at 8:17, dan_partelly@rdsor.ro wrote:
>=20
>>>> No, that's not what's happening. wlan0 isn't racing anything, =
because it's no longer listed in ifconfig
>>=20
>>=20
>> 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 ?
>=20
> lagg might be a problem.
>=20
>=20
> 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 =
was when the driver was loaded and service netif start was called again. =
 I have not had time to debug that any further.
>=20
>=20
>> Also, can you please tell me what happens that devmatch tries to load =
 uhidd multiple times ?
>=20
> 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?798C848D-5F32-4BF9-87E0-ADD4F9B743AD>