From owner-freebsd-current@FreeBSD.ORG Thu Aug 26 18:16:04 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 168D216A4CE for ; Thu, 26 Aug 2004 18:16:04 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C58C43D41 for ; Thu, 26 Aug 2004 18:16:03 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp3.server.rpi.edu (8.13.0/8.13.0) with ESMTP id i7QIG1UL030952; Thu, 26 Aug 2004 14:16:02 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040826103652.F36995@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> <20040826103652.F36995@carver.gumbysoft.com> Date: Thu, 26 Aug 2004 14:16:00 -0400 To: Doug White From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) 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:16:04 -0000 At 10:37 AM -0700 8/26/04, Doug White wrote: >On Mon, 23 Aug 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. > >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. This combination is not something that I have done before, so I no way of knowing if it is related to the IPI-fix that you wrote. I do know that I have not been able to trigger the panic that I got before, even though I have been hammering the machine MUCH harder than I usually do. The "Signal 6"s seem to be hitting various gcc processes, and I did notice that gcc has plenty of calls to abort() in it. At the moment I do not have time to pursue this any farther. (Our first day of classes here @RPI is next Monday, and I have about a hundred things that need to get done before then!). -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu