Date: Thu, 26 Aug 2004 11:20:06 -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: <20040826111853.D37301@carver.gumbysoft.com> In-Reply-To: <p0611041fbd53d77e3b9f@[128.113.24.47]> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> <p0611041fbd53d77e3b9f@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040826111853.D37301>