On Tue, 20 May 2025, Kevin Oberman wrote:
Hi Kevin,
yes, that issue is still a major blocker here for me too. My problem
between the handful-ish of people is that I cannot yet say what the
issue is for all of you.
May 20 20:37:01 ptavv kernel: iwlwifi0: lkpi_sta_scan_to_auth:2270: lvif
0xfffffe0156a60000 vap 0xfffffe0156a60010 iv_bss 0xfffffe0156d9e000 lvif_bss 0
lvif_b$
This seems to be cut off or the kernel log spew it elsewhere.
May 20 20:37:01 ptavv kernel: iwlwifi0: lkpi_sta_a_to_a:2561: lvif
0xfffffe0156a60000 vap 0xfffffe0156a60010 iv_bss 0xfffffe0156d9e000 lvif_bss
0xfffff8004245$
May 20 20:37:01 ptavv kernel: iwlwifi0: lkpi_iv_newstate: error 95 during state
transition 2 (AUTH) -> 2 (AUTH)
But this is usually triggered by net80211/wpa_supplicant hanging mind to
which BSSID to assoc to and ripping the old one away from under our feet.
May 20 20:37:01 ptavv kernel: Invalid TXQ id
This one is weird as it would have an accompanying "see PR" messe from
iwlwifi. In addition I thought I recently fixed this for good. what
version (or branch/githash) are you running?
May 20 20:37:01 ptavv kernel: iwl_mvm_tx_mpdu:1280: fc 0x00b0 tid 8 txq_id
65535 mvm 0xfffffe0156585548 skb 0xfffffe0156da8a60 { len 30 } info
0xfffffe00f12e7$
May 20 20:37:01 ptavv kernel: ieee80211_sta_join: BSS 4c:ed:fb:37:b0:20: 2GHz
channel, VHT info; ignoring
Ok, that Ap is likely a Broadcom(?) [or QCA?] doing VHT on 2Ghz as well;
not standard and not supported in FreeBSD. ASUS AP? This can be
ignored.
May 20 20:37:01 ptavv kernel: wlan0: link state changed to UP
You did assoc to something in the end (same second). I assume that was
a 2.4Ghz channel then?
/bz
--
Bjoern A. Zeeb r15:7
