From owner-freebsd-wireless@FreeBSD.ORG  Fri Apr 26 00:11:46 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 7AF01C33;
 Fri, 26 Apr 2013 00:11:46 +0000 (UTC)
 (envelope-from adrian.chadd@gmail.com)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com
 [IPv6:2a00:1450:400c:c03::22a])
 by mx1.freebsd.org (Postfix) with ESMTP id DF4741244;
 Fri, 26 Apr 2013 00:11:45 +0000 (UTC)
Received: by mail-we0-f170.google.com with SMTP id z2so3103928wey.15
 for <multiple recipients>; Thu, 25 Apr 2013 17:11:44 -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=mszYyRbH2eX5OVF/aRKBE3Jd9NftJGeKED/fzt/q31Q=;
 b=RfWG6fpWobf4v6oFl0yl/Icqlqlp0YDO8TxSbhnWtkOJWdWl00Tr6Lm0tTmBXNy6Ia
 jcq6SXtENfq6TxcsjvJt2KLoH+J+DXfkfw2biCvl5HSFv28A1R73qyCef6wbdcdIorf3
 M9ZIwDIT1KwfyoZc4ufqCG7RVvpdgDrHEpiOBNIkq3reFVW8simeV2iuJqSqNKGc97LT
 VRqozLCSKKC+AOCPQaAZAlk4hqZyRrJAIBzLncM38sQ4JfjcrVMHUy4//eFNT5szKDb+
 Q1bx+tj3dVCpsB2nOzv8OKu3dAsPOu4/LYInIccp9h06X9Z8ut+2sJGAoZdeLreAPf3s
 MYwA==
MIME-Version: 1.0
X-Received: by 10.194.119.33 with SMTP id kr1mr78728914wjb.36.1366935104317;
 Thu, 25 Apr 2013 17:11:44 -0700 (PDT)
Sender: adrian.chadd@gmail.com
Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 17:11:44 -0700 (PDT)
In-Reply-To: <CAJ-VmomUsPgHTVGaKHZ_YE+u1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com>
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>
Date: Thu, 25 Apr 2013 17:11:44 -0700
X-Google-Sender-Auth: j3nhMaoYCbIY9hqBb1ioGm43aYY
Message-ID: <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@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: Fri, 26 Apr 2013 00:11:46 -0000

Ok. Next time it happens, force a stuck beacon:

sysctl dev.ath.X.forcebstuck=1

That will cause the right kind of reset in order to log the frames in
the TX queue.

Make sure you have the right debug mask though!


Adrian