Date: Thu, 5 Mar 2026 15:58:51 +0100 From: ltning-freebsd-wireless@anduin.net To: wireless@freebsd.org Subject: Re: LinuxKPI (iwlwifi, rtw8x) Please test! Important! (in stable/15 in three days) Message-ID: <d3b25b55-c2a8-4825-a77b-0a465011051f@anduin.net> In-Reply-To: <rrn857-6598-4p6n-s63r-r824q675763p@mnoonqbm.arg> References: <r158r59-93o7-9767-1r57-805sq1s07q4p@mnoonqbm.arg> <p836qqn7-6pq4-nrq-p346-8qp5ors7p170@mnoonqbm.arg> <65165b44-b8c2-4762-b7fa-c21a70248848@benhutton.com.au> <rrn857-6598-4p6n-s63r-r824q675763p@mnoonqbm.arg>
index | next in thread | previous in thread | raw e-mail
On 3/5/26 14:58, Bjoern A. Zeeb wrote:
> Thanks to the three of you who have tested the last round and reported
> back.
> That was very much appreciated and helpful!
Count me in, though a bit late! I immediately pulled and built the
sources when I saw your first message on the thread, and while things
seem to work mostly like before, I have had two very-rarely-seen crashes
in relatively short order:
- one complete wedge when doing 'service netif restart wlan0'
(obviously no debug info available)
- one failure to wake from sleep (black screen, hard poweroff required)
I'm not saying I've never seen this before, but it's been ... months? So
I can't help but shake the feeling it's at least plausibly related to
the changes.
On my actual problem with iwlwifi - the firmware still needs to crash at
least once after resuming from sleep before I can successfully connect
to a network. It will (upon 'service netif restart') associate, but
never get an IP, then the firmware crashes, and then it works.
Since I've provided logs for this before I will not right now, however I
am rebuilding again now with your most recent changes, and will collect
logs if it happens again (and you think it is useful).
> Everyone else can now also go and have a try again!
On it!
> 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).
Testing as soon as it is done building, on
iwlwifi0@pci0:170:0:0: class=0x028000 rev=0x1a hdr=0x00 vendor=0x8086
device=0x2725 subvendor=0x8086 subdevice=0x0020
vendor = 'Intel Corporation'
device = 'Wi-Fi 6E(802.11ax) AX210/AX1675* 2x2 [Typhoon Peak]'
> 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.
I will torture it properly. Swear!
Thanks,
/Eirik
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d3b25b55-c2a8-4825-a77b-0a465011051f>