Date: Fri, 26 Apr 2013 14:17:25 -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-Vmom5kKL5YZEXvkqiWWWLY69PJPHES7Np=byr%2Bc7NjH_u-Q@mail.gmail.com> In-Reply-To: <1091133497.20130427011423@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> <766430457.20130426125828@serebryakov.spb.ru> <CAJ-Vmo=kGvPmejzsMw_T5MtL0HyLGa9kNnX_tt0PnFo6M4g37A@mail.gmail.com> <1091133497.20130427011423@serebryakov.spb.ru>
index | next in thread | previous in thread | raw e-mail
On 26 April 2013 14:14, Lev Serebryakov <lev@freebsd.org> wrote: > Hello, Adrian. > You wrote 26 апреля 2013 г., 18:56:57: > > AC> And please cc -wireless with your debugging results :) > Ok. > It is interesting how throughput is not connected to rate after > these problems. Now I have client at stable 270M rate with RSSI ~28, > and only 15-20Mbit/s of UDP traffic AP->Client... :( > > It looks like throughput is bad after card reset without reboot... > But no ath_bar_suspend! > > Yes, after full reboot throughput is osscilate between 65 and > 120Mbit/s! But with bar_suspsends! > > Maybe, it is coincidence, but I npotice this for second time... All kinds of reasons for this behaviour. We'll look into it after we nail down why the TX queue is stalling. adrianhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmom5kKL5YZEXvkqiWWWLY69PJPHES7Np=byr%2Bc7NjH_u-Q>