From owner-freebsd-wireless@FreeBSD.ORG Sun Oct 30 09:11:38 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 586EF1065676; Sun, 30 Oct 2011 09:11:38 +0000 (UTC) (envelope-from bpurgar@gmail.com) Received: from mail-gx0-f182.google.com (mail-gx0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 027E58FC15; Sun, 30 Oct 2011 09:11:37 +0000 (UTC) Received: by ggnq2 with SMTP id q2so6554977ggn.13 for ; Sun, 30 Oct 2011 02:11:37 -0700 (PDT) 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=7j8HdiAuPCm4/pW9zz1a9g0NvHoIyxvGI39S8okSQwo=; b=Ym8UGfvuMF0KtChdz9rreZK7nw1XKn3XlDCWsKC0BY92vmhKyKlZ/Gi3ohvXERq0VT W4fjaUCLWu/fn5rLVw3eoCCIGSK4LVCSWhyeDqhJctPAviHiNwNzuaCno1zpjL16tIHB qdHCfJGndg5CSY2NcXTbOsze51TMUbFvmvIZ8= MIME-Version: 1.0 Received: by 10.68.36.37 with SMTP id n5mr15588152pbj.105.1319965897047; Sun, 30 Oct 2011 02:11:37 -0700 (PDT) Received: by 10.142.125.13 with HTTP; Sun, 30 Oct 2011 02:11:36 -0700 (PDT) In-Reply-To: References: Date: Sun, 30 Oct 2011 10:11:36 +0100 Message-ID: From: Berislav Purgar To: Adrian Chadd Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-wireless@freebsd.org Subject: Re: if_ath_tx - svn r226797 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, 30 Oct 2011 09:11:38 -0000 On Sun, Oct 30, 2011 at 2:28 AM, Adrian Chadd wrote: > Hey, you're right - r225601 on my AR9220 in _congested_ 2.4ghz space > works a lot better. > I'm still getting stuck beacons, but nowhere near as many as before. > > I'm getting like 10,000-15,000 PHY errors a second though, so the NIC > is very much in interference city. > What's annoying is that an AR9160 _right next to it_ is not acting up at > all. > > Ok, I'll go digging later on to see what the story is. What's > unfortunate is this is the first time I've really seen it and it's > whilst sitting 12 storeys up in a hotel in Sydney.. this makes it > rather difficult to reproduce. :) > > > > Adrian > Same situation on me .. next to 9280 is 5212 and 5213 and i don't have any problems with these cards and stuck beacon errors. I'm still trying to find best rev for 9280 to work but for now 225601 is the best (only on 20MHz channel width / 40MHz is same like other revs . much more stuck beacon and BB hangs error) Beri