Date: Tue, 5 Apr 2016 16:48:21 +0300 From: Aleksander Alekseev <afiskon@devzen.ru> To: Mark Johnston <markj@FreeBSD.org> Cc: Adrian Chadd <adrian.chadd@gmail.com>, Hans Petter Selasky <hps@selasky.org>, Andriy Voskoboinyk <s3erios@gmail.com>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: I need a little help in fixing `exclusive sleep mutex urtwn0_com_lock` in CURRENT Message-ID: <20160405164821.0158e0eb@fujitsu> In-Reply-To: <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com> References: <20160330123048.3361a9e4@fujitsu> <op.ye4x9fosiew4ia@localhost> <56FBBC62.6040905@selasky.org> <CAJ-Vmon=s-uKMhzgRm--DttXJ8_x_cAKnpALu4UeLOdQQ9nXpw@mail.gmail.com> <20160331204256.5cb1fdaf@portege> <20160331180333.GA25235@wkstn-mjohnston.west.isilon.com> <20160401002337.36700d9b@portege> <20160331225902.GA32570@wkstn-mjohnston.west.isilon.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> Looking at your original post, the problem isn't related to a missing > unlock. The attempt to lock the ieee80211com is triggering a fault, > presumably because it was freed while the lock was dropped. So DTrace > isn't going to help much here. Yeah... on second though I don't think I'm experienced enough in kernel development to fix this, at least quickly. So if anyone knows how to do it please do. I should probably create a ticket in Bugzilla on this, right? -- Best regards, Aleksander Alekseev http://eax.me/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160405164821.0158e0eb>