From owner-freebsd-current@FreeBSD.ORG Tue Oct 25 08:21:52 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 0519A16A41F; Tue, 25 Oct 2005 08:21:52 +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 8BDC743D48; Tue, 25 Oct 2005 08:21:51 +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 j9P8LoiK086877 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Tue, 25 Oct 2005 03:21:50 -0500 (CDT) (envelope-from pckizer@nostrum.com) In-Reply-To: <20051019175020.S60849@fledge.watson.org> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> <20051019175020.S60849@fledge.watson.org> Mime-Version: 1.0 (Apple Message framework v734) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Philip Kizer Date: Tue, 25 Oct 2005 03:21:48 -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 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: Tue, 25 Oct 2005 08:21:52 -0000 On Oct 19, 2005, at 11:54, Robert Watson wrote: > This appears to be a problem with file descriptor passing and > garbage collection. I've seen one report of a lock order reversal > along these lines, but it was not believed to be symptomatic of an > actual hang, just an architectural issue. This could be a sign > that we need to address the source of the reversal, although it > sounds like you don't get a reversal > warning? > > Could I have you try the following DDB commands also: > > show alllocks > traceall OK, this is a new hang with almost all I had before (looks like I did forgot the "print sysctllock", will I need to be sure and include it for a complete diagnosis?) and those two as well: http://www.nostrum.com/hang/hang.trace-2005-10-25-0.txt [Or would you prefer I include it directly rather than sparing the list the output?] Thank you, Philip