From owner-freebsd-alpha@FreeBSD.ORG Wed Feb 15 21:20:22 2006 Return-Path: X-Original-To: freebsd-alpha@freebsd.org Delivered-To: freebsd-alpha@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6914516A420; Wed, 15 Feb 2006 21:20:22 +0000 (GMT) (envelope-from rand@meridian-enviro.com) Received: from newman.meridian-enviro.com (newman.meridian-enviro.com [207.109.235.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id D9A7443D46; Wed, 15 Feb 2006 21:20:21 +0000 (GMT) (envelope-from rand@meridian-enviro.com) X-Envelope-To: freebsd-alpha@freebsd.org Received: from delta.meridian-enviro.com (delta.meridian-enviro.com [10.10.10.43]) by newman.meridian-enviro.com (8.13.1/8.13.1) with ESMTP id k1FLKJmg033213; Wed, 15 Feb 2006 15:20:19 -0600 (CST) (envelope-from rand@meridian-enviro.com) Date: Wed, 15 Feb 2006 15:20:19 -0600 Message-ID: <8764nge2uk.wl%rand@meridian-enviro.com> From: "Douglas K. Rand" To: John Baldwin In-Reply-To: <87mzgu6b9w.wl%rand@meridian-enviro.com> References: <87u0b35fwp.wl%rand@meridian-enviro.com> <200602131309.55865.jhb@freebsd.org> <87slqn5bfz.wl%rand@meridian-enviro.com> <87mzgu6b9w.wl%rand@meridian-enviro.com> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: ClamAV 0.88/1289/Tue Feb 14 08:36:44 2006 on newman.meridian-enviro.com X-Virus-Status: Clean Cc: freebsd-alpha@freebsd.org Subject: Re: SMP problem on UP2000+ X-BeenThere: freebsd-alpha@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Alpha List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2006 21:20:22 -0000 Doug> I have a UP2000+ system from Microway with two 833 MHz CPUs, and Doug> it keeps freezing up on me when I run it with a SMP kernel. John> Have you tried disabling debug.mpsafevfs? Set it to 0 in the John> loader. Doug> Nope. Trying it now. Thanks for the tip. I'll let you know how Doug> it turns out. Doug> Well, it lasted about 4 hours before locking up on me. :( Doug> Trying it now with both mpsafevfs and mpsafevm set to 0. OK, we've been up for 45 hours with these settings: debug.mpsafevfs: 0 debug.mpsafenet: 1 debug.mpsafevm: 0 I'll let it cook a few more days with these settings, and then I'll try it with mpsafevfs turned on and leave mpsafevm off. I'll let you know how it goes. Again, thanks for the tip! This system is much faster with both CPUs running. :)