Re: lock order reversals, anyone?
Matthew Jacob [EMAIL PROTECTED] writes: pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) That may well be a bug in your app. Xscreensaver, for instance, is riddled with dangling-pointer and off-by-one bugs that rarely (if ever) show up on -STABLE, but result in an immediate core dump on -CURRENT because it has malloc() debugging enabled by default. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversals, anyone?
Possible. On 7 May 2001, Dag-Erling Smorgrav wrote: Matthew Jacob [EMAIL PROTECTED] writes: pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) That may well be a bug in your app. Xscreensaver, for instance, is riddled with dangling-pointer and off-by-one bugs that rarely (if ever) show up on -STABLE, but result in an immediate core dump on -CURRENT because it has malloc() debugging enabled by default. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
lock order reversals, anyone?
T-o-T about 24 hours ago: lock order reversal 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 3rd 0xfeaab8d0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 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 0xfc80f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 3rd 0xfe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversals, anyone?
If memory serves me right, Matthew Jacob wrote: T-o-T about 24 hours ago: ??? lock order reversal 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 3rd 0xfeaab8d0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 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 0xfc80f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 3rd 0xfe0026918080 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. PGP signature
Re: lock order reversals, anyone?
On Thu, May 03, 2001 at 07:31:50AM -0700, Matthew Jacob wrote: T-o-T about 24 hours ago: lock order reversal 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 3rd 0xfeaab8d0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 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 0xfc80f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 3rd 0xfe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) Don't know about your 4.1 executable, but the lock order reversals are a well known issue: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=161827+165415+/usr/local/www/db/text/2001/freebsd-current/20010429.freebsd-current and http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=91622+94620+/usr/local/www/db/text/2001/freebsd-current/20010422.freebsd-current -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org PGP signature
Re: lock order reversals, anyone?
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 0xfc80f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 3rd 0xfe0026918080 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 [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: lock order reversals, anyone?
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=161827+165415+/usr/local/www/db/text/2001/freebsd-current/20010429.freebsd-current Right- sorry to trouble you all. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: lock order reversals, anyone?
On 03-May-01 Matthew Jacob wrote: T-o-T about 24 hours ago: lock order reversal 1st lockmgr interlock last acquired @ /usr/src/sys/kern/kern_lock.c:239 2nd 0xfe0025df8548 process lock @ /usr/src/sys/kern/kern_exit.c:542 3rd 0xfeaab8d0 lockmgr interlock @ /usr/src/sys/kern/kern_lock.c:239 This is new. We shouldn't be holding the proc lock and dinking with lockmgr at the same time. (Well, in theory at least.) 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 This is old. This is really a case of recursion, I'm currently hacking on witness some more which will fix this. lock order reversal 1st vnode interlock last acquired @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:397 2nd 0xfc80f218 mntvnode @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:464 3rd 0xfe0026918080 vnode interlock @ /usr/src/sys/kern/vfs_subr.c:1881 This is quite old. I have some h0h0 patches to fix these, but I'm not sure that they are actually right: http://www.FreeBSD.org/~jhb/patches/mntvnode.patch pid 288 (nsrexecd), uid 0: exited on signal 11 (core dumped) (oh, yeah, a 4.1 built executable is dying, charming) Cute. :-/ -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
