From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 9 09:31:08 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 EC0EB1065672; Mon, 9 Jul 2012 09:31:08 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-yw0-f54.google.com (mail-yw0-f54.google.com [209.85.213.54]) by mx1.freebsd.org (Postfix) with ESMTP id 910718FC1D; Mon, 9 Jul 2012 09:31:08 +0000 (UTC) Received: by yhfs35 with SMTP id s35so5121382yhf.13 for ; Mon, 09 Jul 2012 02:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=LuhJboOw1Ttx24Dc44qH5ZjcO2Ov8j+HIymAUjBd2eA=; b=GV/o0RMKvi6nr+pDZ6Ze4zqcHdQ/Y3f5FzwpicerbDLyO7UqHMHCGfjXc4Hyz/nnnH nkWS8EXViJmebZu3lVzS7N+RlQ0Wd+4J2+rQFh1dLd0s4h8QN4wIuaLDpPlBv02bzIfu Bgur81SbJLBl7GM63zNhUgLgBY9s2qkkw7I9VVzUI+P238LZy1ncJl/FxnSncJ3STA3m ia/20jwU2uav09zdQQ/PKd3+BIn3b4pMTePzV1YRyIg5SuVL1OHTkbSc4s0/1K6NdMgb hnL175pFAVZbDu6tq+JcRn45/TwTP9omv1NZENGNDeFTIKfIM32DYDAEUyz2WnDQZZXU CMfw== MIME-Version: 1.0 Received: by 10.66.73.69 with SMTP id j5mr57586279pav.8.1341826267429; Mon, 09 Jul 2012 02:31:07 -0700 (PDT) Received: by 10.68.195.102 with HTTP; Mon, 9 Jul 2012 02:31:07 -0700 (PDT) In-Reply-To: <1252921508.20120709132351@serebryakov.spb.ru> References: <298155894.20120709002844@serebryakov.spb.ru> <1491344515.20120709013411@serebryakov.spb.ru> <1252921508.20120709132351@serebryakov.spb.ru> Date: Mon, 9 Jul 2012 02:31:07 -0700 Message-ID: From: Adrian Chadd To: lev@freebsd.org 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 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, 09 Jul 2012 09:31:09 -0000 Hm, are you running the latest -HEAD? I'm sure I found/fixed the bug where BAR handling wasn't being refcounted correctly in some corner conditions, leading to a queue that stayed stuck/paused. Adrian On 9 July 2012 02:23, Lev Serebryakov wrote: > Hello, Adrian. > You wrote 9 =D0=B8=D1=8E=D0=BB=D1=8F 2012 =D0=B3., 4:06:52: > > AC> ALQ is the queue used by KTR and others to log data. > AC> Look at ieee80211_alq.c and see. > AC> We just need to craft some probes in the ath TX path to log frames an= d > AC> completion. Then we can try to figure out whats causing your TX to st= all. > I see. > > Latest messages about ath0: > > Jul 9 01:51:44 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: bar_tx=3D= 0, bar_wait=3D0: ? > Jul 9 01:54:35 gateway kernel: ath0: device timeout > Jul 9 01:55:07 gateway kernel: ath0: device timeout > Jul 9 01:55:22 gateway kernel: ath0: device timeout > Jul 9 02:09:58 gateway kernel: ath0: device timeout > Jul 9 04:30:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4efb000: = bf=3D0xc3514fe0: addbaw=3D0, dobaw=3D0, seqno=3D1607, retry=3D0 > Jul 9 04:30:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4efb000: = bf=3D0xc3514fe0: tid txq_depth=3D330 hwq_depth=3D0, bar_wait=3D0 > Jul 9 04:30:54 gateway kernel: ath0: ath_tx_tid_drain: node 0xc4efb000: = tid 0: txq_depth=3D1, txq_aggr_depth=3D0, sched=3D0, paused=3D-1, hwq_depth= =3D0, incomp=3D0, baw_head=3D98, baw_tail=3D98 txa_start=3D1607, ni_txseqs= =3D1937 > > -- > // Black Lion AKA Lev Serebryakov >