freezing, hard locking, and debug.mpsafenet=0
Per olof Ljungmark
peo at intersonic.se
Mon Oct 8 12:07:35 PDT 2007
Kris Kennaway wrote:
> Per olof Ljungmark wrote:
>> Elvar wrote:
>>> Hi there,
>> 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.
More information about the freebsd-questions