From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 30 18:35:28 2014 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 19B67B0B for ; Thu, 30 Jan 2014 18:35:28 +0000 (UTC) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CAA7F188A for ; Thu, 30 Jan 2014 18:35:27 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id e9so5567689qcy.12 for ; Thu, 30 Jan 2014 10:35:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=jZ21oUSLugX8vIO2b7muQwRzXuEAwsG3gkVUE8M3NCg=; b=pU0KtacClPR6ecEuh0Um/9ALrzzTbO4F+Peo/+/fnYjZ/XQ8EmeI74HbUcKBd2fUFl 3owjPM7KLkIJ7i+WH9v9a7+JM6QNuCOTYZZYS8U56x37EIZnaCH8lJhLZvAn5tfEax+T hNi3rzhIU5YnhxDgp8MobUbN8Ft7qHA0M15cr0p8eUqFZWxrBSgpdqaSdqz1pVwJSFgK eFmUhxgaLFWEpr0OJi3IFg2PmdZWoreDQofjk6K0JLApWePsU79EeBoXw9zqmk1wNwSP k9whN+S4mSNWpKLhvqLpug8Ex3csZhyxgyx5Z9MSsq2+fclneCxCJbhe0eIxw0LzRr0d FFJA== MIME-Version: 1.0 X-Received: by 10.140.96.180 with SMTP id k49mr22675255qge.4.1391106926989; Thu, 30 Jan 2014 10:35:26 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.52.8 with HTTP; Thu, 30 Jan 2014 10:35:26 -0800 (PST) In-Reply-To: <20140130184125.6659baf1@fusen> References: <20140116145401.760bbb3c@fusen> <20140116201941.6df23143@fusen> <20140120193101.0eef976d@fusen> <20140130184125.6659baf1@fusen> Date: Thu, 30 Jan 2014 10:35:26 -0800 X-Google-Sender-Auth: DKC1km0fYC6kd9iU2OwpYkIGrDQ Message-ID: Subject: Re: ar9580 failures [freebsd11-snapshot1930213] [2.4Ghz] From: Adrian Chadd To: Christophe Prevotaux Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.17 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, 30 Jan 2014 18:35:28 -0000 Hi, ok, so stuck beacon means a lot of things. It at the top end means "I couldn't transmit this beacon", and it could be for a variety of reasons: * the DMA engine hung; * the RX_BUSY or RX_CLEAR or TX_BUSY lines inside the chip are stuck; * the baseband has hung for some reason; * the DMA timing wasn't met and the frame didn't go out in time; * the PHY is calibrated incorrectly; * there's noise everywhere. So if it were me, I'd start by trying to make the athsurvey API work for the AR9300 HAL, so you could run 'athsurvey' whilst it was live and see what the story is. The MIB counters are a good starting point to see what the MAC thinks is going on. Eg, if RX_CLEAR is low (ie, the air is 'busy' according to the PHY.) I'd also enable NF calibration debugging to see what the noise floor and calibrated noise floor values are. If the differences between chains is more than 3dB then there's something wrong in the PHY that needs to be addressed. -a