From owner-freebsd-wireless@FreeBSD.ORG Thu Apr 25 20:27:05 2013 Return-Path: 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 1CB42284; Thu, 25 Apr 2013 20:27:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by mx1.freebsd.org (Postfix) with ESMTP id 806E51876; Thu, 25 Apr 2013 20:27:04 +0000 (UTC) Received: by mail-wg0-f50.google.com with SMTP id m15so1755118wgh.29 for ; Thu, 25 Apr 2013 13:27:03 -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 :content-transfer-encoding; bh=HPiMWzB9YqRhyNRqcXwdZnnK15FGCBSvXrdDLTOLDr8=; b=ofUbF3xbEtKBbkz22ggcFcqx6CmXm5c/+tr+kGwIWK8NJIfh4mufi4ZYiUUPKTAEdY RL6vkWyJa8MiBlkUDwo+ar1jvcW/oQASnDAklvanf8QWnXein5ztL925BW08IKEzvHfv Jmn7ukCCyCI2RXHSlwuuw6p9/QBcdNsJM0xBT8vprbfm3Sc5RSuxsk6781zl24v4IJ8t RS8VHhVlyl8FcKW04CsYrt5i0I0Pv4JlSsFuyg92kvd03JPJyF+b95AQMJnX2h0FGBOP VBk3jFYWHL/YCEM6xIWVDkdcb88qbrKmJKw0A4iIb0TrUPYGdLrgH6NyqND2Ql62Pcww hTdQ== MIME-Version: 1.0 X-Received: by 10.180.107.6 with SMTP id gy6mr64890wib.22.1366921623595; Thu, 25 Apr 2013 13:27:03 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.58.138 with HTTP; Thu, 25 Apr 2013 13:27:03 -0700 (PDT) In-Reply-To: <6010292503.20130426001447@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <1813905823.20130423184528@serebryakov.spb.ru> <184105677.20130424002002@serebryakov.spb.ru> <1936997795.20130424003555@serebryakov.spb.ru> <886711115.20130424004702@serebryakov.spb.ru> <6010292503.20130426001447@serebryakov.spb.ru> Date: Thu, 25 Apr 2013 13:27:03 -0700 X-Google-Sender-Auth: cuZKxuvlY0eDJjY-XQ5HTZlh988 Message-ID: Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 20:27:05 -0000 Hiya, On 25 April 2013 13:14, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 24 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 0:55:52: > > AC> Turn on reset debugging - sysctl dev.ath.0.debug=3D0x20 > Log attached. Debug was set to BAR + reset flags, UDP stream from AP > to client, at some moment AP stops to work and I've bring interface > down. Thanks. Yeah, the reset path isn't logging the contents of the TX queue. I'll go fix that in -HEAD and email you back when it's there. Thanks, adrian