Date: Thu, 4 Aug 2016 00:50:20 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Andrew Stevenson <andrew@ugh.net.au> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org>, Willem@offermans.rompen.nl Subject: Re: bf_next not NULL! Message-ID: <CAJ-VmokbLnw75mWeQcB2WaPa8CeBXxckUzedW05jPAqAQ6YpcA@mail.gmail.com> In-Reply-To: <2E7BBB3B-2398-413B-BA8E-18CFB16AE4E1@ugh.net.au> References: <2DEF8DBE-1444-435C-B48C-FEAB71CA60E5@ugh.net.au> <20160716105843.GA5832@vpn.offrom.nl> <CAJ-VmomwtRwk8aNcCn3pKzbLspPHN0UKPC4J%2BdS0ebOvHom73g@mail.gmail.com> <A0ED3F72-21EF-4B97-BF4B-AA0AEA336958@ugh.net.au> <762054A0-B628-4CD8-9F59-6B52CEB78481@ugh.net.au> <CAJ-VmokctaK2kgE59C64ugUzwmsbhj5p24EJ126pyosqmwe=2w@mail.gmail.com> <CAJ-Vmo=4tGEE6Owuxtsc9g%2BM5hF%2BpXfq3n3=Txi7LnF0UHo2cQ@mail.gmail.com> <F90C8D26-19D6-4CD1-AFB0-789170678D5D@ugh.net.au> <CAJ-VmonpN_f%2Bp5rE_qNdhDBKsfr2-4xELLLa5HMwY7B6QbGviQ@mail.gmail.com> <09DD4206-6D68-4B03-A3F9-01512C2F866B@ugh.net.au> <CAJ-VmonXg1XAB-FeajcbQ2NG9e=oV3X-R%2BO%2BY92quNTckZgGEw@mail.gmail.com> <DFCDAD37-8EA2-4D5B-AC46-221050E9FD44@ugh.net.au> <CAJ-Vmo=Zeh-83C2B756JTviOAs6jhF07xa%2BOQ4dAQmmFwRGuLA@mail.gmail.com> <2E7BBB3B-2398-413B-BA8E-18CFB16AE4E1@ugh.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, Recompile with ATH_DEBUG, AH_DEBUG, ATH_DIAGAPI Thanks! -adrian On 4 August 2016 at 00:48, Andrew Stevenson <andrew@ugh.net.au> wrote: > > On 04 Aug 2016, at 00:41, Adrian Chadd <adrian.chadd@gmail.com> wrote: > >> ok. I'll go dig an ar9227 out of storage and set it up to see what's goi= ng on. >> >> please do this: >> >> sysctl dev.ath.0.hal.debug=3D0x18 >> >> then paste me the results from 'dmesg' over some period of time (eg >> between good/bad/good times.) > > OK I enabled this last night and this morning I find that the DHCP server= has stopped serving anything on the WIFI interface. Thats a new one. It mi= ght be a random bugs in the ISC DHCP server but I haven=E2=80=99t noticed i= t before and I have seen that rtadvd sometimes doesn=E2=80=99t cope with br= oken interfaces and requires a restart after they are fixed so maybe dhcpd = is similar. That would mean the sysctl loop had brought things back by itse= lf. DHCP didn=E2=80=99t log anything and seemed to be working over wired et= hernet. > > I restarted DHCP and everything seems normal. Pings are a bit variable bu= t no IP layer loss (e.g. best 1.6ms, avg 6.9ms, worst 15.3 ms for a ping fr= om a client to the base station). > > Nothing logged yet from ath0 other than "ath0: stuck beacon; resetting (b= miss count 0)=E2=80=9D (note 0 this time) logged approx every 4 minutes. Ev= ery 5th (approx) has a bmiss of 4). "ath0: device timeout=E2=80=9D appears = about once every 2 hours. > > I will keep checking and let you know. > > Thanks, > > Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokbLnw75mWeQcB2WaPa8CeBXxckUzedW05jPAqAQ6YpcA>