Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Oct 2004 04:53:40 -0400 (EDT)
From:      Robert Watson <rwatson@freebsd.org>
To:        Volker <volker@vwsoft.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: beta6/7 machine freeze
Message-ID:  <Pine.NEB.3.96L.1041017045205.12860A-100000@fledge.watson.org>
In-Reply-To: <4171CDF3.6050901@vwsoft.com>

next in thread | previous in thread | raw e-mail | index | archive | help

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
> 



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1041017045205.12860A-100000>