Mikhail Teterin <[EMAIL PROTECTED]> writes:
> > If you can, please reproduce the panic on a kernel compiled with the
> 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

 1) recompile your kernel with WITNESS_DDB

 2) hook up a serial console and boot with '-h' in /boot.config

 3) provoke the reversal, then get the output from 'trace', 'show
    mutex' and 'show witness' at the DDB prompt

 4) type 'continue' to exit DDB and continue running normally.

>       lock order reversal
>        1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625
>        2nd 0xc0419680 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:939
>        3rd 0xcefb986c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:948

This is a known (and probably benign) bug.

Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to