Date: Sun, 10 Dec 2006 00:10:42 +0300 From: "Andrew Pantyukhin" <infofarmer@FreeBSD.org> To: "Robert Watson" <rwatson@freebsd.org> Cc: freebsd-current@freebsd.org, yal <yal@yal.hopto.org> Subject: Re: CURRENT freezes on Laitude D520 Message-ID: <cb5206420612091310r719f7b3en2d4fb35b23453ddf@mail.gmail.com> In-Reply-To: <20061209204924.N9926@fledge.watson.org> References: <52944.192.168.1.110.1165679313.squirrel@yal.hopto.org> <20061209195519.B60055@mp2.macomnet.net> <20061209204924.N9926@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/9/06, Robert Watson <rwatson@freebsd.org> wrote: > While this may be useful in doing some initial debugging and working around > the problem, I'd really appreciate it if people didn't run with > debug.mpsafenet="0" for any extended period, as it masks bugs rather than > fixing them, and results in them not getting fixed. It also leads to a > significant performance hit, and we really don't want people running with > debugging features like this turned on by default; I'd rather they used the > cycles on INVARIANTS and WITNESS. Do we have to forget about IPSEC+IPv6?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420612091310r719f7b3en2d4fb35b23453ddf>