For some months now, I've noticed that Astropulse work-units give a computation error almost immediately. I had assumed that someone was aware, but maybe they are not, so this is a "heads up".

Here are some of my latest results..

http://setiathome.berkeley.edu/result.php?resultid=2221711451
http://setiathome.berkeley.edu/result.php?resultid=2221682555

The links should be all you need to discover my environment etc.

For some months now, I've noticed that Astropulse work-units give a computation error almost immediately. I had assumed that someone was aware, but maybe they are not, so this is a "heads up".

Here are some of my latest results..

http://setiathome.berkeley.edu/result.php?resultid=2221711451
http://setiathome.berkeley.edu/result.php?resultid=2221682555

The links should be all you need to discover my environment etc.

Yes, that seems to be the rule rather than the exception when running AP on Linux. I know there was a solution to that, and I'm sure someone who knows about Linux, will help you solve that issue.

The solution is to run the Optimised Linux apps, they are a lot faster and a lot less prone to erroring out, check out Arkayn's site for downloads:

Crunchers Anonymous Downloads

Be aware that once you go onto Anonymous Platform, the Setiathome apps won't get updated by the project, you'll have to do that yourself when new Optimised apps are available, or by reverting back to the Stock apps.
(we're probably only a few months away from the Rollout of Setiathome v7 and Astropulse v6)

Claggy

exit139

Here is a link that has info on exit 139 for linux.

---

[/quote]

Old James

This is happening for years now...

x86_64 stock version of Linux AP is broken and sigsegvs on any semi-recent glibc.
You probably don't have (all) 32-bit compatibility libs (such as glibc) and 32-bit version cannot be run (which I think is preferred by the scheduler for Linux).

Shame that admins don't at least remove the 64-bit version. It's 8 MBs of wasted bandwidth.
Don't they run any statistics, checking for errors/invalid counts per platform ??? Like they do at Einstein.

Anyway, run the optimized applications, as already suggested.
They are more than 2x faster!

---

Thanks for all the replies. I'll investigate the optimised versions.

I had an issue with that way back when we went from AP_v5 to AP_v505. All of my tasks would instantly error out with a segment violation. The solution was to upgrade my GLIBC to at least 3.6, I believe it was, as I only had something like 3.1 at the time.

I forget the full details, but bottom line is it looks to me like a GLIBC issue, based on my past experience.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Thanks for all the replies. I'll investigate the optimised versions.

You may find some useful discussion here:
http://setiathome.berkeley.edu/forum_thread.php?id=66123

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

I notices that I got "signal 11" when suspend my computer or I hit the snooze button in boinc manager, computing is without problem until one of this event happened, maybe some other comes. I'm runing boinc v. 6.12.42 on Gentoo 32bit.

Personally I wish that AP's were stopped from being given to Linux hosts all together as I've only ever seen 1 Linux host that returns good results, all the rest have just trashed them, and as a result this impacts on the connection due to resends (1 AP that I did recently was sent out 7 times because 4 separate Linux hosts trashed it, 1 Win machine timed out on it, before it was finally put to rest.

Cheers.

---

mine always does because I use the optimized apps. prior to the Opt app install the AP's were always trashed. Thanks again to the Lunatics folks for their diligent work

---

In a rich man's house there is no place to spit but his face.
Diogenes Of Sinope