From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 1 20:48:50 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 7D002106564A for ; Sun, 1 Jan 2012 20:48:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2EA078FC13 for ; Sun, 1 Jan 2012 20:48:50 +0000 (UTC) Received: by vbbfr13 with SMTP id fr13so20568199vbb.13 for ; Sun, 01 Jan 2012 12:48:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=kgpzp4C1zDwzR0W9vxKbjtQ/teR/dF3jW9ek+mVF5nA=; b=f9tHC4OaGQ1IKlCvK7r1jgL0FxOtq2Ckq+L7hLZLgsNa9ev7tURoKJGM//mZcfLSUA SecLHeCO65X7hNzNs6xR70YUitw5AH+6QuWKiEq2ba+KrQLa/iJk5IHzSlSRjroR2KZk ctMq3KOttNDk1rZoWOoJlr+QSgFkHN/OgNHiU= MIME-Version: 1.0 Received: by 10.52.29.16 with SMTP id f16mr22035462vdh.45.1325450929590; Sun, 01 Jan 2012 12:48:49 -0800 (PST) Received: by 10.52.36.5 with HTTP; Sun, 1 Jan 2012 12:48:49 -0800 (PST) In-Reply-To: References: Date: Sun, 1 Jan 2012 12:48:49 -0800 Message-ID: From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" Subject: Re: ath "stops working" in hostap mode 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: Sun, 01 Jan 2012 20:48:50 -0000 Hi, Can you please wrap up all the attachments and stuff you've sent me and submit a PR for this? It looks like another noisy air problem. Or, something is configuring the radio in a way that completely messes up the noise. Try setting dev.ath.0.hal.force_full_reset to 1 if you're running -HEAD. Although I'm still not convinced I've done the "full reset" code entirely right.. Basically, some of the PHY parameters don't seem to be fully reset after a warm reset - they require a cold reset. I've noticed this on the AR9280, where things will get sufficiently upset as to force a storm of stuck beacons to appear. The only thing that fixes it is a complete power down and up of the PHY/radio, which we can do inside software. (We can't power down a few things on the NIC, but we can reset enough things for the RF issues to clear up.) There's another potential bug with the ANI code and how the PHY registers are read. It has the potential to make garbage choices and program in some terrible values to the signal detection/size/level PHY registers. I haven't yet sat down to write the solution to that. I really should. :) So please, file a PR so I don't forget to chase this stuff down. Adrian