From owner-freebsd-wireless@FreeBSD.ORG Tue Dec 27 16:03:58 2011 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 3AB8C106564A for ; Tue, 27 Dec 2011 16:03:58 +0000 (UTC) (envelope-from gperez@entel.upc.edu) Received: from dash.upc.es (dash.upc.es [147.83.2.50]) by mx1.freebsd.org (Postfix) with ESMTP id A15C48FC16 for ; Tue, 27 Dec 2011 16:03:57 +0000 (UTC) Received: from ackerman2.upc.es (ackerman2.upc.es [147.83.2.244]) by dash.upc.es (8.14.1/8.13.1) with ESMTP id pBRG3tPd010029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 27 Dec 2011 17:03:55 +0100 Received: from portgus.lan (235.Red-81-39-131.dynamicIP.rima-tde.net [81.39.131.235]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id pBRG3n4F026852 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Tue, 27 Dec 2011 17:03:54 +0100 Message-ID: <4EF9EC54.1070005@entel.upc.edu> Date: Tue, 27 Dec 2011 17:03:32 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:9.0) Gecko/20111223 Thunderbird/9.0 MIME-Version: 1.0 To: Adrian Chadd References: <3d4d2d249836fafc6acd885693c02198@webmail.entel.upc.edu> <4ECFCDAB.1080407@entel.upc.edu> <4ED3B4D1.3020701@entel.upc.edu> <4EDA4BBA.6010203@entel.upc.edu> <4EDA609F.2080401@entel.upc.edu> <4EDB3A2B.4050503@entel.upc.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.70 on 147.83.2.244 X-Mail-Scanned: Criba 2.0 + Clamd X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (dash.upc.es [147.83.2.50]); Tue, 27 Dec 2011 17:03:55 +0100 (CET) Cc: freebsd-wireless@freebsd.org Subject: Re: Big delays between an AR5416 AP and its clients 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: Tue, 27 Dec 2011 16:03:58 -0000 On 04/12/2011 11:22, Adrian Chadd wrote: > Ok, to enable logging: > > Firstly, let's just debug the non-beacon TX : > > sysctl dev.ath.0.debug=0x3c000000 > wlandebug -i wlan0 +rate > > Then send some pings. You'll get a _lot_ of debugging. Please capture > some debugging. :) > Point out which log entries correspond to increased latency. > > (This is assuming it's a TX issue; it's possibly an RX issue too..) > > Thanks, > > > Adrian Hi Adrian, I managed to get a trace of the debug info. The file is HUGE and to make things worse I can't tell exactly when it started to happen. The trace beggins with no iphone associated while pinging the AR5416 box. Then, I started the iphone's supplicant, and at around 16:53:14 the latency problem appeared. I hope it tells you anything useful, because I don't know what I'm looking for. The trace can be downloaded at: http://www-entel.upc.edu/gus/ath_tx_logging.xz Please let me know if you need any additional info. Gus