From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 29 11:39:40 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 C26DA10656AB for ; Sun, 29 Jul 2012 11:39:40 +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 6C4DA8FC1F for ; Sun, 29 Jul 2012 11:39:40 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:9db0:4615:f8f5:e1a7]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A421B4AC2D; Sun, 29 Jul 2012 15:39:38 +0400 (MSK) Date: Sun, 29 Jul 2012 15:39:30 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <402841776.20120729153930@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> <1468023399.20120723175744@serebryakov.spb.ru> <978320748.20120729145152@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: Sun, 29 Jul 2012 11:39:40 -0000 Hello, Adrian. You wrote 29 =D0=B8=D1=8E=D0=BB=D1=8F 2012 =D0=B3., 15:23:30: AC> I saw, thanks. AC> Please enable reset debugging too - sysctl dev.ath.X.debug=3D0x20. Done :) I'll post new debug messages as soon as they'll appear. BTW, I've tried association debugging and got a TONS of such messages when client (Blackberry PlayBook) goes to sleep (but it is still associated): Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x11 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x13 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x11 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x13 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x11 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x13 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x11 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x13 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x11 Jul 29 15:29:05 gateway kernel: wlan0: [00:0c:42:64:69:92] HT bss occupancy= change: 1 sta, 1 ht, 0 ht40, non-HT sta present, HT protmode now 0x13 I've turned assotiation debugging off (and posted folloup to PR). AC> Jul 27 04:24:09 gateway kernel: ath0: ath_bar_response: called; AC> tap=3D0xc48c32b8, atid=3D0xc48c4df4, txa_tid=3D0, atid->tid=3D0, status= =3D1, AC> attempts=3D50 AC> Jul 27 04:24:09 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: AC> tid=3D0xc48c4df4, called AC> Jul 27 04:24:09 gateway kernel: ath0: ath_bar_response: called; AC> tap=3D0xc48c32b8, atid=3D0xc48c4df4, txa_tid=3D0, atid->tid=3D0, status= =3D1, AC> attempts=3D50 AC> Jul 27 04:24:09 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: AC> tid=3D0xc48c4df4, called AC> Jul 27 04:24:09 gateway kernel: ath0: ath_tx_tid_bar_unsuspend: AC> bar_tx=3D0, bar_wait=3D0: ? AC> That's very odd. I wonder if I broke that specific handling @ attempt= =3D50. As side note: I'm sure, that client was sleeping at this time, as I was sleeping for sure :) --=20 // Black Lion AKA Lev Serebryakov