From owner-freebsd-wireless@FreeBSD.ORG Thu Nov 3 03:17:07 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 69CFC106566C for ; Thu, 3 Nov 2011 03:17:07 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 29E128FC14 for ; Thu, 3 Nov 2011 03:17:06 +0000 (UTC) Received: by vcbfk26 with SMTP id fk26so1171020vcb.13 for ; Wed, 02 Nov 2011 20:17:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=1+B3LgoTb5RnC3CEziDj+bu36lhleIY5grumbn0NnVw=; b=Y8eaSMWTBY32FA2Hg7l4279r3rWRigkqMii4cDbcuxyxQpZTPTl/shRLiAu801wlwA ZoYUAsgXyp8rb1+V9JuiVQiTLHKqkk8g9UlacpvgdnaRRRfLCG9RUuDBbGCbhjrx6uyP F9hgvrG8IrmqgUOri995HVntu75Xg0f4Z1LcE= MIME-Version: 1.0 Received: by 10.52.35.147 with SMTP id h19mr7669905vdj.38.1320290226096; Wed, 02 Nov 2011 20:17:06 -0700 (PDT) Received: by 10.52.29.198 with HTTP; Wed, 2 Nov 2011 20:17:06 -0700 (PDT) Date: Wed, 2 Nov 2011 20:17:06 -0700 Message-ID: From: Adrian Chadd To: Berislav Purgar Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: AR9280 and noisy environments, please test 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, 03 Nov 2011 03:17:07 -0000 Hi all, I've added some local hacks to my if_ath_tx branch which hopefully will help us nail down what's going on with AR9280 and noisy environments. The theory: AR9220/AR9280 noise floor sampling is not picking up the bursty traffic that's going on in the air. so it's reporting a low NF but as the air spends most of its time with _some_ signal above what it thinks the NF is, it constantly thinks the channel isn't clear to TX. I saw this with AR9160 last year but it turned out to be issues with the AP power supply enclosure generating 2.4ghz spurs. I doubt we're seeing this here. :) The changes: * I've updated the ANI code a bit more, so it does some more "stuff" in hostap mode; * I've disabled OFDM weak detection by default in hostap mode, but I haven't (yet) disabled CCK weak threshold setting; * I've added some very rudimentary support to log how busy the channel is, so we can see what the difference is between different 11n NICs; * I've added a knob to allow the noise floor threshold (and thus the CCA threshold) to be manually set, rather than relying on sampling by the baseband. What I'd like you guys to try: * update if_ath_tx! * run the ar9280 in hostap or STA mode, it doesn't matter what, but enable NF and ANI debugging: # sysctl dev.ath.X.hal.debug=0x28 * let it run for a couple of minutes, so it gets a couple of NF calibrations (which occur every 30 seconds) and then report that to me. What you'll likely see is: * ANI goes bezerk with OFDM/CCK errors, and tries bumping up some things (spur immunity, firstep); * the NF values calibrated are either crazy looking (higher than -80), or chain 0 / chain 1 values are wildly mismatching; Then, try changing the longcal value from 30 to 1, and email me two or so minutes of logging output. Finally, set the CCA threshold to something manual, and rerun tests for a couple minutes: # sysctl dev.ath.X.config.cca=-85 Thanks, Adrian