Date: Fri, 29 Jul 2016 13:42:43 -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-VmokctaK2kgE59C64ugUzwmsbhj5p24EJ126pyosqmwe=2w@mail.gmail.com> In-Reply-To: <762054A0-B628-4CD8-9F59-6B52CEB78481@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>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, What else is logged in dmesg when it happens? I've never had to restart hostapd or the interface, but it's quite possible you've found some situations with hung stations and that needs to be addressed. Thanks! -a On 29 July 2016 at 13:30, Andrew Stevenson <andrew@ugh.net.au> wrote: > > Well after a week of running 11 (BETA1 r303134) I think sadly its worse t= han 10. No more bf_next errors. Still lots of "ath0: stuck beacon; resettin= g (bmiss count 4)=E2=80=9D. The main thing though is the the clients drop o= f the network and can=E2=80=99t reattach. > > Sometimes restarting hostapd is all that is needed, though occasionally I= have to =E2=80=9Crestart" the interface (/etc/rc.d/netif restart wlan0). > > Happens usually once or twice a day. Is there anything I can do to help d= ebug? I tried to attach to hostapd with gdb last time but gdb had an intern= al error and killed the process. > > Thanks, > > Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokctaK2kgE59C64ugUzwmsbhj5p24EJ126pyosqmwe=2w>