Date: Sat, 13 Nov 2004 15:11:00 -0800 From: Andrew Moran <amoran@forsythia.net> To: Sean McNeil <sean@mcneil.com> Cc: freebsd-ports@freebsd.org Subject: Re: seemingly unfixable Spinlock error under 5.3? Message-ID: <4867FB65-35C9-11D9-9133-000D93B1D960@forsythia.net> In-Reply-To: <1100387012.11089.3.camel@server.mcneil.com> References: <E048F96D-35BD-11D9-B3D5-000D93B1D960@forsythia.net> <200411140051.42438.sla@smz.com.ua> <103957F0-35C7-11D9-9133-000D93B1D960@forsythia.net> <1100387012.11089.3.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
As I stated in my original message, I did do a portupgrade -fR gnucash.
I've also recompiled all m ports using portupgrade -fa. neither
have alleviated the problem.
I'm beginning to suspect I have some kind of kernel option throwing me
off. It's very frustrating.
--Andy
On Nov 13, 2004, at 3:03 PM, Sean McNeil wrote:
> On Sat, 2004-11-13 at 14:55 -0800, Andrew Moran wrote:
>> I have tried mapping libc_r to libpthread using libmap.conf. it does
>> not seem to have any effect.. Which doesn't surprise me too much
>> since
>> I can't find anything actually linked to libc_r anyway.
>> :(
>
> You should check to see if gnucash is using any plug-ins or shared
> libraries. You need to check everything gnucash is using. The easiest
> thing would be to do a
>
> portupgrade -fR gnucash
>
> I just bit the bullet and recompiled all my ports when that happened to
> me.
>
> For the libmap.conf you should check that it is working properly. Try
> mapping libpthread.so to libthr.so and do an ldd to verify.
>
>> On Nov 13, 2004, at 2:51 PM, Slava wrote:
>>
>>> 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
>>> _______________________________________________
>>> 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"
>>
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to
>> "freebsd-current-unsubscribe@freebsd.org"
>>
_______________________________________________
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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4867FB65-35C9-11D9-9133-000D93B1D960>