From owner-freebsd-bugs@FreeBSD.ORG Tue May 1 15:50:09 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AEB191065688 for ; Tue, 1 May 2012 15:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 80A908FC15 for ; Tue, 1 May 2012 15:50:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q41Fo9x3003944 for ; Tue, 1 May 2012 15:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q41Fo9vZ003941; Tue, 1 May 2012 15:50:09 GMT (envelope-from gnats) Resent-Date: Tue, 1 May 2012 15:50:09 GMT Resent-Message-Id: <201205011550.q41Fo9vZ003941@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Adrian Chadd Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 58C241065673 for ; Tue, 1 May 2012 15:46:43 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 2A5438FC0A for ; Tue, 1 May 2012 15:46:43 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q41FkhaC010646 for ; Tue, 1 May 2012 15:46:43 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q41FkgW4010645; Tue, 1 May 2012 15:46:42 GMT (envelope-from nobody) Message-Id: <201205011546.q41FkgW4010645@red.freebsd.org> Date: Tue, 1 May 2012 15:46:42 GMT From: Adrian Chadd To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/167491: [ath] TID != hardware queue TID in ath_tx_aggr_comp_aggr() X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 May 2012 15:50:09 -0000 >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@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: