Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 15 Jun 2014 12:14:56 +1000
From:      Darren Reed <darrenr@freebsd.org>
To:        Chris Torek <torek@torek.net>
Cc:        freebsd-hackers@freebsd.org, Mateusz Guzik <mjguzik@gmail.com>
Subject:   Re: FreeBSD 10.0 adaptive mutex with strange mtx_lock value = panic
Message-ID:  <539D01A0.50506@freebsd.org>
In-Reply-To: <201406141010.s5EAAtS0087393@elf.torek.net>
References:  <201406141010.s5EAAtS0087393@elf.torek.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 14/06/2014 8:10 PM, Chris Torek wrote:
>> 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.

Thanks and yes, I think you're right.

Too bad we can't build that logic into the conf files.

Darren





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?539D01A0.50506>