From owner-freebsd-ports@FreeBSD.ORG Sat Nov 13 22:51:54 2004 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1E13316A4CE for ; Sat, 13 Nov 2004 22:51:54 +0000 (GMT) Received: from smz.com.ua (smz.com.ua [193.138.84.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id EC05143D46 for ; Sat, 13 Nov 2004 22:51:52 +0000 (GMT) (envelope-from sla@smz.com.ua) Received: from mailhub (localhost.smz.com.ua [127.0.0.1]) by localhost (Postfix) with ESMTP id E1D60FDD2 for ; Sun, 14 Nov 2004 00:52:27 +0200 (EET) Received: from localhost (localhost.smz.com.ua [127.0.0.1]) by localhost (Postfix) with ESMTP id 6A203FDA1; Sun, 14 Nov 2004 00:52:25 +0200 (EET) Received: from smz.com.ua ([127.0.0.1]) by localhost (smz.com.ua [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03525-10; Sun, 14 Nov 2004 00:52:23 +0200 (EET) Received: from deep.msu0 (unknown [192.168.0.129]) by smz.com.ua (Postfix) with ESMTP id 5AB3AFD9D; Sun, 14 Nov 2004 00:52:22 +0200 (EET) From: Slava To: freebsd-ports@freebsd.org Date: Sun, 14 Nov 2004 00:51:41 +0200 User-Agent: KMail/1.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200411140051.42438.sla@smz.com.ua> X-Virus-Scanned: by amavisd-clamav at smz.com.ua cc: freebsd-current@freebsd.org cc: Andrew Moran Subject: Re: seemingly unfixable Spinlock error under 5.3? X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Nov 2004 22:51:54 -0000 more /usr/src/UPDATING /20040303 man libmap.conf > I made the jump from 5.21 to 5.3 earlier and started getting the > infamous "Fatal error 'Spinlock called when not threaded.' at line 83 > in file /usr/src/lib/libpthread/thread/thr_spinlock.c (errno = 2)" > everytime I ran gnucash. > I asked the freebsd-questions list but have gotten no response. So > in desperation, I'm broadening my quest. I don't want to reinstall > the server from scratch if there is another way to fix this error. > Could there be something in my kernel configuration causing this? I > can't find a reference to libc_r or libkse *anywhere*. :/ > > Does anyone have any ideas for me to try? Thank you for your time. > > --And > > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" > -- Vyacheslav Bocharov VB29-UANIC