From owner-freebsd-arm@FreeBSD.ORG Wed Mar 11 15:06:15 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 B357A12D for ; Wed, 11 Mar 2015 15:06:15 +0000 (UTC) Received: from relay.mailchannels.net (ar-005-i207.relay.mailchannels.net [162.253.144.89]) by mx1.freebsd.org (Postfix) with ESMTP id C3C9AAE4 for ; Wed, 11 Mar 2015 15:06:14 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.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 170AE61541; Wed, 11 Mar 2015 14:11:08 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp1.ore.mailhop.org (smtp1.ore.mailhop.org [10.83.15.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Wed, 11 Mar 2015 14:11:08 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1426083068302:1505907783 X-MC-Ingress-Time: 1426083068302 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp1.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YVhLn-0003Wa-V1; Wed, 11 Mar 2015 14:11:08 +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 t2BEB64f011831; Wed, 11 Mar 2015 08:11:06 -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: U2FsdGVkX1+JGALfhblIYjr4gUJLn9xb Message-ID: <1426083066.33324.34.camel@freebsd.org> Subject: Re: BBB freebsd-current backtrace. why? From: Ian Lepore To: jungle Boogie Date: Wed, 11 Mar 2015 08:11:06 -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 15:06:15 -0000 On Tue, 2015-03-10 at 21:09 -0700, jungle Boogie wrote: > Hi Jason, > On 10 March 2015 at 19:05, Jason Birch wrote: > > > > 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 > > > > Quick Googling turns up these resources: > > > > lock order reversals - what do they mean?: > > https://lists.freebsd.org/pipermail/freebsd-current/2003-December/016617.html > > Glossary of Kernel Options for Debugging: > > https://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-options.html > > FreeBSD LOR(lock order reversal)s seen and comments: > > http://sources.zabbadoz.net/freebsd/lor.html > > Based on what Ian says, I hope these BT don't continue. Those threads > are very likely before the BBB was made...much less had freeBSD > running, so hopefully some progress has been made with freeBSD. The point is that those LORs are harmless. They were declared harmless by the gurus who understand them, years ago, and apparently just by issuing that proclamation, it's a closed subject and we all just have to live with the spewage. -- Ian