From owner-freebsd-current Wed Feb 28 1:13:36 2001 Delivered-To: freebsd-current@freebsd.org Received: from ns.plaut.de (ns.plaut.de [194.99.75.166]) by hub.freebsd.org (Postfix) with ESMTP id 3649537B718 for ; Wed, 28 Feb 2001 01:13:33 -0800 (PST) (envelope-from root@nihil.plaut.de) Received: (from uucp@localhost) by ns.plaut.de (8.9.3/8.9.3) with UUCP id KAA48335 for current@freebsd.org; Wed, 28 Feb 2001 10:13:31 +0100 (CET) (envelope-from root@nihil.plaut.de) Received: from localhost (root@localhost) by nihil.plaut.de (8.11.1/8.8.8) with ESMTP id f1S9D8I00371 for ; Wed, 28 Feb 2001 10:13:08 +0100 (CET) (envelope-from root@nihil) Date: Wed, 28 Feb 2001 10:13:08 +0100 (CET) From: Michael Reifenberger To: FreeBSD-Current Subject: lock order reversal under -current 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 Hi, with -current sources (as of -now) I get during startup: lock order reversal 1st vnode interlock last acquired @ ../../kern/vfs_vnops.c:625 2nd 0xc0306840 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:940 3rd 0xcbd20a0c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:949 32 Is that bad? Bye! ---- Michael Reifenberger ^.*Plaut.*$, IT, R/3 Basis, GPS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message