From owner-freebsd-current@FreeBSD.ORG Thu Apr 30 19:27:49 2009 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95156106566B for ; Thu, 30 Apr 2009 19:27:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 70FF18FC20 for ; Thu, 30 Apr 2009 19:27:49 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 112B846B06; Thu, 30 Apr 2009 15:27:49 -0400 (EDT) Date: Thu, 30 Apr 2009 20:27:48 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: David Wolfskill In-Reply-To: <20090430155408.GX1387@albert.catwhisker.org> Message-ID: References: <20090430155408.GX1387@albert.catwhisker.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: Panic: witness_warn (r191682; shared rw udpinp (udpinp)...netinet6/udp6_usrreq.c:360) 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: Thu, 30 Apr 2009 19:27:49 -0000 On Thu, 30 Apr 2009, David Wolfskill wrote: > Build machine crashed on boot of r191682: > > ... > GEOM_LABEL: Label ufsid/48fa940b4445475f removed. > fxp0: link state changed to UP > suspending ithread with the following locks held: > shared rw udpinp (udpinp) r = 0 (0xc5ac4f3c) locked @ /usr/src/sys/netinet6/udp6_usrreq.c:360 > panic: witness_warn > cpuid = 1 > KDB: enter: panic > [thread pid 12 tid 100008 ] > Stopped at kdb_enter+0x3a: movl $0,kdb_why > db> > > I started to paste the output of "show witness" in here, but it got to be > sufficiently lengthy that I thought it better to save it for private mail or > a follow-up if it's really wanted. This falls into the category of "unlikely software bugs" -- is there any chance this machine is overheating or has memory problems? "show alllocks" would be helpful on general principle, though. Robert N M Watson Computer Laboratory University of Cambridge