Date: Mon, 19 Mar 2007 14:46:07 +0200 From: Ian FREISLICH <ianf@clue.co.za> To: Julian Elischer <julian@elischer.org>, freebsd-current@freebsd.org, Robert Watson <rwatson@FreeBSD.org> Subject: Re: Experiencing hangs on SMP box with no console messages given for clues. Details inside. Message-ID: <E1HTHFX-0005Zk-Q9@clue.co.za> In-Reply-To: Message from Ian FREISLICH <ianf@clue.co.za> of "Mon, 19 Mar 2007 13:33:48 %2B0200." <E1HTG7Y-0005RL-43@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Ian FREISLICH wrote: > Julian Elischer wrote: > > Robert Watson wrote: > > > > > > On Sun, 18 Mar 2007, Bjoern A. Zeeb wrote: > > > > > >> On Sun, 11 Mar 2007, Tillman Hodgson wrote: > > >> > > >>> On Sat, Mar 10, 2007 at 10:40:33PM -0600, Tillman Hodgson wrote: > > >>>> Shouldn't take more than a day or two to get the info requested in > > >>>> 11.9. > > >>> > > >>> As it turns out, a few hours. > > >>> > > >>> After capturing the information below I ran `panic`. While booting, > > >>> the following lock messages came up -- I thought it might be related > > >>> so I'll post it here: > > > > > > 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. 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. > > > > I actually have some work on this in an experimental branch.. > > it removes the requirement for users of ipfw to hold a lock on it > > by making the firewall table an array rather than a lined list and then > > using a read-copy-replace write semantic with reference conts on the array.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1HTHFX-0005Zk-Q9>