GNU/Linux S5R3 App 4.20 available for Beta test
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4330
Credit: 251448193
RAC: 36212
29 Nov 2007 14:47:32 UTC
Topic 193352
(moderation:
A new Linux App is available from our Beta Test page.
This App should fix the bug that caused a SEGV (signal 11) when the App couldn't wirte a checkpoint. Speed should be comparable to that of the 4.16.
Happy testing!
BM
BM
GNU/Linux S5R3 App 4.20 available for Beta test
)
I've just set up another P-III box, and installed this on it. We'll see how it goes.
i threw the new app on one of
)
i threw the new app on one of my p3 boxes and it killed the units that were in progress. ugh.
Yes, switching apps if you
)
Yes, switching apps if you have results running is very tricky and can go wrong if you make a mistake. The safe option would be to let your WUs finish before the update.
At least updating from the
)
At least updating from the earlier 4.16 app should be fine, at least it worked for me. without any workunit loss.
I think I'll skip this time;
)
I think I'll skip this time; although I don't get computation errors for each and every WU any more the shared memory problem on my laptop still doesn't seem to be sorted out completely and I don't want to mess up results by running a beta app on a not-quite-solid system...
I did a closer check and
)
I did a closer check and found out the latest computation errors all seem to have been signal 11 (so, nothing to do with my host) and my other projects are running fine, so I decided to risk beta testing. Hopefully it will work out.
Somehow, completion time seems to be way off atm, they start with 39 hours while half would be about realistic. No idea why. Apart from that, there don't seem to be any problems.
This App fixes at least one
)
This App fixes at least one reason of the "signal 11", it's faster than the 4.02 and hasn't any really obvious bugs, so I made it official. If it should really make things worse than they are with 4.02, I'll deprecate it tomorrow.
BM
BM
resultid=89392342 valid on
)
resultid=89392342 valid on Pentium III / CC 4.19 (command line) but didn't report CPU time. Not a problem as of the fixed credits.
My first WU with 4.20
)
My first WU with 4.20 validated fine, two more are crunching apparently without problems. No way to say anything about performance, though, those WUs are just too different and I crashed rather too many to have a decent comparison.
After upgrading my kernel I
)
After upgrading my kernel I lost a 4.20 workunit with the stderr out message 'Input file missing or invalid'
http://einsteinathome.org/task/89403952