Warner Losh wrote:
>
> I've added INVARIANTS and WITNESS to my kernel. Today I get a random
> panic on boot sometimes:
>
> lock order reseral (this doesn't cause the panic, but
> does seem to happen all the time)
> 1st vnode interlock last acquired @ ../../usr/ffs/ffs_fsops.c:396
> 2nd 0xc04837a0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:457
> 3rd 0xc80b9e8c vnode interlock @ ../../kern/vfs_subr.c:1872
I keep dropping into ddb with:
ad1: 99MB <VMware Inc. Virtual Hard Drive> [216/15/63] at ata0-slave WDMA2
Mounting root from ufs:/dev/ad0s1a
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:239
2nd 0xc085d654 ucred @ ../../kern/kern_prot.c:1177
3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239
lock order reversal
1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625
2nd 0xc02d0a60 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940
3rd 0xc3d7186c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:239
2nd 0xc02b8620 uidinfo hash @ ../../kern/kern_resource.c:765
3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239
lock order reversal
1st lockmgr last acquired @ ../../kern/kern_lock.c:239
2nd 0xc08d321c uidinfo struct @ ../../kern/kern_resource.c:819
3rd 0xc02b65e0 lockmgr @ ../../kern/kern_lock.c:239
hitting 'c' (for continue) allows me to go on....
This with a kernel CVSUP'd in the last day.
I'll CVsup again as I vaguely remember a commit message that may affect this.
--
__--_|\ Julian Elischer
/ \ [EMAIL PROTECTED]
( OZ ) World tour 2000-2001
---> X_.---._/
v
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
