Date: Sat, 21 Dec 2013 21:49:05 -0500 From: Glen Barber <gjb@FreeBSD.org> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-wireless@freebsd.org Subject: Re: "disappearing" ath(4) Message-ID: <20131222024905.GK1730@glenbarber.us> In-Reply-To: <CAJ-VmokT88Kr4pEvcLBB1fYMovSo9vKNjAhbrLF3xzSF%2BZrOUg@mail.gmail.com> References: <20131221023558.GJ3148@glenbarber.us> <20131221023924.GK3148@glenbarber.us> <CAJ-VmonAmPdxpck21jaATctb3zA8pt%2BaTex46uQGRF=O695Hrw@mail.gmail.com> <20131222023331.GJ1730@glenbarber.us> <CAJ-VmokT88Kr4pEvcLBB1fYMovSo9vKNjAhbrLF3xzSF%2BZrOUg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--F55Y67F01HNW3AgB Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I doubt lagg(4) is the issue. I've been doing that evil for years. I'll kill the *_cs_lowest, and see if that changes anything over the next few days. I'm 200% certain lagg(4) is not a factor, but if it continues, I'll disable that for S&G. Glen On Sat, Dec 21, 2013 at 06:44:16PM -0800, Adrian Chadd wrote: > Yeah. Try killing those. Leave it at c1 and no lagg. C2 and later may be > triggering some weird stuff. >=20 > Adrian > On Dec 21, 2013 8:33 PM, "Glen Barber" <gjb@freebsd.org> wrote: >=20 > > 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=3D"C2" > > economy_cx_lowest=3D"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 > > > > --F55Y67F01HNW3AgB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJStlMhAAoJELls3eqvi17Qb5gQAIbTlopwVRUy0GH9OU81aWY8 H4FMwKfl2f1CL8VUC8aJqZ4H/UmUG+zwzB5rl0x22RFQGw8hfKEgHgeIsKErRIQO OPyqR9M4ajKw5JGiPfV8w5mTCeRJ9QYE0+GI+7lX0+YuLIq3W4rOTzGLG355WE+E tjOSmEpKXKjlSf5RLsfsx9cChwhTQt1y0uRRqYHNyZt173CdwLRg9TSI6IPMITnN BBUnvs8yDgb55f3/jR+62ktnVC4jcKCarIRvuKYT77eYS09jGfGPS6LTzGSSkbjv zpSjAgojD9faJRdTQIFaDHj1seQpqXgS+4YoWIx+vNmL2ifOIXSZHcUtHEwIWI4U n9PCQUy6vajuCVeM98sVNX4RfVe6u/f+RiBw5ba0XRoCMxWqqeiVxwvSMqNVpZUN 287/1pROs2IqQHaD4IWyEBdPqIgen6YjMYRVLGUjPq1V8FNcSYvqJ5JO6qo8elDz xRcCj7ktreAkGVpo0jvd6RJsjTMKyw+4GDWYDzNjI2rfMHqeNmMxz1sS1OYiqBoS uQbWf/oCD9fDXUt0AS2kP92yp00+l5D/eWxK6urh24sQqn7FUhipkMuttEbVE7ky Q191fauGtZpZXpZyQoxwJ3LpuquE/9TQBHYXYB2uG7op4v0tviTKds+KX4RgIXAA GlK9gfWfir0i1dIAOTbM =+EVo -----END PGP SIGNATURE----- --F55Y67F01HNW3AgB--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20131222024905.GK1730>