From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 23 13:57:56 2012 Return-Path: Delivered-To: wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 57D02106564A for ; Mon, 23 Jul 2012 13:57:56 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id C7D548FC0A for ; Mon, 23 Jul 2012 13:57:55 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:a84b:9962:ac85:792c]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3B6E84AC2D; Mon, 23 Jul 2012 17:57:47 +0400 (MSK) Date: Mon, 23 Jul 2012 17:57:44 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1468023399.20120723175744@serebryakov.spb.ru> To: Adrian Chadd In-Reply-To: References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> <802688919.20120709140808@serebryakov.spb.ru> <1966637204.20120713194935@serebryakov.spb.ru> <5862675.20120713203432@serebryakov.spb.ru> <7750188.20120716011053@serebryakov.spb.ru> <1214412854.20120722020752@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org 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: Mon, 23 Jul 2012 13:57:56 -0000 Hello, Adrian. You wrote 22 =D0=B8=D1=8E=D0=BB=D1=8F 2012 =D0=B3., 2:10:42: >> AC> Hm. With debuggimg it works, but turning it off causes timeouts? >> I'll turn it off tomorrow and will see AC> Thanks. If that's the case, it's quite likely a timing / race AC> condition bug and even your debugging logs as they are will be very AC> helpful. Again (without debug): ath0: ath_tx_tid_bar_unsuspend: bar_tx=3D0, bar_wait=3D0: ? ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: device timeout ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: addbaw=3D0, dobaw= =3D0, seqno=3D3113, retry=3D0 ath0: ath_tx_tid_drain: node 0xc404b000: bf=3D0xc34fda60: tid txq_depth=3D5= 03 hwq_depth=3D0, bar_wait=3D0 ath0: ath_tx_tid_drain: node 0xc404b000: tid 0: txq_depth=3D1, txq_aggr_dep= th=3D0, sched=3D0, paused=3D-1, hwq_depth=3D0, incomp=3D0, baw_head=3D111, = baw_tail=3D111 txa_start=3D3113, ni_txseqs=3D5107 FRDS 00:0c:42:64:69:92->70:d4:f2:ad:6a:26(00:0c:42:64:69:92) data QoS [TID = 0] WEP [IV 29 0c 00 00 00 00 KID 0] 0M 8862 0000 70d4 f2ad 6a26 000c 4264 6992 000c 4264 6992 90c2 0000 0101 290c= 0020 0000 0000 aaaa 0300 0000 0800 ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) ath0: stuck beacon; resetting (bmiss count 4) --=20 // Black Lion AKA Lev Serebryakov