Date: Sat, 21 Dec 2013 18:44:16 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Glen Barber <gjb@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: "disappearing" ath(4) Message-ID: <CAJ-VmokT88Kr4pEvcLBB1fYMovSo9vKNjAhbrLF3xzSF%2BZrOUg@mail.gmail.com> In-Reply-To: <20131222023331.GJ1730@glenbarber.us> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> <CAJ-VmonAmPdxpck21jaATctb3zA8pt%2BaTex46uQGRF=O695Hrw@mail.gmail.com> <20131222023331.GJ1730@glenbarber.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Yeah. Try killing those. Leave it at c1 and no lagg. C2 and later may be triggering some weird stuff. Adrian On Dec 21, 2013 8:33 PM, "Glen Barber" <gjb@freebsd.org> wrote: > On Sat, Dec 21, 2013 at 08:17:32AM -0800, Adrian Chadd wrote: > > The second possibility is that it's asleep - and no, NIC reads aren't > > showing 0xdeadc0de, 0xdeadbeef, etc. So no, it's not that. > > > > I didn't think of this when you first mentioned it, but I recently added > this to rc.conf: > > performance_cx_lowest="C2" > economy_cx_lowest="C2" > > Another thing I failed to mention, is the ath(4) is part of lagg(4), > accompanied by alc(4). > > I'm half wondering if the *_cx_lowest is triggering something. The > other half wonders if lagg(4) triggers something funky. > > > He's also recently opened up his laptop and fiddled around. > > > > "Trust me, I'm an engineer!" > > > he's going off to do some more testing. > > > > "What can possibly go wrong?" > > Glen > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokT88Kr4pEvcLBB1fYMovSo9vKNjAhbrLF3xzSF%2BZrOUg>