From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 24 03:38:35 2011 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9611E1065676; Thu, 24 Nov 2011 03:38:35 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 5126A8FC15; Thu, 24 Nov 2011 03:38:35 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id pAO3cYT0065868; Wed, 23 Nov 2011 20:38:34 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id pAO3cYks065865; Wed, 23 Nov 2011 20:38:34 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 23 Nov 2011 20:38:34 -0700 (MST) From: Warren Block To: Adrian Chadd In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-1003571343-1322105914=:65846" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 23 Nov 2011 20:38:34 -0700 (MST) Cc: wireless@freebsd.org Subject: Re: Testing 802.11n 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: Thu, 24 Nov 2011 03:38:35 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-1003571343-1322105914=:65846 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 24 Nov 2011, Adrian Chadd wrote: > On 24 November 2011 06:39, Warren Block wrote: >> Statistics after it's been up for a while.  From a user perspective, no >> problems with the wireless at all. >> >> # athstats -i ath0 >> athstats: ath0: Invalid argument >> athstats: ath0: Invalid argument > > You're missing ATH_DIAGAPI? Yep. Here's the full version: # athstats -i ath0 9607 data frames received 1007 data frames transmit 32 tx frames with an alternate rate 509 long on-chip tx retries 7 tx failed 'cuz too many retries 8 mib overflow interrupts MCS7 current transmit rate 2833 rx failed 'cuz of bad CRC 126 rx failed 'cuz of PHY err 1 OFDM restart 125 CCK restart 26 periodic calibrations -0/+0 TDMA slot adjust (usecs, smoothed) 44 rssi of last ack 45 avg recv rssi -96 rx noise floor 146 tx frames through raw api 1178 A-MPDU sub-frames received 3 CRC errors for non-last A-MPDU subframes 5 Number of frames retransmitted in software 100 A-MPDU sub-frame TX attempt success 5 A-MPDU sub-frame TX attempt failures 1 first step level 1 OFDM weak signal detect 16 ANI increased spur immunity 16 ANI decrease spur immunity 16 ANI enabled OFDM weak signal detect 138 ANI disabled OFDM weak signal detect 122 ANI disabled CCK weak signal threshold 1 ANI increased first step level 31594 cumulative OFDM phy error count 32257 cumulative CCK phy error count 28 ANI forced listen time to zero 509 missing ACK's 3408 bad FCS 7163 beacons received 46 average rssi (beacons only) 45 average rssi (all rx'd frames) 44 average rssi (ACKs only) Antenna profile: [0] tx 913 rx 1194 [1] tx 0 rx 8413 ---902635197-1003571343-1322105914=:65846--