From owner-freebsd-hackers@freebsd.org  Tue Apr  5 14:04:02 2016
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 29045B03C72
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Tue,  5 Apr 2016 14:04:02 +0000 (UTC)
 (envelope-from afiskon@devzen.ru)
Received: from relay14.nicmail.ru (relay14.nicmail.ru [195.208.3.99])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D05291B81;
 Tue,  5 Apr 2016 14:04:00 +0000 (UTC)
 (envelope-from afiskon@devzen.ru)
Received: from [109.70.25.187] (port=43774 helo=fujitsu)
 by f19.mail.nic.ru with esmtp (Exim 5.55)
 (envelope-from <afiskon@devzen.ru>)
 id 1anRLf-000EBb-Bp; Tue, 05 Apr 2016 16:48:52 +0300
Received: from [93.174.131.138] (account afiskon@devzen.ru HELO fujitsu)
 by proxy08.mail.nic.ru (Exim 5.55)
 with id 1anRLf-0002zG-K9; Tue, 05 Apr 2016 16:48:51 +0300
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>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 14:04:02 -0000

> 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/