From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 03:11:14 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08C92620 for ; Wed, 11 Mar 2015 03:11:14 +0000 (UTC) Received: from relay.mailchannels.net (tkt-001-i373.relay.mailchannels.net [174.136.5.175]) by mx1.freebsd.org (Postfix) with ESMTP id 2F252EE for ; Wed, 11 Mar 2015 03:11:12 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (ip-10-213-14-133.us-west-2.compute.internal [10.213.14.133]) by relay.mailchannels.net (Postfix) with ESMTPA id 781F960167; Wed, 11 Mar 2015 02:52:21 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp7.ore.mailhop.org (smtp7.ore.mailhop.org [10.21.145.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Wed, 11 Mar 2015 02:52:21 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426042341566:4219252017 X-MC-Ingress-Time: 1426042341566 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp7.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YVWku-0004QZ-SD; Wed, 11 Mar 2015 02:52:21 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t2B2qGrd010669; Tue, 10 Mar 2015 20:52:16 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX18gxxrfTfPRIge1CxpmkQXE Message-ID: <1426042336.33324.32.camel@freebsd.org> Subject: Re: BBB freebsd-current backtrace. why? From: Ian Lepore To: Jason Birch Date: Tue, 10 Mar 2015 20:52:16 -0600 In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Mar 2015 03:11:14 -0000 On Wed, 2015-03-11 at 13:05 +1100, Jason Birch wrote: > On Wed, Mar 11, 2015 at 11:35 AM, jungle Boogie > wrote: > > > Hello All, > > > > Brand new download and install of -current on my beagle bone black and > > getting below backtrace, but the portsnap extract is continuing. If > > this is how it was on last weeks image, the backtrace will randomly > > print something similar to what's below even when the BBB is inactive. > > > > Downloaded from: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/arm/armv6/ISO-IMAGES/11.0/ > > > > Is this expected? > > > > root@beaglebone:~ # portsnap fetch extract update > > Looking up portsnap.FreeBSD.org mirrors... 7 mirrors found. > > Fetching public key from isc.portsnap.freebsd.org... done. > > Fetching snapshot tag from isc.portsnap.freebsd.org... done. > > Fetching snapshot metadata... done. > > Fetching snapshot generated at Tue Mar 10 00:05:13 UTC 2015: > > 248798a3bfb5e11c4a642a6254d9ec1573982894936270100% of 71 MB 2297 kBps > > 00m32s > > Extracting snapshot... lock order reversal: > > 1st 0xcd228ba0 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3097 > > 2nd 0xc2fa0e00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:285 > > KDB: stack backtrace: > > > > They're lock order reversals, as enabled by the WITNESS kernel option. You > probably don't need to worry, but it's helpful to check if they've been > reported and, if not, report them. > > You might be running into this one: > http://sources.zabbadoz.net/freebsd/lor/261.html That website hasn't been updated for years. The sad truth is that you can report LORs all day long and nobody seems to care anymore. But if you try to turn it off by default in the kernel configs you get yelled at about how important it is. Bah. -- Ian