On 12-Mar-01 Dag-Erling Smorgrav wrote:
> Mikhail Teterin <[EMAIL PROTECTED]> writes:
>> > If you can, please reproduce the panic on a kernel compiled with the
>> > INVARIANTS, INVARIANT_SUPPORT and WITNESS options.
>> Well, with this options on, the machine does not crash, but the
>> program segfaults on startup:
> The trace you're showing looks like it's from a shell script that
> starts civctp. I need to see the trace from the civctp binary itself.
>> lock order reversal
>> 1st lockmgr interlock last acquired @ ../../kern/kern_lock.c:239
>> 2nd 0xcefa0520 process lock @ ../../kern/kern_sig.c:183
>> 3rd 0xc1029f80 lockmgr interlock @ ../../kern/kern_lock.c:560
> Haven't seen this one before... If it's reproducible, could you do the
It's stupidness due to proctree and allproc locks being backed by lockmgr I
think. I'm waiting on looking at this one until proctree and allproc are
converted to sx locks.
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message