From owner-freebsd-current Wed Jul 26 16:19:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 425B137B6F4 for ; Wed, 26 Jul 2000 16:19:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA02916 for ; Wed, 26 Jul 2000 16:19:25 -0700 Date: Wed, 26 Jul 2000 16:18:41 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: more ffs locking breakage? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has this been addressed today? This is with an SMP kernel for this morning's sources.... Always seems to happen on a reboot. syncing disks... panic: lockmgr: pid 85061, not exclusive lock holder 0 unlocking mp_lock = 01000001; cpuid = 1; lapic.id = 0c000000 Debugger("panic") Stopped at Debugger+0x34: movb $0,in_Debugger.591 db> t Debugger(c0266012) at Debugger+0x34 panic(c0265100,14c45,c02650e0,0,c8ad7000) at panic+0xa4 lockmgr(c0b09a00,6,c8ad706c,c8b5d740,c92a3e24) at lockmgr+0x2c8 vop_stdunlock(c92a3e40,c92a3e50,c01fe477,c92a3e40,c8ad7000) at vop_stdunlock+0x3a ufs_vnoperate(c92a3e40) at ufs_vnoperate+0x15 ufs_inactive(c92a3e70,c92a3e80,c01a4855,c92a3e70,c8ad7000) at ufs_inactive+0x127 ufs_vnoperate(c92a3e70,c8ad7000,0,c028c480,c8ad7000) at ufs_vnoperate+0x15 vput(c8ad7000,0,c02c5880,c92a3f80,0) at vput+0xa1 ffs_sync(c0aa9000,2,c0719980,c02c5880,c0aa9000) at ffs_sync+0x150 sync(c02c5880,0,c0265ca5,1,c8b5d740) at sync+0xa1 boot(0,c92a3fa0,c0241fa1,c8b5d740,c92a3f80) at boot+0x9b reboot(c8b5d740,c92a3f80,2,0,0) at reboot+0x1c syscall2(2f,2f,2f,0,0) at syscall2+0x219 Xint0x80_syscall() at Xint0x80_syscall+0x2b To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message