From owner-freebsd-wireless@FreeBSD.ORG Sat Dec 3 17:47:17 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 697FB106566B for ; Sat, 3 Dec 2011 17:47:17 +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 D5B5B8FC0C for ; Sat, 3 Dec 2011 17:47:16 +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 pB3HlDox031382 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 3 Dec 2011 18:47:14 +0100 Received: from portgus.lan (141.Red-81-39-182.dynamicIP.rima-tde.net [81.39.182.141]) (authenticated bits=0) by ackerman2.upc.es (8.14.4/8.14.4) with ESMTP id pB3HlC6k021105 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sat, 3 Dec 2011 18:47:13 +0100 Message-ID: <4EDA609F.2080401@entel.upc.edu> Date: Sat, 03 Dec 2011 18:47:11 +0100 From: =?ISO-8859-1?Q?Gustau_P=E9rez?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:8.0) Gecko/20111111 Thunderbird/8.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> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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]); Sat, 03 Dec 2011 18:47:14 +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: Sat, 03 Dec 2011 17:47:17 -0000 On 03/12/2011 17:22, Adrian Chadd wrote: > 2011/12/4 Gustau Pérez: > >> I see nothing particular in my dmesg with wlandebug enabled. I see the >> AR5416 complaining about a beacon off-channel for a MAC I don't know about. >> I also see the iphone's MAC going power save with a message like this: >> >> power save mode on, 2 sta's in ps mode > Well, it _is_ doing power saving, which I expected. This doesn't at > all correlate with the periodicity of the issue? No it doesn't. The period of the issue was 0.1sec, because it happens after 10 pings and the time between pings was 0.01 seconds. During the tests the power save mode message only appeared 4 times, and they did during a second and then never appeared again. As I was doing 5 times 6000 pings and the problem repeats every 10 pings, I would have expected the message about 5*600 times. So I would say they don't correlate at all. During normal operation the power save mode on also appears. Other stations also trigger that message. > >> However, I see these the following entries in my dmesg when using r227364: >> >> Dec 3 16:46:27 harkserver kernel: Timeout while waiting for nf >> to load: AR_PHY_AGC_CONTROL=0x41d1a >> Dec 3 16:46:27 harkserver kernel: Timeout while waiting for nf >> to load: AR_PHY_AGC_CONTROL=0x41d1a >> >> Dec 3 16:18:27 harkserver kernel: ar5416PerCalibrationN: NF >> >> calibration didn't finish; delaying CCA >> Dec 3 16:18:27 harkserver kernel: ar5416PerCalibrationN: NF >> >> calibration didn't finish; delaying CCA >> >> I don't see those messages with a previous revision because they appear to >> be part of r227364. Those problems appear from time to time, could they and >> the latency increase be related? > That could be related. If the device thinks the air is constantly busy > (or it's spending a lot of time trying to TX) then it may fail NF > calibration. > I just wonder what I've changed which may be causing the NIC to behave this way. > > What's interesting (!) is that I have seen similar reports with ath9k > in Linux. I wonder if part of the 11n work (that ath9k has also > borrowed) has the same broken behaviour on the AR5416. Well, if they did have that issue, maybe we could also borrow their solution. Did they fix the issue. Do you have any link I could read and try while you finish unpacking yourself :) ? > Can you please file all of this in the PR? I'll have finished moving > by December 15 so I can start trying to replicate this issue and help > you debug it. > > You can count on this. I'll fill the PR with the collected info. It may get quite long, so maybe I'll fill it tomorrow. Thanks, Gus