Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Jul 2012 17:23:34 -0700
From:      Adrian Chadd <adrian.chadd@gmail.com>
To:        lev@freebsd.org
Cc:        wireless@freebsd.org
Subject:   Re: ath0: device timeout with 802.11n client
Message-ID:  <CAJ-VmomwM2o0c40eajzvg7iEHZs9Rs0cqdO3ua-tcEmgy4T=JA@mail.gmail.com>
In-Reply-To: <402841776.20120729153930@serebryakov.spb.ru>
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> <1252921508.20120709132351@serebryakov.spb.ru> <CAJ-VmonDzZEBubrbTxMbj32X024orbgbRHFz7FpchrHuJigbkg@mail.gmail.com> <802688919.20120709140808@serebryakov.spb.ru> <CAJ-Vmom-s=4sVZ-Y1VJLXMouz3n48PLSdqHJ8ghH6iXyjFUaTg@mail.gmail.com> <1966637204.20120713194935@serebryakov.spb.ru> <CAJ-VmomBznMGZWyfaqibT9HXPGr1ORNaSG838aLPDeY%2B0smoew@mail.gmail.com> <5862675.20120713203432@serebryakov.spb.ru> <CAJ-Vmok%2BtQULYHy3=pqgHTfK-oEfBNV7OMugzOuAosC_Msha9g@mail.gmail.com> <CAJ-Vmon2-1d7dg%2BeDDz4Dpnq_FdW_U24=xdW5yOKKg=NeUsveQ@mail.gmail.com> <7750188.20120716011053@serebryakov.spb.ru> <CAJ-Vmom70sNoRKdVPSH3Aqxi6r=z7BDK6x_ydTEtygunYrLrVA@mail.gmail.com> <CAJ-Vmo=DOPr9PKOfcF4%2BfHXYzSbDEmrTt4iK9NP4UL=akycW5g@mail.gmail.com> <1468023399.20120723175744@serebryakov.spb.ru> <CAJ-VmonOSQ8OyJdp=KAW4nR0RNEnHAVKCeuNWHPzgHF31SHcSg@mail.gmail.com> <CAJ-VmonCzocGFeue1MR%2BtNn2S8gvo8JPRwWNYps=SkrTJqUn%2Bg@mail.gmail.com> <978320748.20120729145152@serebryakov.spb.ru> <CAJ-Vmomv9wi2PdjczY6AYOkFbctWzrd6m3CsCY9XRQy5sMX4BQ@mail.gmail.com> <402841776.20120729153930@serebryakov.spb.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
Hm, I've seen that bss occupancy change spam.

There's another project for someone to figure out. Why is it flipping
so quickly?


On 29 July 2012 04:39, Lev Serebryakov <lev@freebsd.org> wrote:
> 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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 occupan=
cy 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, stat=
us=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, stat=
us=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 :)
>
> --
> // 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?CAJ-VmomwM2o0c40eajzvg7iEHZs9Rs0cqdO3ua-tcEmgy4T=JA>