From owner-freebsd-current@FreeBSD.ORG Wed Oct 19 21:32:03 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 8578D16A41F; Wed, 19 Oct 2005 21:32:03 +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 13CA543D66; Wed, 19 Oct 2005 21:32:02 +0000 (GMT) (envelope-from pckizer@nostrum.com) Received: from [165.91.250.64] (magus.tamu.edu [165.91.250.64]) (authenticated bits=0) by nostrum.com (8.12.11/8.12.11) with ESMTP id j9JLW06O037214 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Wed, 19 Oct 2005 16:32:01 -0500 (CDT) (envelope-from pckizer@nostrum.com) In-Reply-To: <200510191533.26590.jhb@freebsd.org> References: <200510191623.j9JGNSfr007356@magus.nostrum.com> <200510191423.42922.jhb@freebsd.org> <200510191533.26590.jhb@freebsd.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: Wed, 19 Oct 2005 16:31:59 -0500 To: freebsd-current@freebsd.org X-Mailer: Apple Mail (2.734) Received-SPF: pass (nostrum.com: 165.91.250.64 is authenticated by a trusted mechanism) Cc: 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, 19 Oct 2005 21:32:03 -0000 On Oct 19, 2005, at 14:33, John Baldwin wrote: > You just have to add 'hptlock' to the list in sys/kern/subr_witness.c. > Something like this: Gotcha, that works just fine and the new kernel with WITNESS and INVARIANTS is now in place. It will be low-usage while I'm out of town, so it will probably be early next week when I can get the DDB output from the next hang. -philip