Re: panic: mutex process slock not owned ...

Marcel Moolenaar wrote:
> Log says it all:
> 
>     ...
> Waiting 3 seconds for SCSI devices to settle
> panic: mutex process slock not owned at ../../../kern/kern_resource.c:1034
> cpuid = 0
> KDB: enter: panic
> [thread pid 0 tid 0 ]
> Stopped at      kdb_enter+0x32: leave
> db> bt
> Tracing pid 0 tid 0 td 0xc07ade50
> kdb_enter(c074716f,0,c0745e8f,c0c20cc8,0,...) at kdb_enter+0x32
> panic(c0745e8f,c0746206,c07469ee,40a,c0c20cf8,...) at panic+0x126
> _mtx_assert(c1e5d814,1,c07469ee,40a,c1e5d804,...) at _mtx_assert+0x8d
> rufetch(c1e5d804,c0c20d14,c07423fa,1fd,c078a6e4,...) at rufetch+0x32
> proc0_post(0,c1ec00,c1ec00,c1e000,c28000,...) at proc0_post+0x5c
> mi_startup() at mi_startup+0xa6
> begin() at begin+0x2c

ok, pointy hat to me.
it seems I just commited the pre-merge version of this patch instead 
than the post-merge with the other rusage patch.

Expect a fix in the next 10 mins.

Attilio