From owner-freebsd-wireless@FreeBSD.ORG Thu May 9 19:24:08 2013 Return-Path: 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 2DD5682F; Thu, 9 May 2013 19:24:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by mx1.freebsd.org (Postfix) with ESMTP id EB13CDA2; Thu, 9 May 2013 19:24:07 +0000 (UTC) Received: by mail-pb0-f43.google.com with SMTP id md12so2212570pbc.2 for ; Thu, 09 May 2013 12:24:07 -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=i/TpEbtSZqE4Pk4qLdaeuGiRDIYM5hNSyL5TPmP+72M=; b=odi/s7GH3Yvw1n4psnsDKuzeAhikRDyg1FucX6YG5MhbJ+0F+/NiaH/OrWB4HBkLQm eiNwmZZu2BQD6uPq1+AsXd+zYm05VzpdlnxiLLWVSZhum1GPOC68+llfK971oS1aOz34 f9fjyaNZaE/WM9vFbT8Gm/QrSNLduJEvVs9SSKIVAKp4nFoQpyOEJBj6QVCozLVtXLbU Ou73kgupCyZBO51vbkTh4ETXW7a2GMrUe6MNohxkvvQoh2NWgvy/b85FDbCKC4u8LO5N zKVe8J9AnAGNcZvyYJweFa2Cs1HR+1MwFidpTdBCGznuY58uBE67TogTJw/rrtiKAht7 Oa8Q== MIME-Version: 1.0 X-Received: by 10.66.251.202 with SMTP id zm10mr14564063pac.53.1368127447810; Thu, 09 May 2013 12:24:07 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.70.85.73 with HTTP; Thu, 9 May 2013 12:24:07 -0700 (PDT) In-Reply-To: <510232154.20130509211849@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> <99510815.20130426122508@serebryakov.spb.ru> <124956607.20130430122459@serebryakov.spb.ru> <146903383.20130501000714@serebryakov.spb.ru> <94204652.20130501133220@serebryakov.spb.ru> <94971208.20130503122811@serebryakov.spb.ru> <105246227.20130509004931@serebryakov.spb.ru> <510232154.20130509211849@serebryakov.spb.ru> Date: Thu, 9 May 2013 12:24:07 -0700 X-Google-Sender-Auth: sjTFzwAvEq6wdbLChZJDF6eFylM 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=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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 May 2013 19:24:08 -0000 Hi, Next time you do this, can you do this: wlandebug +crypto +assoc +state I'd like to see what's actually going on behind the scenes. so: May 9 21:08:59 gateway sudo: lev : TTY=pts/1 ; PWD=/usr/home/lev/bin ; USER=root ; COMMAND=/sbin/sysctl dev.ath.0.debug=0x900000020 .. then a bunch of time, which I guess is you doing UDP: May 9 21:16:25 gateway kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff8000d7f000: bf=0xffffff800085d8e0: addbaw=0, dobaw=0, seqno=715, retry=0 May 9 21:16:25 gateway kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8000d7f000: bf=0xffffff800085d8e0: txq[1] axq_depth=502, axq_aggr_depth=0 May 9 21:16:25 gateway kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8000d7f000: bf=0xffffff800085d8e0: tid txq_depth=1 hwq_depth=503, bar_wait=0, isfiltered=0 May 9 21:16:25 gateway kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8000d7f000: tid 0: sched=1, paused=0, incomp=0, baw_head=0, baw_tail=0 txa_start=51018, ni_txseqs=61249 .. so: * hardware queue depth is 502 frames * no aggregates * there's only one frame in the TID txq, but 503 frames from that TID in the hardware queue * it's scheduled for more frames but there's likely no space left in the TXQ. But there's no hardware reset until you do a forcebstuck. So I guess that first one is actually a disassociate/reassociate bug more than anything. I bet this is what is actually going on. Can you please do the wlandebug above, so we can see if it's actually disassociating and not transitioning back through SCAN/ASSOC states? Thanks, adrian