From owner-freebsd-current Sun Sep 23 9:57:32 2001 Delivered-To: freebsd-current@freebsd.org Received: from arb.arb.za.net (arb.arb.za.net [196.7.148.4]) by hub.freebsd.org (Postfix) with ESMTP id E0DF037B415 for ; Sun, 23 Sep 2001 09:57:25 -0700 (PDT) Received: (from uucp@localhost) by arb.arb.za.net (8.11.3/8.11.3) with UUCP id f8NGv5E88878; Sun, 23 Sep 2001 18:57:05 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.6/8.11.6) with ESMTP id f8NGuXE00513; Sun, 23 Sep 2001 17:56:33 +0100 (BST) (envelope-from mark@grondar.za) Message-Id: <200109231656.f8NGuXE00513@grimreaper.grondar.za> To: Evan Sarmiento Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic on mount References: <200109231559.f8NFxPc13750@csa.bu.edu> In-Reply-To: <200109231559.f8NFxPc13750@csa.bu.edu> ; from Evan Sarmiento "Sun, 23 Sep 2001 11:59:25 EDT." Date: Sun, 23 Sep 2001 17:56:33 +0100 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > After compiling a new kernel, installing it, when my laptop > tries to mount its drive, it panics with this message: > > panic: lock (sleep mutex) vnode interlock not locked @ > ../../../kern/vfs_default.c:460 > > which is: > > if (ap->a_flags & LK_INTERLOCK) > mtx_unlock(&ap->a_vp->v_interlock); I get exactly the same thing. Manual bactrace is: panic witness_unlock _mtx_unlock_flags vop_nolock vop_defaultop vn_lock ffs_mountfs ffs_mount vfs_mountroot_try vfs_mountroot mi_startup begin M -- o Mark Murray \_ FreeBSD Services Limited O.\_ Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message