Date: Mon, 08 Oct 2007 21:29:03 +0200 From: Kris Kennaway <kris@FreeBSD.org> 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: <470A84FF.1090605@FreeBSD.org> In-Reply-To: <470A7FEC.6060806@intersonic.se> References: <4705E5B1.6010808@ooz.net> <470A6C43.7040104@intersonic.se> <470A7CE7.1070605@FreeBSD.org> <470A7FEC.6060806@intersonic.se>
next in thread | previous in thread | raw e-mail | index | archive | help
Per olof Ljungmark wrote: > Kris Kennaway wrote: >> Per olof Ljungmark wrote: >>> Elvar wrote: >>>> Hi there, >>> <snip> > <snip> >>> >>> Could someone familiar with -CURRENT perhaps explain why this option >>> (debug.mpsafenet=0) is gone? >> >> Because it was an obsolete option that was complicating the code and >> holding back further development. >> >> If you are seeing bugs, you need to follow through with obtaining the >> necessary debugging (see the developers handbook), then submit a PR. >> Note that if you don't do this then you cannot reasonably expect >> anyone to fix your problems. > > Kris, if a system locks up completely (does not take any input, no > dumps, just stop) is there anything one can do in terms of debugging? > > I would post more information if I knew how to get it. Of course, and it's documented in the above place. Did you read it yet? Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?470A84FF.1090605>