From owner-freebsd-current@FreeBSD.ORG Sun Oct 17 08:53:44 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BA9C016A4CF for ; Sun, 17 Oct 2004 08:53:44 +0000 (GMT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2991743D58 for ; Sun, 17 Oct 2004 08:53:44 +0000 (GMT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.13.1/8.13.1) with ESMTP id i9H8re4L021356; Sun, 17 Oct 2004 04:53:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)i9H8reKl021352; Sun, 17 Oct 2004 04:53:40 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 17 Oct 2004 04:53:40 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Volker In-Reply-To: <4171CDF3.6050901@vwsoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: beta6/7 machine freeze X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Oct 2004 08:53:44 -0000 On Sun, 17 Oct 2004, Volker wrote: > I'm still using debug.mpsafenet=0 for the i4b code (may I remove it or > is it still required for i4b?). You can move the explicit reference, because the network stack will automatically set debug.mpsafenet=0 if you compile i4b into it. I hope to have some patches to make it more mpsafe in the near future, but am currently working on other bugs. I'll probably bother you again in a few weeks with some patches to try :-). Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Principal Research Scientist, McAfee Research > > Before your i4b changes the machine died in the middle or at the end of > a ppp connection. For me, this is a huge step forward (or backward into > stability). > > Now while the machine is running stable (no lock ups, no panics) for > quite some days (the first time since BETA-4) I'm sure RELENG_5 made a > huge step into the 5-STABLE direction. Two weeks ago I really had > concerns for 5's stability but now I think 5.x will do a good job as 4.x > did it. > > I think you guys really did a great job! :) > > Will remove INVARIANTS and WITNESS now and enjoy the speed of a good OS. > > Thanks, > > Volker > > > > On 2004-10-11 17:44, Robert Watson wrote: > > > In fact, this is almost certainly part of the problem. I'd try setting > > debug.mpsafenet=0 in /boot/loader.conf and reboot as a first step t see if > > the problem goes away. > > > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > > > On Mon, 11 Oct 2004, Robert Watson wrote: > > > > > >>BTW, since it sounds like this might be a networking related problem, you > >>might try setting debug.mpsafenet=0 in loader.conf to see if the problem > >>goes away -- that will put the Giant lock back over the network stack and > >>might close races. i4b might not be MPSAFE, I'll go take a look. > >> > >>Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > >>robert@fledge.watson.org Principal Research Scientist, McAfee Research > >> > >> > > > > > > -- > GPG/PGP fingerprint: > FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1 >