From owner-freebsd-wireless@FreeBSD.ORG  Mon Mar 19 21:50:13 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 619BB106564A
	for <freebsd-wireless@hub.freebsd.org>;
	Mon, 19 Mar 2012 21:50:13 +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 338948FC1C
	for <freebsd-wireless@hub.freebsd.org>;
	Mon, 19 Mar 2012 21:50:13 +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 q2JLoDa5032062
	for <freebsd-wireless@freefall.freebsd.org>;
	Mon, 19 Mar 2012 21:50:13 GMT
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2JLoDNk032061;
	Mon, 19 Mar 2012 21:50:13 GMT (envelope-from gnats)
Date: Mon, 19 Mar 2012 21:50:13 GMT
Message-Id: <201203192150.q2JLoDNk032061@freefall.freebsd.org>
To: freebsd-wireless@FreeBSD.org
From: "Adrian Chadd" <adrian.chadd@gmail.com>
Cc: 
Subject: Re: kern/166190: [ath] TX hangs and frames stuck in TX queue
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Adrian Chadd <adrian.chadd@gmail.com>
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: Mon, 19 Mar 2012 21:50:13 -0000

The following reply was made to PR kern/166190; it has been noted by GNATS.

From: "Adrian Chadd" <adrian.chadd@gmail.com>
To: "Vincent Hoffman" <vince@unsane.co.uk>, "bug-followup@freebsd.org"
  <bug-followup@freebsd.org>
Cc:  
Subject: Re: kern/166190: [ath] TX hangs and frames stuck in TX queue
Date: Mon, 19 Mar 2012 14:49:28 -0700

 --Alternative__boundary__1332193773950
 Content-Type: text/plain; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Just check the txagg sysctl and mae sure your buffer count stays up around=
  512.
 
 I want to make sure that buffers aren't being leaked.
 
 Thanks again!
 
 
 
 Sent from my Palm Pre on AT&amp;T
 On Mar 19, 2012 2:38 PM, Vincent Hoffman &lt;vince@unsane.co.uk&gt; wrote:=
  
 
 Hi Adrian,
 
 
 
 
 
         This patch is looking good as yet, I've repeated tests that were
 
 previously causing timeouts and as yet not been able cause a timeout
 
 after applying this patch.
 
 
 
     Its not definitive but so far it appears to have resolved this issue
 
 for me.
 
 
 
 
 
 Regards,
 
 Vince Hoffman
 
 
 
 --Alternative__boundary__1332193773950
 Content-Type: text/html; charset=UTF-8
 Content-Transfer-Encoding: quoted-printable
 
 Just check the txagg sysctl and mae sure your buffer count stays up around=
  512.<br><br>I want to make sure that buffers aren't being leaked.<br><br>T=
 hanks again!<br><br><span style=3D"font-family:Prelude, Verdana, san-serif;=
 "><br><br></span><span id=3D"signature"><div style=3D"font-family: arial,=
  sans-serif; font-size: 12px;color: #999999;">Sent from my Palm Pre on AT&a=
 mp;T</div><br></span><span style=3D"color:navy; font-family:Prelude, Verdan=
 a, san-serif; "><hr align=3D"left" style=3D"width:75%">On Mar 19, 2012 2:38=
  PM, Vincent Hoffman &lt;vince@unsane.co.uk&gt; wrote: <br><br>Hi Adrian,
 <br>
 <br>
 <br>        This patch is looking good as yet, I've repeated tests that were
 <br>previously causing timeouts and as yet not been able cause a timeout
 <br>after applying this patch.
 <br>
 <br>    Its not definitive but so far it appears to have resolved this issue
 <br>for me.
 <br>
 <br>
 <br>Regards,
 <br>Vince Hoffman
 <br></span>
 
 --Alternative__boundary__1332193773950--