From owner-freebsd-wireless@FreeBSD.ORG Sun Mar 11 01:42:28 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E5DBB106566C; Sun, 11 Mar 2012 01:42:28 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 52EC88FC15; Sun, 11 Mar 2012 01:42:28 +0000 (UTC) Received: from badger.unsane.co.uk (badger.unsane.co.uk [85.233.185.165]) (authenticated bits=0) by unsane.co.uk (8.14.5/8.14.5) with ESMTP id q2B1gRVa004835 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 11 Mar 2012 01:42:27 GMT (envelope-from vince@unsane.co.uk) Message-ID: <4F5C0302.8090403@unsane.co.uk> Date: Sun, 11 Mar 2012 01:42:26 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Adrian Chadd References: <4F59DD98.8080905@unsane.co.uk> <4F5AA149.8000904@unsane.co.uk> <4F5BDF3C.8070605@unsane.co.uk> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-wireless@freebsd.org Subject: ath0 timeout was "Re: (more) bugs fixed in -HEAD, AP mode is now mostly (again) stable!" 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2012 01:42:29 -0000 On 11/03/2012 00:00, Adrian Chadd wrote: > The next time it happens, please do this: sysctl dev.ath.0.txagg=1 and > then check dmesg, email the list the output. I'd like to see if the TX > queue is stuck. Then, force a scan: ifconfig wlan0 scan Even if it's > in hostap mode, it'll cause a full TX queue flush and if 11n TX > aggregation is stuck for whatever reason, it'll complain bitterly at > you in dmesg. Thanks, Adrian as requested. output of dmesg after a timeout, then me setting the sysctl http://unsane.co.uk/ath-timeout-dmesg.txt output after i then ran ifconfig wlan0 scan http://unsane.co.uk/ath-timeout-dmesg-with-scan.txt Please note that it hung twice in these dmesg, the first time I didnt see it until after it had recovered, I then ran sysctl dev.ath.0.txagg=1 but not the scan as it hung again shortly after (passing much traffic will do it it seems.) On the second hang I set the sysctl before the network connection came back, then ran ifconfig wlan0 scan. Output of the scan is SSID/MESH ID BSSID CHAN RATE S:N INT CAPS Radford_Net... 00:19:e0:a1:2f:f8 6 54M -93:-96 100 EPS RSN WPA ATH BTHomeHub2-... 00:21:04:c2:d6:c2 11 54M -93:-96 100 EPS RSN WPA WME HTCAP O2wireless9... 00:24:17:97:84:31 3 54M -92:-96 100 EP RSN virginmedia... a0:21:b7:e3:5b:89 5 54M -92:-96 100 EP RSN HTCAP WPS WPA WME vhoff e0:91:f5:48:5b:b9 5 54M -77:-96 100 EPS RSN WPA WME HTCAP ATH WPS Seems someone has switched channels to be on the same as me again :( ath and ath_pci complied into the kernel. Any more info needed let me know. Vince