Date: Mon, 08 Oct 2007 21:54:04 +0400 From: Yuri Pankov <yuri.pankov@gmail.com> To: Per olof Ljungmark <peo@intersonic.se> Cc: Elvar <elvar@ooz.net>, freebsd-questions@freebsd.org Subject: Re: freezing, hard locking, and debug.mpsafenet=0 Message-ID: <1191866044.1286.0.camel@darklight> In-Reply-To: <470A6C43.7040104@intersonic.se> References: <4705E5B1.6010808@ooz.net> <470A6C43.7040104@intersonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2007-10-08 at 19:43 +0200, Per olof Ljungmark wrote: > Elvar wrote: > > Hi there, > <snip> > > http://www.freebsdforums.com/forums/showthread.php?t=38765&page=1&pp=1 > > <http://www.freebsdforums.com/forums/showthread.php?t=38765&page=1&pp=1> > > which seemed to describe the same freezing I was having. One person > > mentioned setting debug.mpsafenet=0 in /boot/loader.conf and not having > > a problem since doing so. Well, I ended up doing the same thing and it's > > been about 25 days with not one freeze / lockup. > > > > It's my understanding that the ability to even disable this has been > > taken out of 7.x, I only can hope that it's not an issue in 7.x like it > > is on some systems in 6.x. So anyway, I hope this helps someone out. > > Hi, > What hardware is this? Sounds very similar to something I've seen too, > if it's the samt issue I can confirm it is happening in -CURRENT also. > > Could someone familiar with -CURRENT perhaps explain why this option > (debug.mpsafenet=0) is gone? > > Per olof This might be the answer: http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075180.html -- Yuri Pankov <yuri.pankov@gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1191866044.1286.0.camel>