kern/166190: [ath] TX hangs and frames stuck in TX queue
Adrian Chadd
adrian.chadd at gmail.com
Mon Mar 19 21:50:13 UTC 2012
The following reply was made to PR kern/166190; it has been noted by GNATS.
From: "Adrian Chadd" <adrian.chadd at gmail.com>
To: "Vincent Hoffman" <vince at unsane.co.uk>, "bug-followup at freebsd.org"
<bug-followup at 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&T
On Mar 19, 2012 2:38 PM, Vincent Hoffman <vince at unsane.co.uk> 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 <vince at unsane.co.uk> 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--
More information about the freebsd-wireless
mailing list