From owner-freebsd-bugs@FreeBSD.ORG Mon Jul 30 21:40:10 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8579F106566B for ; Mon, 30 Jul 2012 21:40:10 +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 6FD688FC18 for ; Mon, 30 Jul 2012 21:40:10 +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 q6ULeAAq085722 for ; Mon, 30 Jul 2012 21:40:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q6ULeAY7085721; Mon, 30 Jul 2012 21:40:10 GMT (envelope-from gnats) Date: Mon, 30 Jul 2012 21:40:10 GMT Message-Id: <201207302140.q6ULeAY7085721@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Adrian Chadd Cc: Subject: Re: kern/170254: [ath] Atheros 9220 device timeouts. X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Chadd List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 21:40:10 -0000 The following reply was made to PR kern/170254; it has been noted by GNATS. From: Adrian Chadd 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 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