On Sunday 24 March 2002 05:26 pm, you wrote: > The bento cluster is now running with WITNESS enabled to try and track > down some odd UMA lock corruption panics. Instead, it found the > following lock order reversal in sys_pipe.c overnight: > > Mar 24 07:31:44 <user.crit> gohan17 kernel: lock order reversal > Mar 24 07:31:44 <user.crit> gohan17 kernel: 1st 0xcf51aa80 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:31:44 <user.crit> > gohan17 kernel: 2nd 0xcf88dadc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:12 > <user.crit> gohan10 kernel: lock order reversal > Mar 24 07:32:12 <user.crit> gohan10 kernel: 1st 0xd9a29dc0 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:12 <user.crit> > gohan10 kernel: 2nd 0xd961addc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 07:32:57 > <user.crit> gohan12 kernel: lock order reversal > Mar 24 07:32:57 <user.crit> gohan12 kernel: 1st 0xd9423080 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 07:32:57 <user.crit> > gohan12 kernel: 2nd 0xdaa704dc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 Mar 24 09:02:29 > <user.crit> gohan13 kernel: lock order reversal > Mar 24 09:02:29 <user.crit> gohan13 kernel: 1st 0xd99d6500 pipe mutex @ > /local0/scratch/usr/src/sys/kern/sys_pipe.c:450 Mar 24 09:02:29 <user.crit> > gohan13 kernel: 2nd 0xd971cddc process lock @ > /local0/scratch/usr/src/sys/kern/kern_sig.c:2093 > > Those source references are from a -current kernel from last night. > > Kris I think I found something similar as well, I also found a panic, but havn't had time to track it down. The panic doesn't occur with a kernel from march 13th, but occurs with the latest kernels.
Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
