Date: Wed, 30 Mar 2016 11:47:44 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Aleksander Alekseev <mail@eax.me>, freebsd-hackers@freebsd.org, Adrian Chadd <adrian@freebsd.org> Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <56FBA0C0.8030809@selasky.org> In-Reply-To: <20160330123048.3361a9e4@fujitsu> References: <20160330123048.3361a9e4@fujitsu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/30/16 11:30, Aleksander Alekseev wrote: > So as I understand some code acquired a mutex and didn't release it. > And naturally it has something to do with USB. Now how can I figure out > what code acquired this lock? Best approach I can think of currently is > to find all places where this lock is accessed and add a debug logging. > But perhaps there is a better way? Looks like the USB driver or WLAN stack needs to drain this taskqueue before detaching. Maybe Adrian knows? --HPS
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?56FBA0C0.8030809>