From owner-freebsd-current@FreeBSD.ORG  Fri Mar  4 02:38:09 2005
Return-Path: <owner-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 2CF1C16A4CE; Fri,  4 Mar 2005 02:38:09 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id AF5E343D5A; Fri,  4 Mar 2005 02:38:08 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	j242c7aU011258;	Thu, 3 Mar 2005 21:38:07 -0500 (EST)
Date: Thu, 3 Mar 2005 21:38:07 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: David Xu <davidxu@freebsd.org>
In-Reply-To: <4227C741.9040400@freebsd.org>
Message-ID: <Pine.GSO.4.43.0503032137320.4088-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: alc@freebsd.org
cc: freebsd-current@freebsd.org
cc: Robert Watson <rwatson@freebsd.org>
cc: peter@freebsd.org
Subject: Re: FreeBSD 5.3 crash (core with debug symbols available)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
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, 04 Mar 2005 02:38:09 -0000

On Fri, 4 Mar 2005, David Xu wrote:

> Scott Long wrote:
>
> >
> > Can you provide a reference for the umtx problem?  There might be a
> > reasonable solution.
> >
> I have put umtx_q on stack, and link it into global umtx hash, as you said,
> I have to use malloc/free.

Just allocate it once and attach it to the thread.

-- 
DE