FreeBSD 10.0 adaptive mutex with strange mtx_lock value = panic

[Darren Reed]

On 14/06/2014 6:48 PM, Mateusz Guzik wrote:
...
> This is a 'destroyed mutex' state, i.e. you are doing mtx_lock after
> mtx_destroy.
> 
> A kernel with INVARIANTS enabled wold tell you that straight away.

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'
cam_periph.o: In function `cam_periph_release_locked_buses':
/usr/src/sys/amd64/compile/DEBUG/../../../cam/cam_periph.c:382:
undefined reference to `__mtx_assert'
cam_periph.o: In function `camperiphfree':
/usr/src/sys/amd64/compile/DEBUG/../../../cam/cam_periph.c:603:
undefined reference to `__mtx_assert'
cam_periph.o: In function `cam_periph_release':
/usr/src/sys/amd64/compile/DEBUG/../../../cam/cam_periph.c:409:
undefined reference to `__mtx_assert'
cam_periph.o: In function `cam_periph_hold':
/usr/src/sys/amd64/compile/DEBUG/../../../cam/cam_periph.c:430:
undefined reference to `__mtx_assert'
...

Darren