On Fri, 29 Aug 2025 at 02:41, Bjoern A. Zeeb <bzeeb-li...@lists.zabbadoz.net> wrote:
> I still have a > > ath0@pci0:1:0:0: class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c > device=0x0034 subvendor=0x11ad subdevice=0x6621 > vendor = 'Qualcomm Atheros' > device = 'AR9462 Wireless Network Adapter' > class = network > > in a machine I use for other ath-unrelated testing. > Tha ath is configured as hostap currently but unused. > > Out of the blue the following has started scrolling by on the console > > ... > ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, > arg_tid=0 > ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, > arg_tid=0 > ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, > arg_tid=0 > ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, > arg_tid=0 > ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, > arg_tid=0 > Yup, I see them too. I _think_ they're NULL QoS data frames going to the wrong TID/queue. I'll sort it out soon! (I'm sorting out NULL QoS data frames in general as part of the seqno diff stack you've reviewed.) -adrian > ... > > > /bz > > -- > Bjoern A. Zeeb r15:7 > >
