Date: Thu, 3 May 2001 07:57:45 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: "Bruce A. Mah" <bmah@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: lock order reversals, anyone? Message-ID: <Pine.BSF.4.21.0105030757260.17151-100000@beppo.feral.com> In-Reply-To: <200105031452.f43EqeX32443@bmah-freebsd-0.cisco.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 May 2001, Bruce A. Mah wrote: > If memory serves me right, Matthew Jacob wrote: > > > T-o-T about 24 hours ago: > > ??? Top of Tree > > > acquiring duplicate lock of same type: "allproc" > > > 1st @ /usr/src/sys/kern/kern_proc.c:609 > > > 2nd @ /usr/src/sys/kern/kern_proc.c:146 > > > lock order reversal > > > 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 > > > 2nd 0xfffffc000080f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 > > > 3rd 0xfffffe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 > > I saw something similar on my 5-CURRENT box built around 27 April. No > core dumps that I know of. These showed up at boot time, shortly after > my machine's SCSI devices were probed. From /var/log/messages: > > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: <SEAGATE ST39236LW 0004> Fixed Direct Access SCSI-3 device > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xcb64665c process lock @ /usr/src/sys/kern/kern_exit.c:542 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xc0e3f988 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: acquiring duplicate lock of same type: "allproc" > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st @ /usr/src/sys/kern/kern_proc.c:607 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd @ /usr/src/sys/kern/kern_proc.c:144 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: lock order reversal > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 1st vnode interlock last acquired @ /usr/src/sys/kern/vfs_vnops.c:636 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 2nd 0xc050d060 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:975 > May 2 10:18:59 bmah-freebsd-1 /boot/kernel/kernel: 3rd 0xccf9c52c vnode interlock @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:984 > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: ntpd 4.0.99b Fri Apr 27 16:43:30 PDT 2001 (1) > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2040 > May 2 10:19:12 bmah-freebsd-1 ntpd[355]: using kernel phase-lock loop 2041 > > My machine is running a GENERIC kernel. > > Bruce. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0105030757260.17151-100000>