Date: Mon, 30 Jul 2012 12:11:24 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: PseudoCylon <moonlightakkiy@yahoo.ca> Cc: freebsd-wireless@freebsd.org, Kim Culhan <w8hdkim@gmail.com> Subject: Re: ath lor Message-ID: <CAJ-VmonktzxboAcVhiJQipS58Wmr17Jyu8M3efgaBkkJRh5-XA@mail.gmail.com> In-Reply-To: <CAFZ_MYKgUkryy4parts3QahAyPA7FY9xUqC98_E7oFW%2BzarA8A@mail.gmail.com> References: <CAFZ_MYKgUkryy4parts3QahAyPA7FY9xUqC98_E7oFW%2BzarA8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Well, we really need to figure out exactly the code and locking paths that is causing these LORs. I don't have the time to figure it out just at the moment - I want to focus on bringing the AR93xx series NICs into FreeBSD in a clean, non-hacky method. I also don't really like at all how these locks are recursive, but fixing that is likely a very large effort. I'd like to tackle it but not quite right at the moment. So, let's list all the LORs that you're seeing and figure out the code paths, so we can correctly fix these issues. :) Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonktzxboAcVhiJQipS58Wmr17Jyu8M3efgaBkkJRh5-XA>