From owner-freebsd-current Mon Apr 16 20:11:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 4087237B42C for ; Mon, 16 Apr 2001 20:11:22 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3H3B9G85218; Mon, 16 Apr 2001 20:11:09 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200104161623.f3GGN6W83082@bunrab.catwhisker.org> Date: Mon, 16 Apr 2001 20:10:38 -0700 (PDT) From: John Baldwin To: David Wolfskill Subject: RE: lock messages from today's -CURRENT Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Apr-01 David Wolfskill wrote: > I saw that jhb committed some changes as of r1.307 of > src/sys/i386/conf/GENERIC, so I replicated those changes (that I didn't > already have) to my kernel config. > > Got -CURRENT built & running; the message below (bracketed by "normal" > messages, to supply a little context) appear to be documenting weirdnesses, > but I don't see other evidence of problems: > > Apr 16 08:57:44 localhost /boot/kernel/kernel: pccard: card inserted, slot 1 > Apr 16 08:57:44 localhost /boot/kernel/kernel: acquring duplicate lock of > same type: "allproc" > Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st @ > /usr/src/sys/kern/kern_proc.c:584 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd @ > /usr/src/sys/kern/kern_proc.c:143 > Apr 16 08:57:44 localhost /boot/kernel/kernel: lock order reversal > Apr 16 08:57:44 localhost /boot/kernel/kernel: 1st vnode interlock last > acquired @ /usr/src/sys/kern/vfs_vnops.c:625 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 2nd 0xc0459b80 mntvnode @ > /usr/src/sys/ufs/ffs/ffs_vfsops.c:954 > Apr 16 08:57:44 localhost /boot/kernel/kernel: 3rd 0xce7d54ac vnode interlock > @ /usr/src/sys/ufs/ffs/ffs_vfsops.c:963 > Apr 16 08:57:44 localhost savecore: magic number mismatch (8b98aa0d != > 8fca0101) > Apr 16 08:57:44 localhost savecore: no core dump These are known right now. The allproc one is because witness is still somewhat bogus wrt to sx locks and treats the recursive shared lock as duplicate acquires of the same lock. The other reversals that are vfs related have been around since probably at least 4.4bsd or perhaps earlier. -- John Baldwin -- 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message