From owner-freebsd-hackers@FreeBSD.ORG Sat Jun 14 10:29:33 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 17A52C37; Sat, 14 Jun 2014 10:29:33 +0000 (UTC) Received: from elf.torek.net (50-73-42-1-utah.hfc.comcastbusiness.net [50.73.42.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA4D32333; Sat, 14 Jun 2014 10:29:32 +0000 (UTC) Received: from elf.torek.net (localhost [127.0.0.1]) by elf.torek.net (8.14.5/8.14.5) with ESMTP id s5EAAtS0087393; Sat, 14 Jun 2014 04:10:55 -0600 (MDT) (envelope-from torek@torek.net) Message-Id: <201406141010.s5EAAtS0087393@elf.torek.net> From: Chris Torek To: Darren Reed Subject: Re: FreeBSD 10.0 adaptive mutex with strange mtx_lock value = panic In-reply-to: Your message of "Sat, 14 Jun 2014 19:43:53 +1000." <539C1959.30203@freebsd.org> Date: Sat, 14 Jun 2014 04:10:55 -0600 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (elf.torek.net [127.0.0.1]); Sat, 14 Jun 2014 04:10:55 -0600 (MDT) Cc: freebsd-hackers@freebsd.org, Mateusz Guzik X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Jun 2014 10:29:33 -0000 >I added "options INVARIANTS" to a kernel and recompiled.. > >Well, I tried to recompile - compiling ends like this: > >cam_periph.o: In function `cam_periph_find': >/usr/src/sys/amd64/compile/DEBUG/../../../cam/cam_periph.c:301: >undefined reference to `__mtx_assert' [etc] The INVARIANTS option requires the INVARIANT_SUPPORT option. I believe INVARIANTS ought to just automatically turn on INVARIANT_SUPPORT, really. But it's pretty minor, once you know. Chris