From owner-freebsd-stable Wed Jul 4 15:43:43 2001 Delivered-To: freebsd-stable@freebsd.org Received: from midten.fast.no (midten.fast.no [213.188.8.11]) by hub.freebsd.org (Postfix) with ESMTP id 7DF9537B406 for ; Wed, 4 Jul 2001 15:43:39 -0700 (PDT) (envelope-from Tor.Egge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [213.188.8.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id AAA96500; Thu, 5 Jul 2001 00:43:35 +0200 (CEST) Message-Id: <200107042243.AAA96500@midten.fast.no> To: jjreynold@home.com Cc: stable@FreeBSD.ORG Subject: Re: Hard lockups since cvsup'ing Jul 1st. Help! From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 4 Jul 2001 07:14:33 -0700" References: <15171.9417.415084.463575@whale.home-net> 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: Thu, 05 Jul 2001 00:43:35 +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > FWIW, applying both of Tor's patches (the MFS one committed to > > -stable AND the first patch to procfs included in his email) seems > > to sort the problem here -- I have gone without problems through a > > full make world. > > > > I concur. Commit the patch Tor :) I committed a different patch (to sys/kern/vfs_default.c) and backed out the mfs patch. vop_noislocked() should not be identical to vop_stdislocked(). I changed it to return 0 (which the 5.0-current version does). This should solve the SMP lockup problem when using file systems that did not start their per-vnode private data with a struct lock (mfs, procfs, devfs and linprocfs) - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message