From owner-freebsd-current@freebsd.org  Sun May 15 07:44:07 2016
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 3A2BBB3CABA
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 15 May 2016 07:44:07 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (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 006651E2B
 for <freebsd-current@freebsd.org>; Sun, 15 May 2016 07:44:06 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.87 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1b1qia-000Izp-DF; Sun, 15 May 2016 09:44:04 +0200
Date: Sun, 15 May 2016 09:44:04 +0200
From: Kurt Jaeger <lists@opsec.eu>
To: Will Brokenbourgh <will_brokenbourgh@yahoo.com>
Cc: freebsd-current@freebsd.org
Subject: Re: Lock order reversal errors during boot
Message-ID: <20160515074404.GF15034@home.opsec.eu>
References: <6b965a16-a6c7-a063-3c2a-7c577c2f9b56@yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6b965a16-a6c7-a063-3c2a-7c577c2f9b56@yahoo.com>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2016 07:44:07 -0000

Hi!

> I am seeing 'lock order reversal' errors during boot on 11-CURRENT - 
> r298793.  A sample error:
> 
> lock order reversal:
>   1st 0xfffff8011280d068 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
>   2nd 0xfffffe01ca539400 bufwait (bufwait) @ 
> /usr/src/sys/ufs/ffs/ffs_vnops.c:263
>   3rd 0xfffff80112a23b78 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2498
> stack backtrace:
> #0 0xffffffff80a94bf0 at witness_debugger+0x70
> #1 0xffffffff80a94ae4 at witness_checkorder+0xe54
> #2 0xffffffff80a0fdd6 at __lockmgr_args+0x4d6
> #3 0xffffffff80ce9626 at ffs_lock+0xa6
> [...snip...]
> 
> I'm not sure if this is even something I should report, but better safe 
> than sorry, yes?

Yes, and there's even a page to compare your LOR against other ones:

http://sources.zabbadoz.net/freebsd/lor.html

Can you try if you find your LOR there ? If not, can you add it
to that page ?

-- 
pi@opsec.eu            +49 171 3101372                         4 years to go !