Date: Fri, 22 Oct 2004 09:20:04 +0100 (BST) From: "Matt Hamilton" <matth@netsight.co.uk> To: jesk@killall.org Cc: freebsd-current@freebsd.org Subject: Re: mysql super-smack test on FreeBSD 5.3-RC1 amd64 Message-ID: <61089.147.114.226.175.1098433204.squirrel@mail.testbed.netsight.co.uk> In-Reply-To: <32C33A5ACC16924A80AC1084@jesk.int.de.clara.net> References: <6.1.2.0.2.20041022154756.02b67090@202.179.0.80> <32C33A5ACC16924A80AC1084@jesk.int.de.clara.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Did you turned of HTT? > try to set "sysctl machdep.hlt_logical_cpus=1" and test again. > did you compile with linuxthreads or pthreads? You can't (according to the ports) compile LinuxThreads on non-i386 platforms. I am still trying to find out why python 2.3.4 will not compile and run its test suite on FreeBSD 5/AMD64. It runs for on i386, but not on AMD64, it just core dumps when doing anything stack-heavy when compiled with threading. The fact it works with i386 and not AMD64 leads me to believe it is a problem with FreeBSD, not python (works fine on -stable on i386 too). The normal tricks on increasing the stack size for pthreads doesn't seem to help at all. I've tried linking against -libpthread, -libkse and -libthr and all get the same results. I've not tried it with -RC1 yet, the latest was -B7. I'm not sure if this is related to your issues or not, but I just wanted to point out that I think there is a deeper issue with threads on FreeBSD and so it may affect stuff other than python. -Matt -- Matt Hamilton matth@netsight.co.uk Netsight Internet Solutions, Ltd. Business Vision on the Internet http://www.netsight.co.uk +44 (0)117 9090901 Web Design | Zope/Plone Development and Consulting | Co-location | Hosting
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?61089.147.114.226.175.1098433204.squirrel>