From owner-freebsd-current Tue Oct 24 20:25:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from jaunt.chuckr.org (jaunt.chuckr.org [216.254.96.119]) by hub.freebsd.org (Postfix) with ESMTP id 4694637B479 for ; Tue, 24 Oct 2000 20:25:14 -0700 (PDT) Received: from localhost (chuckr@localhost) by jaunt.chuckr.org (8.9.3+Sun/8.9.3) with ESMTP id XAA06649; Tue, 24 Oct 2000 23:25:19 -0400 (EDT) Date: Tue, 24 Oct 2000 23:25:18 -0400 (EDT) From: Chuck Robey To: Mike Meyer Cc: current@FreeBSD.ORG Subject: Re: smp instability In-Reply-To: <14838.18086.224614.149206@guru.mired.org> 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 On Tue, 24 Oct 2000, Mike Meyer wrote: > Chuck Robey writes: > > I'm having rather extreme problems with stability on my dual PIII > > setup. I know this is to be expected, but it's gotten so extreme on my > > system, I can't spend more than a few minutes before it locks up. > > > > Is there any chance that I could make things better by using a sysctl to > > tell the box it's now a single-cpu system? I can't read man pages at the > > moment (I'm composing this on my Sparc Ultra-5) so if this might work, and > > someone knows the exact command to use, I'd appreciate a bit of help. > > Try "sysctl -w machdep.smp_active=0". It's not clear how much good > this will do since you'll still be running an SMP kernel. Please > let us know how that works. With less than a full hour's history, I haven't exactly heavily tested it, but it only lasted 10 minutes last time, and my system is still kicking currently. Regarding that control-C needed on booting thing: when I log in, my call to fortune needs to be interrupted also, so I immediately went and tried a "ktrace fortune". I didn't need to kdump, because doing that ktrace seems to have somehow cleared the control-C thing on all that kicked it off before (not just fortune alone). My system is really repeatable on that, so if it's not yet fixed, and you have other things to try on it, I'd be willing (if my system stays up!) In the meantime, I think that "sysctl -w machdep.smp_active=0" might actually work for me (I did it in single user so the multiuser startup would be cleaner). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message