From owner-freebsd-arm@freebsd.org  Sat Aug 25 15:31:46 2018
Return-Path: <owner-freebsd-arm@freebsd.org>
Delivered-To: freebsd-arm@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DA69108DD9A
 for <freebsd-arm@mailman.ysv.freebsd.org>;
 Sat, 25 Aug 2018 15:31:46 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org
 [54.200.247.200])
 (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 1F89375429
 for <freebsd-arm@freebsd.org>; Sat, 25 Aug 2018 15:31:46 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-RoutePath: aGlwcGll
X-MHO-User: f87e433a-a87b-11e8-93fa-f3ebd9db2b94
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 67.177.211.60
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [67.177.211.60])
 by outbound1.ore.mailhop.org (Halon) with ESMTPSA
 id f87e433a-a87b-11e8-93fa-f3ebd9db2b94;
 Sat, 25 Aug 2018 15:31:44 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id w7PFVhua003318;
 Sat, 25 Aug 2018 09:31:43 -0600 (MDT) (envelope-from ian@freebsd.org)
Message-ID: <1535211103.1488.47.camel@freebsd.org>
Subject: Re: FBS-12.0-APLHA, messages running portsnap
From: Ian Lepore <ian@freebsd.org>
To: Nicola Mingotti <nmingotti@gmail.com>, "freebsd-arm@freebsd.org"
 <freebsd-arm@freebsd.org>
Date: Sat, 25 Aug 2018 09:31:43 -0600
In-Reply-To: <c5920410-0bfd-1770-510c-d1b09fc348ee@gmail.com>
References: <c5920410-0bfd-1770-510c-d1b09fc348ee@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Aug 2018 15:31:46 -0000

On Sat, 2018-08-25 at 17:15 +0200, Nicola Mingotti wrote:
> Hi,
> 
> I am doing some tests with: 
> FreeBSD-12.0-ALPHA1-arm-armv7-BEAGLEBONE-20180810-r337557.img
> 
> Lunching :
> #> portsnap fetch
> 
> I get these messages on the serial console, I can not understand what 
> they mean,
> can I ignore them or are they important ?
> ---------------------
>   1st 0xc33c0af0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3916
>   2nd 0xd365e000 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:289
> stack backtrace:
> lock order reversal:
>   1st 0xd406e034 ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2572
>   2nd 0xc33c0af0 bufwait (bufwait) @ /usr/src/sys/ufs/ffs/ffs_vnops.c:282
>   3rd 0xd40ce84c ufs (ufs) @ /usr/src/sys/kern/vfs_subr.c:2572
> stack backtrace:
> --------------------
> 
> bye
> Nicola
> 
> 
> 

These are lock order reversal (LOR) warnings. While a LOR is a
potential deadlock, these particular instances are well-known and don't
cause any problems, so you can ignore them. Unfortunately, the
mechanisms that detect and reports these situations make it hard to
turn off the few specific places where the situation is known to be
harmless.

-- Ian