From owner-freebsd-current@FreeBSD.ORG Wed Oct 26 06:46:24 2005 Return-Path: X-Original-To: freebsd-current@FreeBSD.org 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 DC67116A41F; Wed, 26 Oct 2005 06:46:24 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from nostrum.com (magus.nostrum.com [69.5.195.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31B3A43D45; Wed, 26 Oct 2005 06:46:24 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from [10.10.10.253] (hermes.nostrum.com [10.10.10.253]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id j9Q6kNLX084806 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 26 Oct 2005 01:46:23 -0500 (CDT) (envelope-from pckizer@nostrum.com) In-Reply-To: <20051025110453.L6720@fledge.watson.org> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> <20051019175020.S60849@fledge.watson.org> <20051025110453.L6720@fledge.watson.org> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <2E18CEAE-2A72-4387-B92E-DAED7CC7FACD@nostrum.com> Content-Transfer-Encoding: 7bit From: Philip Kizer Date: Wed, 26 Oct 2005 01:46:17 -0500 To: freebsd-current@FreeBSD.org X-Mailer: Apple Mail (2.734) Received-SPF: pass (nostrum.com: 10.10.10.253 is authenticated by a trusted mechanism) Cc: Robert Watson , John Baldwin Subject: Re: Problem remains with FreeBSD 6.0-RC1 as seen in RELENG_5 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 26 Oct 2005 06:46:25 -0000 On Oct 25, 2005, at 05:07, Robert Watson wrote: > There are a couple of possible sources, so if this is reproduceable > and you don't mind trying some diagnostic patches, I've attached a > first one below. This checks for the case where the looping in the > unp_gc() routine becomes unbounded due to a possible lack of > synchronization in the handling of marking and counting of > marking. It needs INVARIANTS to be compiled in to work; if it > fires, this will suggest an avenue to explore. OK, patch applied and it ran all day, finally hanging again. http://www.nostrum.com/hang/hang.trace-2005-10-26-0.txt Hopefully that's more of a help. Till later, Philip