From owner-freebsd-smp Fri Sep 17 20:49:43 1999 Delivered-To: freebsd-smp@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id C8338154EC for ; Fri, 17 Sep 1999 20:49:12 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id FAA19076; Sat, 18 Sep 1999 05:49:06 +0200 (CEST) Message-Id: <199909180349.FAA19076@midten.fast.no> To: sraja@cinenet.net Cc: freebsd-smp@FreeBSD.ORG Subject: Re: SMP problems continue on 3.3-RC From: Tor.Egge@fast.no In-Reply-To: Your message of "Fri, 17 Sep 1999 15:39:01 -0700 (PDT)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Sat, 18 Sep 1999 05:49:06 +0200 Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > :panic (c0241d25,0,cc848cb0,1,c01769d4) at panic 0xa4 > > :bsl1 (cc848c40, 2, cbbe6860, cbe3043f, cc848d00) at bs1 > > :nfs_lookup (cbf3de30, cbafce00, cbf3dedc, cbf3deb80) at nfs_lookup 0x22f > > :lookup(cbf3deb8,cbbe6860,cbbe6860,cbf3df94,cbf3de74) at lookup 0x2c1 > > :namei(cbf3deb8,cbbe6860,c0292740,0,8162ce4) at namei 0x133 > > :stat(cbbe6860,cbf3df94,13,5,bfbfdd50) at stat 0x44 > > :syscall(27,bfbf0027,bfbfdd50,5,bfbfdb28) at syscall 0x107 > > :Xint0x80_syscall() at Xint)x80_syscall + 0x4c nfs_lookup called vget, but the trace is incomplete due to s_lock being a frameless function. One of the simple_lock calls in vget failed due to the vnode interlock already being held by the same CPU. If it was held by any other CPU then you would get a hang instead of a panic. I suggest testing a UP kernel with the SIMPLELOCK_DEBUG kernel option defined and mi_switch modified to panic instead of just printing a warning when a process attempts to sleep with a simple lock held. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message