https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #38 from Cheng Cui ---
After applying D43879 and D43909 with the latest Feb 15 main kernel, still
seeing the "Invalid TXQ" print from the vm4 I managed to reproduce the story.
root@n2fbsdtmp:~ # uname -a
FreeBSD n2fbsdtmp 15.0-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #39 from Bjoern A. Zeeb ---
(In reply to Cheng Cui from comment #38)
sta is added to FW and in state IEEE80211_STA_NONE sta->lsta->ni is
0xfe00ab574000
IEEE80211_STA_NONE can be from scan-to-auth, assoc-down, run-init.
Gi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #40 from Cheng Cui ---
(In reply to Bjoern A. Zeeb from comment #39)
Thanks. With these extra prints. The dmesg after booting shows:
[1.427073] pci0: driver added
[1.632542] wlan0: bpf attached
[1.632744] iwlwifi0: lkpi_iv_upda
On 2024-02-14 11:53, Bjoern A. Zeeb wrote:
Hi,
can I ask everyone who has a spare cycle to test main on/after
0936c648ad0ee5152dc19f261e77fe9c1833fe05 (commit went in a minute ago).
The last changes include "band-aid" hacks to net80211 which will affect
all drivers and sta/ap mode.
While the c
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274382
--- Comment #41 from Ed Maste ---
dmesg snippit from the Framework laptop which produces one 'Invalid TXQ id' at
boot, with the additional debugging:
iwlwifi0: lkpi_iv_update_bss:2574: lvif 0xfe01424ae000 vap
0xfe01424ae010 iv_bss
14.02.24 21:53, Bjoern A. Zeeb:
Hi,
can I ask everyone who has a spare cycle to test main on/after
0936c648ad0ee5152dc19f261e77fe9c1833fe05 (commit went in a minute ago).
The last changes include "band-aid" hacks to net80211 which will affect
all drivers and sta/ap mode.
While the commit messa
