From owner-freebsd-current@FreeBSD.ORG Tue Aug 24 02:28:50 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 E3FEC16A4CE; Tue, 24 Aug 2004 02:28:50 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E0A643D45; Tue, 24 Aug 2004 02:28:50 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.11/8.12.11) id i7O2SoWI006182; Mon, 23 Aug 2004 21:28:50 -0500 (CDT) (envelope-from dan) Date: Mon, 23 Aug 2004 21:28:50 -0500 From: Dan Nelson To: Garance A Drosihn Message-ID: <20040824022849.GE36920@dan.emsphone.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040824005149.GG77326@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 5.3-BETA1 X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i 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: Tue, 24 Aug 2004 02:28:51 -0000 In the last episode (Aug 23), Garance A Drosihn said: > At 8:51 PM -0400 8/23/04, Brian Fundakowski Feldman wrote: > >On Mon, Aug 23, 2004, Garance A Drosihn wrote: > > > [...] 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. > > > >Are you watching system temperatures? > > I doubt that's a problem right now. Right now my office is pretty > chilly, and it was even cooler last night while these were running. > This is the first time I've seen these "*** Signal 6"s, and this is > also the first time I've tried a USE_KQUEUE verison of `make'. And > while the make-related processes died with the signal's, none of the > other processes on the system had any problems. (including the > folding-at-home client which is still running on the machine). Signal 6 (SIGABRT) is usually caused by an assert or other deliberate action. Scroll back up in the log and see if you can find any error messages. -- Dan Nelson dnelson@allantgroup.com