From owner-freebsd-wireless@FreeBSD.ORG Sat Jul 21 18:35:20 2012 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 6EE48106566B for ; Sat, 21 Jul 2012 18:35:20 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 41E948FC08 for ; Sat, 21 Jul 2012 18:35:20 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so8868865pbb.13 for ; Sat, 21 Jul 2012 11:35:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=AItp1H+1ZR8Zbn8CMV42cJDHCGrBeU5jbE1ozwiLXio=; b=zFOvPbD8wfMFr+WK1cEthhjFrZw3oqx0/Q3ttfqLa54sLawr62mtOfJjHTvMKGkBYC 4aL2Mm2DfaiaID+PcNZaeQXOJ0bqXok+CqO+56HzHecCkNX/tV6JEbtew7so2fATVmEB 3MSGMRjTDMkILEwNh9liQT/MCZLjAltbWC8wM+MKlcuqhNUm7eKZLjasEW+mWte9VsML /9ARymcEzfpYH1iRN4IISaOD4498pwvGc/RfThrUBrvWvVnuPlayvRdXsG8Y9xDgb23Q LgsBxNidCygtZzLxo+QW7ns9WJHo049ETBIqGA20lb0tsv24y2mK3azy733+OV7FQG+A dYyw== MIME-Version: 1.0 Received: by 10.66.84.7 with SMTP id u7mr7647498pay.83.1342895720043; Sat, 21 Jul 2012 11:35:20 -0700 (PDT) Received: by 10.68.191.138 with HTTP; Sat, 21 Jul 2012 11:35:20 -0700 (PDT) In-Reply-To: References: Date: Sat, 21 Jul 2012 11:35:20 -0700 Message-ID: From: Adrian Chadd To: Kim Culhan Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: r238613 NF cal didn't finish 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, 21 Jul 2012 18:35:20 -0000 On 21 July 2012 03:43, Kim Culhan wrote: > The system has been running in its current config for > 12 hours with no > instances of the nfcal message. Yup. So what's happening (now that I have 30 seconds of spare time): * the initial reset path in the HAL starts an NF calibration; * then the driver _immediately_ calls the HAL calibration routine, which checks if an NF cal is in progress; * .. and since the previously started one may still be in progress, it skips (re)starting a new one. It only shows up on: * AR5416, in moderately noisy environments; * any of the chips, if there's a very strong interferer signal present; * in station mode with scanning, as there's lots of channel changes going on. The print is there because I'd like to be told if it's constantly happening. It coincides with strong interference and/or RX deafness, so it's good to have as a data point. Thanks again for testing this out! Adrian