From owner-freebsd-bugs@FreeBSD.ORG Thu Sep 30 21:10:25 2004 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E146216A4D0 for ; Thu, 30 Sep 2004 21:10:24 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 624BA43D46 for ; Thu, 30 Sep 2004 21:10:10 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 090BD51491; Thu, 30 Sep 2004 14:10:42 -0700 (PDT) Date: Thu, 30 Sep 2004 14:10:42 -0700 From: Kris Kennaway To: Henrik W Lund Message-ID: <20040930211042.GA13198@xor.obsecurity.org> References: <200409221600.i8MG0jNF088018@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200409221600.i8MG0jNF088018@freefall.freebsd.org> User-Agent: Mutt/1.4.2.1i cc: freebsd-bugs@FreeBSD.org Subject: Re: kern/71714: Fatal error 'Spinlock called when not threaded.' at line 83 in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 0) (BETA4) X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Sep 2004 21:10:25 -0000 On Wed, Sep 22, 2004 at 04:00:45PM +0000, Henrik W Lund wrote: > The following reply was made to PR kern/71714; it has been noted by GNATS. > > From: Henrik W Lund > To: freebsd-gnats-submit@FreeBSD.org, lsi@samtel.ru > Cc: > Subject: Re: kern/71714: Fatal error 'Spinlock called when not threaded.' > at line 83 in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = > 0) (BETA4) > Date: Wed, 22 Sep 2004 17:48:14 -0700 > > Running FreeBSD/amd64 5.3-BETA5 and I can confirm the problem. It seems > not related to the building of the qt port, but rather to libpthread. > Mozilla, for one, produces the same error message, as do some other > builds as well. > > Libmapping pthread to libc_r is a workaround, but shouldn't this work > for pthread too? This error is well-known and has been discussed on mailing lists dozens of times. Rebuild all your ports, or search the archives for extensive discussion. Kris