From owner-freebsd-threads@FreeBSD.ORG  Thu Apr 20 23:47:54 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 6A01816A404;
	Thu, 20 Apr 2006 23:47:54 +0000 (UTC)
	(envelope-from davidxu@freebsd.org)
From: David Xu <davidxu@freebsd.org>
To: Kris Kennaway <kris@obsecurity.org>
Date: Fri, 21 Apr 2006 07:47:47 +0800
User-Agent: KMail/1.8.2
References: <20060418204240.GA69833@xor.obsecurity.org>
	<200604210717.22947.davidxu@freebsd.org>
	<20060420232533.GA32046@xor.obsecurity.org>
In-Reply-To: <20060420232533.GA32046@xor.obsecurity.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="gb2312"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200604210747.47903.davidxu@freebsd.org>
Cc: Daniel Eischen <deischen@freebsd.org>, freebsd-sparc64@freebsd.org,
	freebsd-threads@freebsd.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:47:54 -0000

On Friday 21 April 2006 07:25, Kris Kennaway wrote:

> > Do you have WITNESS backtrace ? I don't have sparc hardware.
>
> Actually I mis-remembered a bit.
>
> > panic: _mtx_lock_sleep: recursed on non-recursive mutex system map @
> > ../../../vm/vm_map.c:2993 panic() at panic+0x164
> > _mtx_lock_sleep() at _mtx_lock_sleep+0x40
> > _mtx_lock_flags() at _mtx_lock_flags+0x98
> > _vm_map_lock_read() at _vm_map_lock_read+0x1c
> > vm_map_lookup() at vm_map_lookup+0x1c
> > vm_fault() at vm_fault+0x68
> > trap_pfault() at trap_pfault+0x1a8
> > trap() at trap+0x2b0
> > -- fast data access mmu miss tar=0xe85a6000 %o7=0xc02f3b08 --
> > vm_map_entry_splay() at vm_map_entry_splay+0x10
> > vm_map_find() at vm_map_find+0x34
> > kmem_alloc_nofault() at kmem_alloc_nofault+0x44
> > vm_thread_new() at vm_thread_new+0x44
> > thread_init() at thread_init+0x8
> > slab_zalloc() at slab_zalloc+0x264
> > uma_zone_slab() at uma_zone_slab+0x1ac
> > uma_zalloc_bucket() at uma_zalloc_bucket+0x1b4
> > uma_zalloc_arg() at uma_zalloc_arg+0x398
> > thread_alloc() at thread_alloc+0x18
> > create_thread() at create_thread+0x78
> > thr_new() at thr_new+0x64
> > syscall() at syscall+0x2dc
> > -- syscall (455, FreeBSD ELF64, thr_new) %o7=0x40348e7c --
>
> It may be a deeper vm problem.
>
> Kris

I think it is a bug of some VM allocation code, it probably should be
reported on -CURRENT.

David Xu