From owner-freebsd-threads@FreeBSD.ORG  Thu Apr 20 23:17:29 2006
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
X-Original-To: freebsd-threads@freebsd.org
Delivered-To: freebsd-threads@freebsd.org
Received: from localhost.my.domain (localhost [127.0.0.1])
	by hub.freebsd.org (Postfix) with ESMTP id 240BD16A402;
	Thu, 20 Apr 2006 23:17:29 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
From: David Xu <davidxu@freebsd.org>
To: freebsd-threads@freebsd.org
Date: Fri, 21 Apr 2006 07:17:22 +0800
User-Agent: KMail/1.8.2
References: <20060418204240.GA69833@xor.obsecurity.org>
	<20060420074713.Y52948@hades.admin.frm2>
	<20060420182331.GA26174@xor.obsecurity.org>
In-Reply-To: <20060420182331.GA26174@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604210717.22947.davidxu@freebsd.org>
Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-sparc64@freebsd.org,
	Kris Kennaway <kris@obsecurity.org>
Subject: Re: pthread_mutex_timedlock on sparc64
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2006 23:17:29 -0000

On Friday 21 April 2006 02:23, Kris Kennaway wrote:

> Hopefully David or someone will be able to look at the WITNESS panics
> from libthr on sparc soon.  Then we can make libthr the default on
> FreeBSD 6.x as well.
>
> In the meantime, you might be able to force the port to use libthr on
> 5.x/6.x, but this may not work since you typically encounter problems
> if different thread libraries are mixed in the same binary.  If not,
> the port should probably be marked BROKEN on sparc/5.x and 6.x until
> the change can be made.
>
> Kris

Do you have WITNESS backtrace ? I don't have sparc hardware.

David Xu