I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT

[Hans Petter Selasky]

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