From owner-freebsd-wireless@FreeBSD.ORG  Tue Apr 30 22:17:54 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id 9DE64F73;
 Tue, 30 Apr 2013 22:17:54 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com
 [IPv6:2a00:1450:400c:c05::22f])
 by mx1.freebsd.org (Postfix) with ESMTP id 0744F1C38;
 Tue, 30 Apr 2013 22:17:53 +0000 (UTC)
Received: by mail-wi0-f175.google.com with SMTP id h11so4446675wiv.8
 for <multiple recipients>; Tue, 30 Apr 2013 15:17:53 -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=qthXf9a46Q9uQaC99eW47Iw+T/DZhf/4wpxco6DPH5k=;
 b=U+Jlj7GedBrJe5noIx9yg3x5DeffLNHFxcLOPJuq6e2kOim1eVwV/j1b5kSyIIfRqA
 mT6gnd4d7aGpp70gM7MQycUKd5v1TLvwwLc8iCrGjWxa2Uk/ZLAl/VabH6q9w8kdf18V
 zQKMERqbScE98MfD7LSFiate2yJ8EULvJLm7omddXDnC36hgMFlzuION7xTYePiXUsF6
 kyQdkZvhfxnTt4iktRK5poKCN02cKkiwrROzBwlUeIwcDFdYE0fxSwuRt0T8HyrCsQKQ
 i4/XuQatozDjSJI+gmnI8RanFIBykwjd3+85no7AXLaN6TZ+v7gSZTE11E5USvid8FUV
 FW1w==
MIME-Version: 1.0
X-Received: by 10.194.248.200 with SMTP id yo8mr226287wjc.36.1367360273165;
 Tue, 30 Apr 2013 15:17:53 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.58.138 with HTTP; Tue, 30 Apr 2013 15:17:52 -0700 (PDT)
In-Reply-To: <146903383.20130501000714@serebryakov.spb.ru>
References: <2810538978.20130423164137@serebryakov.spb.ru>
 <CAJ-Vmom4UDoz7EgdnVeQ+ALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com>
 <1813905823.20130423184528@serebryakov.spb.ru>
 <CAJ-VmomhRaKODxis09MjAhUbAUOw+6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com>
 <184105677.20130424002002@serebryakov.spb.ru>
 <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com>
 <1936997795.20130424003555@serebryakov.spb.ru>
 <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com>
 <886711115.20130424004702@serebryakov.spb.ru>
 <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com>
 <6010292503.20130426001447@serebryakov.spb.ru>
 <CAJ-VmomUsPgHTVGaKHZ_YE+u1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com>
 <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com>
 <99510815.20130426122508@serebryakov.spb.ru>
 <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com>
 <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com>
 <725880393.20130429004352@serebryakov.spb.ru>
 <CAJ-Vmokz=0rZM-nHtt9S+a-SxRLuyP+yDhSAbLpr0xFS+pO3vA@mail.gmail.com>
 <187241224.20130429113623@serebryakov.spb.ru>
 <CAJ-Vmo=MzeJsKHfVoipPQqCRmkOHWk6p-iZNaXDwye6oG+76xg@mail.gmail.com>
 <CAJ-Vmo=b-kBDWKz=Y709kYEsYQt3ZRczCN0wG9zDRk=sR60+tg@mail.gmail.com>
 <124956607.20130430122459@serebryakov.spb.ru>
 <CAJ-VmonQXyB_Aik-ApSmgRqT3yhD5Bqrx3zj+KM+itVmZhY0TQ@mail.gmail.com>
 <146903383.20130501000714@serebryakov.spb.ru>
Date: Tue, 30 Apr 2013 15:17:52 -0700
X-Google-Sender-Auth: 6-gEHvVGewW4UpC7fuJADqQvvzw
Message-ID: <CAJ-Vmo=n27vAzsEPDwaO+jxS-n42WBbiNyfpvmnO931q1CKcDA@mail.gmail.com>
Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic
From: Adrian Chadd <adrian@freebsd.org>
To: lev@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: 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, 30 Apr 2013 22:17:54 -0000

Well, right now I'm trying to figure out whether there's a race
condition in setting up / enabling the TX queue that I haven't yet
seen before, or whether we've hit another one of those corner case
bugs in the TX queue handling.

I may add in a hack to the completion code that checks if the queue
isn't active and if it isn't (but there's frames in the TX queue), it
restarts TX.


adrian