> Seriously, that's ok, I only want to check if I get the same panic. And give
> feedback of course.

Here I am again. Didn't get as far as a login prompt, I have a panic when qmail
starts up:

lock order reversal
 1st lockmgr last acquired @ ../../kern/kern_lock.c:239
 2nd 0xc02630c0 uidinfo hash @ ../../kern/kern_resource.c:727
 3rd 0xc0261080 lockmgr @ ../../kern/kern_lock.c:239
panic: mutex_enter: recursion on non-recursive mutex process lock @
Stopped at      Debugger+0x46:  pushl   %ebx
db> trace
Debugger(c0213d83) at Debugger+0x46
panic(c0212cc0,c0211119,c021195a,104,c65d6964) at panic+0x70
witness_enter(c65d6964,0,c021195a,104,c65d6964) at witness_enter+0x1b2
_mtx_enter(c65d6964,0,c021195a,104) at _mtx_enter+0x154
lockmgr(c026849c,1,0,c65d6840,c0a6691c) at lockmgr+0xad
kernacc(c027bd40,4,1,c023c500,0c0212497,34d) at kernacc+0x54
mtx_validate(c0a6691c,1) at mtx_validate+0x59
mtx_init(c0a6691c,c02138cc,0,0,57) at mtx_init+0x13
uicreate(57,c65d6964,c0a6d0c0,c65e0f30,c014f13a) at uicreate+0x8a
uifind(57,c65d6964,0,c02135b0,586) at uifind+0x33
change_ruid(c65d6840,57,c65d6840,0,1) at change_ruid+0x46
setuid(c65d6840,c65e0f80,bfbffd80,bfbffd7c,bfbffd90) at setuid+0x3a
syscall2(2f,2f,2f,bfbffd90,bfbffd7c) at syscall2+0x29c
Xint0x80_syscall() at Xint0x80_syscall+0x23
--- syscall 0x17, eip = 0x280a039c, esp 0xbfbffcdc, ebp = 0xbfbffcf8

At least I think it's qmail, looking at the `ps' output...

              The best things in life are free, but the
                expensive ones are still worth a look.

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

Reply via email to