Date: Thu, 26 Aug 2004 10:37:59 -0700 (PDT) From: Doug White <dwhite@gumbysoft.com> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch Message-ID: <20040826103652.F36995@carver.gumbysoft.com> In-Reply-To: <p0611040ebd4fe0bd637c@[128.113.24.47]> References: <20040822115345.Y94593@carver.gumbysoft.com> <p0611040ebd4fe0bd637c@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 23 Aug 2004, Garance A Drosihn wrote: > At 12:05 PM -0700 8/22/04, Doug White wrote: > >Hey folks, [...] please try this patch: > > > >http://people.freebsd.org/~dwhite/smp_rv_mtx.patch > > > >This patch avoids a deadlock between the smp_rendezvous() > >mechanism and TLB shootdowns via pmap by forcing them to > >share a mutex. > > I have completed a series of buildworlds with -j3 to -j10 with > no problem. I then started up a "folding at home" client, and > repeated the buildworlds. No panics, but in the second set I > did have one buildworld (-j9) which failed with four processes > apparently getting a "*** Signal 6". I am not sure what that > was about. Note that all these builds were done with a `make' > that was compiled to USE_KQUEUE , so maybe that's where the > Signal's came from. In any case, the machine is still running > fine, even after that heavy pounding. Signal 6 is SIGABRT, which is usually intentional. You'd have to check the output for a specific process that abended. I'd also have to scan the make code for any abort() calls. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040826103652.F36995>