Date: Mon, 30 Jul 2012 21:40:10 GMT From: Adrian Chadd <adrian@freebsd.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/170254: [ath] Atheros 9220 device timeouts. Message-ID: <201207302140.q6ULeAY7085721@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/170254; it has been noted by GNATS. From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: bug-followup@freebsd.org Subject: Re: kern/170254: [ath] Atheros 9220 device timeouts. Date: Mon, 30 Jul 2012 14:39:44 -0700 On 30 July 2012 00:18, Lev Serebryakov <lev@freebsd.org> wrote: > Hello, Bug-followup. > > Here is more logs. Now, client was 802.11g only, and it was not > sleeping (I've wathcied movie on notebook from server, via WiFi). > I've got multiple device timeouts (1 per 20-30 seconds), and notebook > lost connection at all (it shows my AP in list of available APs, but > cannot associate with it). Only after 10 minutes (!) AP becomes > available again. Howdy, I'm going over the logs now. Thanks very much for this. Now, whilst I'm doing so - the next time this TX hang happens (where you can scan but can't associate/pass traffic), can you please log in to the AP and do 'sysctl dev.ath.0.txagg=1' and include that? I bet we'll find the TX buffers have been exhausted. The TX buffer exhaustion issue should really be fixed as a separate issue. I would like to see why you're seeing TX stalls. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207302140.q6ULeAY7085721>