From owner-freebsd-wireless@FreeBSD.ORG Fri Aug 26 11:42:13 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 B6E931065670 for ; Fri, 26 Aug 2011 11:42:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 663908FC08 for ; Fri, 26 Aug 2011 11:42:13 +0000 (UTC) Received: by ywo32 with SMTP id 32so3273121ywo.13 for ; Fri, 26 Aug 2011 04:42:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=OUf2PmZtWIHDLXnqhAW8rnCNJAu1UpShblI+Dqkir+I=; b=vCJv+jSKaSoJi3lO3QfCgRwbDVAscnK2/ZjrgsMnX6jcw62zfZhawJeYn3zjTRlzk0 QiNl4PpTxUOTr/MPlrGOvmN/tcJSHZGBcZmOPFBU96P33vAPVDlaePotnO788sBzWlOZ 0f09zoXTi1eZiILse+x7EtRWzv65grC+yUKbs= MIME-Version: 1.0 Received: by 10.151.42.18 with SMTP id u18mr2111802ybj.429.1314357595509; Fri, 26 Aug 2011 04:19:55 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.150.145.21 with HTTP; Fri, 26 Aug 2011 04:19:55 -0700 (PDT) In-Reply-To: <957EB052144AA64AB39F7AB26878320101215E9CB8@VA3DIAXVS881.RED001.local> References: <957EB052144AA64AB39F7AB26878320101215E9CB8@VA3DIAXVS881.RED001.local> Date: Fri, 26 Aug 2011 19:19:55 +0800 X-Google-Sender-Auth: Kr4J-8VNliccom_u6fqevAqPtAE Message-ID: From: Adrian Chadd To: Edgar Martinez Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: XR9 w 8.2 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: Fri, 26 Aug 2011 11:42:13 -0000 (re-cc'ing freebsd-wireless as it's interesting.) On 26 August 2011 19:14, Edgar Martinez wrote: > what's causing the stuck beacons you think? No idea. :) Lot's of reasons. DMA taking too long, TX engine is stuck, RX CLEAR is stuck low, the medium is too busy, calibration is taking too long, etc. > also when the ucast rate is set to 6, I notice that all nodes have a minimum latency of 17ms. > > when set to 12, they appear to work just fine. ideas? No idea? :) "6" should be an OFDM rate, same as 12. Maybe there's something going on with power calibration in the AR5212 series NICs that needs the higher rates to be used? (Since the earlier nics use PAPRD test frames to calibrate the output TX.) Adrian