From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 17:55:00 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0969A16A4CE for ; Thu, 26 Aug 2004 17:55:00 +0000 (GMT) Received: from freebee.digiware.nl (dsl390.iae.nl [212.61.63.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id AC82A43D1D for ; Thu, 26 Aug 2004 17:54:58 +0000 (GMT) (envelope-from wjw@withagen.nl) Received: from [212.61.27.71] (dual [212.61.27.71]) by freebee.digiware.nl (8.12.10/8.12.10) with ESMTP id i7QHsuEg066642; Thu, 26 Aug 2004 19:54:56 +0200 (CEST) (envelope-from wjw@withagen.nl) Message-ID: <412E23F0.1010006@withagen.nl> Date: Thu, 26 Aug 2004 19:54:56 +0200 From: Willem Jan Withagen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug White References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> In-Reply-To: <20040826103652.F36995@carver.gumbysoft.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: PLEASE TEST: IPI deadlock avoidance patch X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Aug 2004 17:55:00 -0000 Doug White wrote: >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. > > I have not given it much attention yet, since I'm bussy doing other things right now. But on my dual AMD64 box compiling the current 5.3 Beta generated also 'Abort Trap' while doing a buildworld -j 32. Compiling without -j worked fine, and now I'm at 5.3 B1, so I can test again. It ws running a 5.3B1 kernel. I'll let you know if the problem persists --WjW