Date: Fri, 26 Apr 2013 14:34:24 -0700 From: Adrian Chadd <adrian@freebsd.org> To: lev@freebsd.org Cc: freebsd-wireless@freebsd.org Subject: Re: New hardware, old problem: stuck beacon when here is WiFi traffic Message-ID: <CAJ-Vmonxz3spCYeM5b3ijBgnM6wfjTa%2Bv5j8pbnX%2B-_Sg4hSGw@mail.gmail.com> In-Reply-To: <1977535276.20130427012851@serebryakov.spb.ru> References: <2810538978.20130423164137@serebryakov.spb.ru> <CAJ-Vmom4UDoz7EgdnVeQ%2BALuFFXkH9t_Uj7=FwL77S5rKfUD1g@mail.gmail.com> <1813905823.20130423184528@serebryakov.spb.ru> <CAJ-VmomhRaKODxis09MjAhUbAUOw%2B6jWBY48JpZR_JgfZZLKcQ@mail.gmail.com> <184105677.20130424002002@serebryakov.spb.ru> <CAJ-VmokVmHDXwE7S5koSqtFjPXQ_VUPhj8gfMruDM2k-DyUMPw@mail.gmail.com> <1936997795.20130424003555@serebryakov.spb.ru> <CAJ-Vmokx2QhcjcsgA-_kqjX63Vu4CLk7HkuyALautbnzp61ywQ@mail.gmail.com> <886711115.20130424004702@serebryakov.spb.ru> <CAJ-VmoksSTBC7jmC-_hvBeJFSD0k28HoZodaWdHm0AF0d1yZJg@mail.gmail.com> <6010292503.20130426001447@serebryakov.spb.ru> <CAJ-VmomUsPgHTVGaKHZ_YE%2Bu1ZOjGqrVfh2uYmvOs6gKmhnxOw@mail.gmail.com> <CAJ-VmokZBbmHbruKJV-8kvTyOTsiq5_XHnfqUYo3vO68872Q=w@mail.gmail.com> <99510815.20130426122508@serebryakov.spb.ru> <CAJ-VmoktRPbnDRbRuwA4i8w50kExs2pwD4yBawL6iOz7F4Bknw@mail.gmail.com> <CAJ-VmonCao99MOrm97tQS_f1xS9tieQfg-nQUB4APWVmdJJUBg@mail.gmail.com> <1977535276.20130427012851@serebryakov.spb.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
You're not doing something like leaving bgscan enabled, or not defining a channel up front? There's a lot of resets hre. adrian On 26 April 2013 14:28, Lev Serebryakov <lev@freebsd.org> wrote: > Hello, Adrian. > You wrote 26 =D0=B0=D0=BF=D1=80=D0=B5=D0=BB=D1=8F 2013 =D0=B3., 12:51:17: > >>> Wait. sysctl dev.ath.0.forcebstuck=3D1 didn't fix it? > Ok, several such commands helps without down/up of interface. > Log attached: a lot of traffic, several BAR retransmits, interface > hangs, several "forcebstuck=3D1", client could associate again and > interface passes traffic. > > Maybe, there were too many "forcebstuck=3D1", but one ro two doesn't > fix situation for sure, client was not able to assotate after first > two of them. > > -- > // 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-Vmonxz3spCYeM5b3ijBgnM6wfjTa%2Bv5j8pbnX%2B-_Sg4hSGw>