Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 29 Aug 2025 08:10:05 -0700
From:      Adrian Chadd <adrian.chadd@gmail.com>
To:        "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc:        FreeBSD wireless mailing list <wireless@freebsd.org>
Subject:   Re: ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0
Message-ID:  <CAJ-Vmo=vr8ujM4F2j47ouwSZxmEoVEJTVpPJ4J7izx7sKzdM7Q@mail.gmail.com>
In-Reply-To: <8478n161-p6nq-5on3-s587-sn3425758854@yvfgf.mnoonqbm.arg>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]
On Fri, 29 Aug 2025 at 02:41, Bjoern A. Zeeb <bzeeb-lists@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
>
>

[-- Attachment #2 --]
<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, 29 Aug 2025 at 02:41, Bjoern A. Zeeb &lt;<a href="mailto:bzeeb-lists@lists.zabbadoz.net">bzeeb-lists@lists.zabbadoz.net</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I still have a<br>
<br>
ath0@pci0:1:0:0:        class=0x028000 rev=0x01 hdr=0x00 vendor=0x168c device=0x0034 subvendor=0x11ad subdevice=0x6621<br>
     vendor     = &#39;Qualcomm Atheros&#39;<br>
     device     = &#39;AR9462 Wireless Network Adapter&#39;<br>
     class      = network<br>
<br>
in a machine I use for other ath-unrelated testing.<br>
Tha ath is configured as hostap currently but unused.<br>
<br>
Out of the blue the following has started scrolling by on the console<br>
<br>
...<br>
ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0<br>
ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0<br>
ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0<br>
ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0<br>
ath0: ieee80211_output_seqno_assign: called; TID mismatch; tid=14, arg_tid=0<br></blockquote><div><br></div><div>Yup, I see them too. I _think_ they&#39;re NULL QoS data frames going to the wrong TID/queue.</div><div><br></div><div>I&#39;ll sort it out soon! (I&#39;m sorting out NULL QoS data frames in general as part of the seqno diff stack you&#39;ve reviewed.)</div><div><br></div><div><br></div><div><br></div><div>-adrian</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
...<br>
<br>
<br>
/bz<br>
<br>
-- <br>
Bjoern A. Zeeb                                                     r15:7<br>
<br>
</blockquote></div></div>
home | help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=vr8ujM4F2j47ouwSZxmEoVEJTVpPJ4J7izx7sKzdM7Q>