On Fri, 28 Nov 2025, FreeBSD User wrote:
Running 15-STABLE (15.0-STABLE #16 stable/15-n281349-b903f27e171b: Fri Nov 28
05:20:32
CET 2025 amd64) on a Lenovo T580 laptop. The system is equipted with an Intel
i8265/8275
WiFi chipset (for recognized technical details see below).
[...]
From my perseptive anything seems to be OK:
[...]
end FB_INFO
iwlwifi0: <iwlwifi> mem 0xe8100000-0xe8101fff at device 0.0 on pci2
iwlwifi0: Detected crf-id 0xbadcafe, cnv-id 0x10 wfpm id 0x80000000
iwlwifi0: PCI dev 24fd/0010, rev=0x230, rfid=0xd55555d5
iwlwifi0: Detected Intel(R) Dual Band Wireless-AC 8265
iwlwifi0: successfully loaded firmware image 'iwlwifi-8265-36.ucode'
iwlwifi0: loaded firmware version 36.ca7b901d.0 8265-36.ucode op_mode iwlmvm
iwlwifi0: base HW address: MACxxxxxMAC , OTP minor version: 0x0
hms0: <Logitech Wireless Receiver Mouse> on hidbus0
hms0: 5 buttons and [XYW] coordinates ID=1
[...]
I'm unable to connect to any access point. I use at home a OpenWRT based AP
with latest
firmware, connecting with the Linux- and Windows hosts of my employer (so:
functionality
at a basic level guaranteed). FreeBSD - 14-STABLE (last time I used until
branch of
16-CURRENT) and 15-STABLE do not. A similar misbehaviour is observed when
trying to
access APs at several campi via "eduroam" - the hardware behind those APs is
probably
Cisco technology, I do not know.
The log and console are filled with "dramatic" messages like
iwlwifi0: lkpi_sta_scan_to_auth:2419: lvif 0xfffffe00c3307000 vap
0xfffffe00c3307010 iv_bss 0xfffffe00b4135000 lvif_bss 0 lvif_bss->ni 0 synched
0, ni 0xfffffe00c2bf4000 lsta 0xfffff8002e01e800
iwlwifi0: lkpi_iv_newstate: error 95 during state transition 2 (AUTH) -> 2
(AUTH)
This is net80211 chaning the iv_bss under us.
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
wlan0: link state changed to UP
wlan0: link state changed to DOWN
This indicates that you get associated. Hard to say without timestamps but ...
iwlwifi0: Not associated and the time event is over already...
iwlwifi0: linuxkpi_ieee80211_connection_loss: vif 0xfffffe00c3307f00 vap
0xfffffe00c3307010 state ASSOC (synched 1, assoc 0 beacons 0 dtim_period 0)
But then things are timing out.
That is a problem Oleg has reported on rtw88, I had last night with an AX101
but after a reboot was gone again, ...
iwlwifi0: fail to flush all tx fifo queues Q 5
iwlwifi0: Queue 5 is active on fifo 3 and stuck for 10000 ms. SW [2, 3] HW [2,
3] FH TRB=0x080305002
This is the 2nd report I lately got with queue stuck.
wlan0: link state changed to UP
wlan0: link state changed to DOWN
iwlwifi0: Not associated and the time event is over already...
iwlwifi0: linuxkpi_ieee80211_connection_loss: vif 0xfffffe00c3307f00 vap
0xfffffe00c3307010 state ASSOC (synched 1, assoc 0 beacons 0 dtim_period 0)
iwlwifi0: fail to flush all tx fifo queues Q 5
iwlwifi0: Queue 5 is active on fifo 3 and stuck for 10000 ms. SW [2, 3] HW [2,
3] FH TRB=0x080305002
wlan0: link state changed to UP
wlan0: link state changed to DOWN
[...]
I'm helpless here ...
What would be interesting to me:
What does wpa_supplicant say? What are the errors?
I am thinking of messages like:
Nov 27 18:37:59 x wpa_supplicant[5946]: wlan0: Authentication with
xx:xx:xx:xx:xx: timed out.
Nov 27 19:30:02 x wpa_supplicant[5689]: wlan0: CTRL-EVENT-DISCONNECTED
bssid=xx:xx:xx:xx:xx:xx reason=3 locally_generated=1
[... pciconf ...]
# pciconf -lvceb iwlwifi0@pci0:4:0:0
iwlwifi0@pci0:4:0:0: class=0x028000 rev=0x78 hdr=0x00 vendor=0x8086
device=0x24fd subvendor=0x8086 subdevice=0x0010
vendor = 'Intel Corporation'
device = 'Wireless 8265 / 8275'
--
Bjoern A. Zeeb r15:7
