From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 18:20:28 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 46C9716A4D5 for ; Thu, 26 Aug 2004 18:20:28 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8D6943D1D for ; Thu, 26 Aug 2004 18:20:06 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id AFD9F72DD4; Thu, 26 Aug 2004 11:20:06 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id AD5A172DCB; Thu, 26 Aug 2004 11:20:06 -0700 (PDT) Date: Thu, 26 Aug 2004 11:20:06 -0700 (PDT) From: Doug White To: Garance A Drosihn In-Reply-To: Message-ID: <20040826111853.D37301@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 18:20:28 -0000 On Thu, 26 Aug 2004, Garance A Drosihn wrote: > >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 pinned this down yet, but I have determined that it is > not related to the USE_KQUEUE `make'. It is only happening if I do > several -j buildworlds in a row, and (at least so far) only if I > also have the folding-at-home client running as a background task. I guess I'll go run that client and beat up my testbox a bit :) I'm suspecting the data corruption issue isn't directly caused by the IPI fix, but rather it just unmasked an existing issue. -- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org