kern/167491: [ath] TID != hardware queue TID in ath_tx_aggr_comp_aggr()

Adrian Chadd adrian at FreeBSD.org
Tue May 1 15:50:09 UTC 2012


>Number:         167491
>Category:       kern
>Synopsis:       [ath] TID != hardware queue TID in ath_tx_aggr_comp_aggr()
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 01 15:50:09 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Adrian Chadd
>Release:        10.0-CURRENT
>Organization:
>Environment:
FreeBSD home-11bg-ap 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r234826M: Wed Dec 31 16:00:00 PST 1969     adrian at dummy:/home/adrian/work/freebsd/svn/obj/mipseb/mips.mips/usr/home/adrian/work/freebsd/svn/src/sys/TP-WN1043ND  mips

>Description:
After the recent net80211 TX aggregation state handling changes (changing from per-AC to per-TID), I've begun seeing these messages pop up in the log:


ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 9
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 4
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 13
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8
ath0: ath_tx_aggr_comp_aggr: tid 0 != hw tid 8

The code came over from Linux/atheros with this comment:

        /* Occasionally, the MAC sends a tx status for the wrong TID. */

However, I don't recall seeing this problem whilst the TX aggregation state was being kept per-AC, rather than per-TID.
>How-To-Repeat:
Enable ath(4) 802.11n, use as hostap, do a whole lot of aggregate traffic.

>Fix:
None yet.

>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list