From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 18:17:37 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 8BCEF16A4CE; Mon, 23 Aug 2004 18:17:37 +0000 (GMT) Received: from smtp3.server.rpi.edu (smtp3.server.rpi.edu [128.113.2.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 357D043D1F; Mon, 23 Aug 2004 18:17:37 +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 i7NIHVsM019619; Mon, 23 Aug 2004 14:17:32 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20040822115345.Y94593@carver.gumbysoft.com> References: <20040822115345.Y94593@carver.gumbysoft.com> Date: Mon, 23 Aug 2004 14:17:30 -0400 To: Doug White , freebsd-current@freebsd.org From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) 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: Mon, 23 Aug 2004 18:17:37 -0000 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. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu