Hi,
I'm running freebsd 8.1 (amd64).
I found that nearly all of my tasks status are "error while computing", with exit status 132, which means "cannot get process run time".
Below is part of my dmesg:
pid 63214 (milkyway_0.4_i686-p), uid 0: exited on signal 4 (core dumped)
pid 63215 (milkyway_0.4_i686-p), uid 0: exited on signal 4 (core dumped)
linux_sys_futex: unknown op 265
linux_sys_futex: unknown op 265
pid 68796 (milkyway_0.4_i686-p), uid 0: exited on signal 4 (core dumped)
pid 68797 (milkyway_0.4_i686-p), uid 0: exited on signal 4 (core dumped)
linux_sys_futex: unknown op 265
Exit signal 4 means "illegal instruction".
I think this may have something to do with the linux emulation layer?
Any suggestions will be appreciated.
/ 
Reply
Quote
Exit signal 4 means "illegal instruction".
Well I think the Linux 32 bit one was accidentally compiled with SSE2, but you say you're on 64 bit FreeBSD so that isn't be a problem. Does the x86_64 FreeBSD Linux layer actually work with 32 bit Linux executables? I would kind of expect it to work but I'm not sure. Is there a reason you aren't trying to run the x86_64 one?
linux_sys_futex: unknown op 265
I think this may have something to do with the linux emulation layer?
Apparently. I found this (quite recent too):http://www.listshow.net/201010/freebsd-emulation/6365-reduce-unknown-op-265-message-storm.html
I can try to maybe get it to work on FreeBSD. Does the N-body work for you, or is it the same thing? I would expect this clock thing to be used somewhere in the BOINC libraries.
/ Reply
Quote