Date: Sun, 14 Dec 2014 18:23:14 +0100 From: Thomas Zander <riggs@freebsd.org> To: Adrian Chadd <adrian@freebsd.org> Cc: Danilo Egea Gondolfo <daniloegea@yahoo.com.br>, FreeBSD Stable Mailing List <freebsd-stable@freebsd.org> Subject: Re: ath(4) device timeout -> reboot necessary Message-ID: <CAFU734y2_nZKr0VunKNfOTE8K6qUR_bgXTckoeaj4G-4u1_0tg@mail.gmail.com> In-Reply-To: <CAFU734yUsBy8FXyS2C9%2BzUXQLHQhhgMFrzTuSC5=D36A-8EbTw@mail.gmail.com> References: <20141122171734.GA4600@marvin2011.fritz.box> <5470C695.3040204@yahoo.com.br> <CAJ-Vmo=wUr%2BCTJA7zkANR3LAaDSYOW3eBVNwFK8xt22UBGOCdw@mail.gmail.com> <CAFU734yUsBy8FXyS2C9%2BzUXQLHQhhgMFrzTuSC5=D36A-8EbTw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 November 2014 at 13:23, Thomas Zander <riggs@freebsd.org> wrote: > On 22 November 2014 at 19:11, Adrian Chadd <adrian@freebsd.org> wrote: > >> Try setting >> sysctl dev.ath.0.hal.force_full_reset=1 > > Thanks Adrian. I put this into sysctl.conf and observe the effects > over the next weeks. I made the following observations in the past two weeks regarding this sysctl: - Reboots are not strictly necessary after an ath0 device timeout to get wifi to reconnect, as you expected, - If a device timeout has happend once, it is a virtual certainty to get the next one within 2 hours. This continues until the next reboot. So *something* might not get reset fully Any ideas? Best regards Riggs
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFU734y2_nZKr0VunKNfOTE8K6qUR_bgXTckoeaj4G-4u1_0tg>