Date: Sun, 18 Mar 2007 13:29:45 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: freebsd-current@freebsd.org Subject: Re: Experiencing hangs on SMP box with no console messages given for clues. Details inside. Message-ID: <20070318192945.GB1264@seekingfire.com> In-Reply-To: <20070318154536.U20456@fledge.watson.org> References: <20070308125927.GA1265@seekingfire.com> <20070308204041.GA55240@xor.obsecurity.org> <20070310153206.GF1230@seekingfire.com> <3bbf2fe10703100749h14e9b075wb6d730ed7c9189f8@mail.gmail.com> <20070310161423.GA1256@seekingfire.com> <20070310193946.GA96514@xor.obsecurity.org> <20070311044033.GB1256@seekingfire.com> <20070311062637.GA1256@seekingfire.com> <20070318125635.N62476@maildrop.int.zabbadoz.net> <20070318154536.U20456@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 18, 2007 at 03:50:01PM +0100, Robert Watson wrote: > If using uid/gid firewall rules, make sure to read the pertinent man pages > regarding setting debug.mpsafenet=0 in loader.conf to avoid deadlocks. I am using firewall rules, with pf rather than ipfw, but I'm not using anything tied to user information. > This is only a workaround for the issue, and when debug.mpsafenet is > removed, this workaround will no longer be available. The > authors/maintainers of the various firewall packages need to correct these > problems or the lock order reversals (and associated deadlocks) will > persist. Interesting :-) -T
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070318192945.GB1264>