Re: LinuxKPI (iwlwifi, rtw8x) Please test! Important! (in stable/15 in three days)

From: Kevin Oberman <rkoberman_at_gmail.com>
Date: Fri, 06 Mar 2026 18:25:40 UTC
On Thu, Mar 5, 2026 at 5:59 AM Bjoern A. Zeeb <bz@freebsd.org> wrote:

> Hi everyone!
>
> I'll keep this thread alive.
>
> Thanks to the three of you who have tested the last round and reported
> back.
> That was very much appreciated and helpful!
>
> Everyone else can now also go and have a try again!
>
> In the last 48 hours I pushed the next round of LinuxKPI 802.11
> changes which would be good to validate on a wide set of chipsets
> and supported drivers.  One of them fixed a firmware crash, another
> one re-enabled some code again which was silently not doing its things
> due to Linux KPI changes (and surprisingly most of it worked anyway the
> last months).
>
> This time you'll likely not need long testing time.  Maybe a change of
> association or if you want a netif restart will be good tests.
>
> If the last round of changes are good, I am currently cleaning up some
> loose iwlwifi ends and will push the driver update and we'll all be on
> v6.19.
>
> After that more LinuxKPI 802.11 bits for Realtek etc. will slowly start
> showing up.
>
>
> I can only emphasize that all your testing will help us with what will be
> shipping in 15.1-R.  The earlier we catch possible problems the more likely
> your wifi will work in the release!
>
> Lots of health and joy,
> /bz
>
> --
> Bjoern A. Zeeb                                                     r15:7
>
> Tested the latest and it is working fine. I restarted netif with no issues.

I will also note that after the prior code having been running for about
7.4 days I noted an unusually large number of output errors; about 15,000
over this time. But I also had moved over 20G packets out of my system,
mostly ACKs and related small packets as the data was being downloaded. It
will take a while to see if this continues.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683