From owner-freebsd-wireless@FreeBSD.ORG  Tue Apr 23 20:01:57 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id 1A31C718;
 Tue, 23 Apr 2013 20:01:57 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com
 [IPv6:2a00:1450:400c:c05::232])
 by mx1.freebsd.org (Postfix) with ESMTP id 80F5B1C05;
 Tue, 23 Apr 2013 20:01:56 +0000 (UTC)
Received: by mail-wi0-f178.google.com with SMTP id hm14so1289921wib.5
 for <multiple recipients>; Tue, 23 Apr 2013 13:01:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:sender:in-reply-to:references:date
 :x-google-sender-auth:message-id:subject:from:to:cc:content-type;
 bh=z4gNnnDOKTXxUmPkjub03m3qvkX88shIFmr9SpBRagk=;
 b=bSt5uQV40y5pH6ulJj4aZHCrtXembVSJz7mzDtqPMrtEKDDrvly9r4EOD6ag78/yPT
 8G2vxi7b2w/2h8zW4veESSv8WE9FWsEWFThjyYQ5jKD4nmqUd8kv2ckdcdP460wAniwU
 87IqjXqukGr82RSHGhpgpegIs7B2SU6gy//ZHjQF9WkNMqvunqphmSueD/YHH9O/gdY9
 NpWnMzvTEPXLuUEpDa7g8Zsvyf3Q8lvjiAFgvZNdzQ+OaAQK73r2sLyI4SaTa2ob8hui
 EEAn5u4GiekfQYkJw5oVJYSh3KoBAXg1X2Ffw3ZO0OdFY6I6bkN5duaUALslIoe4cjR/
 tWAw==
MIME-Version: 1.0
X-Received: by 10.194.142.236 with SMTP id rz12mr21796477wjb.12.1366747315717; 
 Tue, 23 Apr 2013 13:01:55 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.88.129 with HTTP; Tue, 23 Apr 2013 13:01:55 -0700 (PDT)
In-Reply-To: <CAAgmp6uCGEEDh6cS8qWsf4x4M7V3JQhvhhEiGsiMgGmqxmiPtg@mail.gmail.com>
References: <2810538978.20130423164137@serebryakov.spb.ru>
 <CAJ-Vmom4UDoz7EgdnVeQ+ALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com>
 <1813905823.20130423184528@serebryakov.spb.ru>
 <CAAgmp6uCGEEDh6cS8qWsf4x4M7V3JQhvhhEiGsiMgGmqxmiPtg@mail.gmail.com>
Date: Tue, 23 Apr 2013 13:01:55 -0700
X-Google-Sender-Auth: uRMy_W0-RlBVa5CvImJncCp8Lbs
Message-ID: <CAJ-VmokFWWBiF3z2suEKaYz4+UvEyZddZ1=hMExCx1YEpQJDBA@mail.gmail.com>
Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic
From: Adrian Chadd <adrian@freebsd.org>
To: Petko Bordjukov <bordjukov@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: lev@freebsd.org, freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Apr 2013 20:01:57 -0000

On 23 April 2013 12:57, Petko Bordjukov <bordjukov@gmail.com> wrote:
> Falling back to a ht:20- channel did considerably lower the number of stuck
> beacon messages on my AR9220. It still periodically hangs though (is this
> why ``baseband hangs?'' is listed in the wiki?).

Well, partially.

I'm seeing stuck beacons in my testing with my modified AP power save
code running, so it's also possible that there's something odd going
on with the hardware programming that's locking things up. Luckily I
can easy reproduce it, so I'm going to dig into it a bit more and see
what I find.



Adrian