From owner-freebsd-current@FreeBSD.ORG Sat Oct 29 16:01:29 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 3298316A41F for ; Sat, 29 Oct 2005 16:01:29 +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 AED0943D48 for ; Sat, 29 Oct 2005 16:01:28 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from [10.10.10.252] (hermes-10bt.nostrum.com [10.10.10.252]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id j9TG1Ror019898 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO) for ; Sat, 29 Oct 2005 11:01:27 -0500 (CDT) (envelope-from pckizer@nostrum.com) Mime-Version: 1.0 (Apple Message framework v734) In-Reply-To: <33E53AA7-2A01-4BBE-9674-8F54E008D0A8@nostrum.com> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> <20051019175020.S60849@fledge.watson.org> <20051025110453.L6720@fledge.watson.org> <2E18CEAE-2A72-4387-B92E-DAED7CC7FACD@nostrum.com> <33E53AA7-2A01-4BBE-9674-8F54E008D0A8@nostrum.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <0906B09C-B5A2-402E-BF39-57EBB20B2D4F@nostrum.com> Content-Transfer-Encoding: 7bit From: Philip Kizer Date: Sat, 29 Oct 2005 11:01:21 -0500 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.734) Received-SPF: pass (nostrum.com: 10.10.10.252 is authenticated by a trusted mechanism) 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: Sat, 29 Oct 2005 16:01:29 -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. Well, it's been a few days since the last time I heard from anyone that had been helping me with this and I only recall seeing one diagnostic patch to apply (that does not seem to have been triggered in subsequent hangs). Have there been any more patches I've missed that would help either the problem or diagnostics? With that, I had another pair of examples last night again, one for each version of the OS: http://www.nostrum.com/hang/hang.RELENG_6-trace-2005-10-29-0.txt http://www.nostrum.com/hang/hang.RELENG_5-trace-2005-10-29-0.txt Any other suggestions or pointers on how to identify this livelock? Thank you, Philip