Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Apr 2006 19:25:33 -0400
From:      Kris Kennaway <kris@obsecurity.org>
To:        David Xu <davidxu@freebsd.org>
Cc:        Daniel Eischen <deischen@freebsd.org>, Kris Kennaway <kris@obsecurity.org>, freebsd-sparc64@freebsd.org, freebsd-threads@freebsd.org
Subject:   Re: pthread_mutex_timedlock on sparc64
Message-ID:  <20060420232533.GA32046@xor.obsecurity.org>
In-Reply-To: <200604210717.22947.davidxu@freebsd.org>
References:  <20060418204240.GA69833@xor.obsecurity.org> <20060420074713.Y52948@hades.admin.frm2> <20060420182331.GA26174@xor.obsecurity.org> <200604210717.22947.davidxu@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 21, 2006 at 07:17:22AM +0800, David Xu wrote:
> On Friday 21 April 2006 02:23, Kris Kennaway wrote:
>=20
> > 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
>=20
> 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=3D0xe85a6000 %o7=3D0xc02f3b08 --
> 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=3D0x40348e7c --

It may be a deeper vm problem.

Kris

--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFESBhtWry0BWjoQKURAt5YAJ0dj2z9w2Ckg0XVxt2pdfx+P28gNgCg4YnC
59a5tyrYzLWjzrzJ9PdlpaA=
=K6fC
-----END PGP SIGNATURE-----

--/04w6evG8XlLl3ft--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060420232533.GA32046>