[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: named illegal instruction on i486
In article <lj5u1k$qsm$1%ger.gmane.org@localhost>,
Christos Zoulas <christos%astron.com@localhost> wrote:
>In article <69B2BF00-4BDB-4876-843E-CF0B9C5DCD4A%azeotrope.org@localhost>,
>Dave Huang <khym%azeotrope.org@localhost> wrote:
>>On Apr 22, 2014, at 6:43, Christos Zoulas <christos%astron.com@localhost>
>>> In article <20140422025233.086696b3.frank%phoenix.owl.de@localhost>,
>>> Frank Wille <frank%phoenix.owl.de@localhost> wrote:
>>>> The disassembly shows that the CPU fails on executing the instruction
>>>> "lock cmpxchg...", which is only available for Pentium CPUs and higher.
>>>> Any idea what went wrong? Is it a general problem in libc or was named
>>>> built for >=Pentium?
>>> Looks that way (our assembly files are written for >= pentium). Until
>>> that gets fixes, you can turn off NAMED_USE_PTHREADS.
>>I thought cmpxchg was available on the 486 (but not on the 386)...
>The easiest way is to comment out __HAVE_ATOMIC64_OPS in
>/usr/src/sys/arch/i386/include/types.h and rebuild everything.
That breaks rumpzfs which I ``fixed'' on head.
Main Index |
Thread Index |