Date: Mon, 9 Jul 2012 13:23:51 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: wireless@freebsd.org Subject: Re: ath0: device timeout with 802.11n client Message-ID: <1252921508.20120709132351@serebryakov.spb.ru> In-Reply-To: <CAJ-VmokFcHSx9bQtRMFFx5EGXE=P2Zj-omZ266nNfTVd-DELWw@mail.gmail.com> References: <298155894.20120709002844@serebryakov.spb.ru> <CAJ-VmomWfbTZG1z_iEDEXWmFTWSSfDpPJZ0iFFHOio8eGwuUhg@mail.gmail.com> <1491344515.20120709013411@serebryakov.spb.ru> <CAJ-VmokFcHSx9bQtRMFFx5EGXE=P2Zj-omZ266nNfTVd-DELWw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 and AC> completion. Then we can try to figure out whats causing your TX to stal= l. I see. Latest messages about ath0: Jul 9 01:51:44 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: bar_tx=3D0,= 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: ti= d 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 --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1252921508.20120709132351>