From owner-freebsd-current@FreeBSD.ORG Thu Jul 7 10:04:48 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DB61F1065674; Thu, 7 Jul 2011 10:04:48 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id 72AA28FC18; Thu, 7 Jul 2011 10:04:48 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.4/8.14.4/ALCHEMY.FRANKEN.DE) with ESMTP id p67A4lif089729; Thu, 7 Jul 2011 12:04:47 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.4/8.14.4/Submit) id p67A4lar089728; Thu, 7 Jul 2011 12:04:47 +0200 (CEST) (envelope-from marius) Date: Thu, 7 Jul 2011 12:04:46 +0200 From: Marius Strobl To: KOT MATPOCKuH Message-ID: <20110707100446.GJ14797@alchemy.franken.de> References: <20110629134140.GF14797@alchemy.franken.de> <4E0B8F25.7090107@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: Doug Barton , FreeBSD Current Subject: Re: named crashes on assertion in rbtdb.c on sparc64/SMP 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, 07 Jul 2011 10:04:48 -0000 On Thu, Jul 07, 2011 at 01:46:23PM +0400, KOT MATPOCKuH wrote: > I updated system to r223824 and got named patched to 9.6.-ESV-R4-P3, > but problem is still exists: > 07-Jul-2011 13:24:22.765 general: > /usr/src/lib/bind/dns/../../../contrib/bind9/lib/dns/rbtdb.c:1622: > REQUIRE(prev > 0) failed > 07-Jul-2011 13:24:22.781 general: exiting (due to assertion failure) > > How can I find root cause of the problem? > >From your description it's unclear whether you've built BIND with or without sparc64_isc_disable_atomic.diff. If it was built without that patch please give it a try. If you had applied it then this apparently is a generic bug in BIND and unrelated to the MD atomic implementation and I don't know how to proceed in order to get that fixed. Hopefully Doug can help you in that case. Marius