Date: Sun, 11 Mar 2012 20:20:11 GMT From: Joel Dahl <joel@freebsd.org> To: freebsd-wireless@FreeBSD.org Subject: Re: kern/163318: [ath] ath(4) stops working Message-ID: <201203112020.q2BKKBIF010768@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/163318; it has been noted by GNATS. From: Joel Dahl <joel@freebsd.org> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: bug-followup@freebsd.org Subject: Re: kern/163318: [ath] ath(4) stops working Date: Sun, 11 Mar 2012 21:13:46 +0100 On 11-03-2012 13:07, Adrian Chadd wrote: > Hi! > > On 11 March 2012 13:01, Joel Dahl <joel@freebsd.org> wrote: > > Some news... > > > > I updated from a Jan 18 CURRENT to a Feb 19 CURRENT some time ago and the > > issue was gone. Adrian asked me to try to track down the revision that fixed > > the problem, and that's what I've been doing for the last two weeks. > > Sweet! > > > > Revision 231852 does not survive for very long. It dies as usual. I haven't > > been able to make any revision before 231852 survive longer than 8 hours. > > > > Revision 231854 has survived my 12 hour testing period 3 times and I haven't > > been able to crash any revision after 231854. > > > > Adrian, your commit to the ath driver (231854) seems to fix my ath problems. > > Does that make sense to you? > > Nope. That just started shifting around locks. Can you please try > 231852 with the debugging patch I threw you (that patched > ieee80211_scan.c) and see if it complains? Sure, I'll try 231852 + your patch. > If that patch fixed anything, it just delayed things enough to hide > what's going on... I see. Hiding a problem is not equal to fixing it. :-) -- Joel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203112020.q2BKKBIF010768>