On Tue, Mar 26, 2002 at 02:43:07PM -0800, Alfred Perlstein wrote: > * Kris Kennaway <[EMAIL PROTECTED]> [020324 14:26] 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. > > Are you %100 on that? How did you get this to happen?
Yes. I wasn't doing anything special, unless you count building 5-10 packages simultaneously for a period of 24 hours counts as special ;-) I had to increase the witness limits in order to stop getting the following: witness_get: witness exhausted Well, I eventually got it anyway on all of the machines, but it didn't happen instantly like it did with the default values ;-) I haven't seen any more witness warnings, but it's probably only because it ran out of resources. I expect I'll see it again when I reboot the cluster. Kris
msg36603/pgp00000.pgp
Description: PGP signature
