From owner-freebsd-current@FreeBSD.ORG Sun Feb 22 18:54:57 2015 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D2AB0C5A for ; Sun, 22 Feb 2015 18:54:57 +0000 (UTC) Received: from mail.ignoranthack.me (ignoranthack.me [199.102.79.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AFDE675A for ; Sun, 22 Feb 2015 18:54:57 +0000 (UTC) Received: from [192.168.200.212] (unknown [50.136.155.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: sbruno@ignoranthack.me) by mail.ignoranthack.me (Postfix) with ESMTPSA id 3E1DB192A3B; Sun, 22 Feb 2015 18:54:55 +0000 (UTC) Message-ID: <54EA25FE.60401@ignoranthack.me> Date: Sun, 22 Feb 2015 10:54:54 -0800 From: Sean Bruno Reply-To: sbruno@freebsd.org User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: Konstantin Belousov Subject: Re: panic on application core dump? References: <54E8EA2A.7020904@ignoranthack.me> <20150221211712.GG74514@kib.kiev.ua> <54EA1325.6070009@ignoranthack.me> <20150222180425.GJ74514@kib.kiev.ua> <54EA241D.6020606@ignoranthack.me> <20150222185352.GL74514@kib.kiev.ua> In-Reply-To: <20150222185352.GL74514@kib.kiev.ua> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: FreeBSD current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Feb 2015 18:54:57 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 02/22/15 10:53, Konstantin Belousov wrote: > On Sun, Feb 22, 2015 at 10:46:53AM -0800, Sean Bruno wrote: >> Hmm ... looks unrelated to signals (maybe). This looks like a >> common ZFS deadlock that is yet undiagnosed. I do not have a >> show alllocks command available in db> . I will show each lock >> information below: > Add witness. > >> >> db> show lockedvnods Locked vnodes >> >> 0xfffff801141a6588: tag zfs, type VDIR usecount 19, writecount 0, >> refcount 20 mountedhere 0 flags (VV_ROOT|VI_ACTIVE) v_object >> 0xfffff80079be4500 ref 0 pages 0 cleanbuf 0 dirtybuf 0 lock type >> zfs: EXCL by thread 0xfffff801ca10c4a0 (pid 75907, sh, tid >> 101262) with exclusive waiters pending > Without backtraces of the acquisition, it is not useful. You need > DEBUG_VFS_LOCKS for this. > > Thank you. I will do so and restart my non-determinstic test and see what I can find. sean -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJU6iX7XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRCQUFENDYzMkU3MTIxREU4RDIwOTk3REQx MjAxRUZDQTFFNzI3RTY0AAoJEBIB78oecn5kw+wH/3lcy7AJOvOu3cIQilxmfovt rplhxp/t5lYVRS76FyBM9FekYtLZhK3uFyL2ZdEYNh11hjuitFXfaoADrZgyXvzI SxJhjKy3Zhqt8reeLvKM9MhhdyNWNrbufhB4mqsmamtCDKh7jQ7EDIRsES9EzBon brzZObtFTCNZgulQiTAWZZKNz0NH9hyJoPw9yHfXNTgVyLCkOBDDfCLLthiMd6l0 0RITV3CZ3W3RJvFWAnYU7iWaLWATEzOzPLhegRLG5G2P1khCxsYOH7+1BbOpF86N PCg49DuEsjhlhJrbX+CqRDb1oGI0/Gt+HE/RGkoCj77Ow98jyIH3Jg5vmhBJYN0= =2Fjt -----END PGP SIGNATURE-----