From owner-freebsd-wireless@FreeBSD.ORG  Fri Oct  5 14:01:04 2012
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 81A961065677;
	Fri,  5 Oct 2012 14:01:04 +0000 (UTC)
	(envelope-from adrian@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 6E3518FC0C;
	Fri,  5 Oct 2012 14:01:04 +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 q95E14CB060181;
	Fri, 5 Oct 2012 14:01:04 GMT
	(envelope-from adrian@freefall.freebsd.org)
Received: (from adrian@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q95E14DH060177;
	Fri, 5 Oct 2012 14:01:04 GMT (envelope-from adrian)
Date: Fri, 5 Oct 2012 14:01:04 GMT
Message-Id: <201210051401.q95E14DH060177@freefall.freebsd.org>
To: adrian@FreeBSD.org, adrian@FreeBSD.org, freebsd-wireless@FreeBSD.org
From: adrian@FreeBSD.org
Cc: 
Subject: Re: kern/171816: [ath] [net80211] BAR TX overlapping with key
	renegotiation is causing issues?
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Discussions of 802.11 stack,
	tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
	<mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Oct 2012 14:01:04 -0000

Synopsis: [ath] [net80211] BAR TX overlapping with key renegotiation is causing issues?

State-Changed-From-To: open->closed
State-Changed-By: adrian
State-Changed-When: Fri Oct 5 13:59:11 UTC 2012
State-Changed-Why: 
This turned out to be an invalid bug - the actual cause of my
disconnects were "EAPOL frames were non-QoS and dumped into TID 16;
then they'd be put in the same hardware TXQ as best effort traffic;
any non-QoS broadcast/multicast traffic (eg ARP) would end up in TID
16."

Then "if any powersave occured, the EAPOL frames may be stuck in
a software queue; the ARP frames would be stuffed into the CABQ
and the ARP frames would go out first. But if they came in AFTER
the EAPOL frame, the EAPOL frame would have a sequence number
which is earlier and it'd be dropped.."


http://www.freebsd.org/cgi/query-pr.cgi?pr=171816