From owner-freebsd-current@FreeBSD.ORG  Fri Jul  8 19:32:39 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 DDA80106566C;
	Fri,  8 Jul 2011 19:32:39 +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 536068FC0C;
	Fri,  8 Jul 2011 19:32:37 +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
	p68JWaZR098053; Fri, 8 Jul 2011 21:32:36 +0200 (CEST)
	(envelope-from marius@alchemy.franken.de)
Received: (from marius@localhost)
	by alchemy.franken.de (8.14.4/8.14.4/Submit) id p68JWar1098052;
	Fri, 8 Jul 2011 21:32:36 +0200 (CEST) (envelope-from marius)
Date: Fri, 8 Jul 2011 21:32:36 +0200
From: Marius Strobl <marius@alchemy.franken.de>
To: KOT MATPOCKuH <matpockuh@gmail.com>
Message-ID: <20110708193236.GB95673@alchemy.franken.de>
References: <BANLkTi=_PP=tvLUbXiTE1DT4tMirLRUY+w@mail.gmail.com>
	<20110629134140.GF14797@alchemy.franken.de>
	<4E0B8F25.7090107@FreeBSD.org>
	<CALmdT0V2Fzf8mcYRzYzsu5XkauuxGaF4dxFPR7ZHr-FH2a_5bQ@mail.gmail.com>
	<20110707100446.GJ14797@alchemy.franken.de>
	<CALmdT0VFC7kBxaEqLuFVWkLk3o2hLe29tsx3dgn17tuTNaTRLA@mail.gmail.com>
	<20110707154958.GK14797@alchemy.franken.de>
	<CALmdT0V_MG7abrGyp-JodsP3Bun-C863VGqTkSAdewnFbiA-+g@mail.gmail.com>
	<20110708181102.GA95673@alchemy.franken.de>
	<CALmdT0UnAkjNK2MScU8rjMQ+ieqUtER6FrEwaDCiQ3cynKfBQw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CALmdT0UnAkjNK2MScU8rjMQ+ieqUtER6FrEwaDCiQ3cynKfBQw@mail.gmail.com>
User-Agent: Mutt/1.4.2.3i
Cc: Doug Barton <dougb@freebsd.org>,
	FreeBSD Current <freebsd-current@freebsd.org>
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
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2011 19:32:39 -0000

On Fri, Jul 08, 2011 at 11:17:20PM +0400, KOT MATPOCKuH wrote:
> 2011/7/8 Marius Strobl <marius@alchemy.franken.de>:
> 
> > Please try the following:
> > a) Instead of the base BIND use the dns/bind96 port. The native build
> > ? of the latter defaults to not using the ISC atomic implementation
> > ? on sparc64 (and arm) and should properly enable the alternative. I
> > ? can at least start named from bind96-9.6.3.1.ESV.R4.3 with the default
> > ? configuration on -CURRENT without problems.
> dns/bind96? Why not bind98?

In order to have a result which can be compared with the base BIND.
Whether bind98 works or works without the ISC atomic operations says
nothing about the bind96 port or the base version.

> As I see dns/bind98 configures without atomic swap operations.
> I will try to use dns/bind98 at first :)
> 
> > b) Revert the above patch and try the base bind with the following
> > ? (third) patch:
> > ? http://people.freebsd.org/~marius/sparc64_isc_atomic.h.diff2
> > ? That one adds the memory barriers required for reference counting
> > ? albeit in a sledgehammer-like fashion as the ISC atomic API doesn't
> > ? allow to distinguish between acquire and release semantics.
> 
> Hmmm... With this patch build fails:

Oops, sorry, I forgot to revert the previous patch when test-compiling.
Please re-fetch sparc64_isc_atomic.h.diff2 and try again.

Marius