GNU/Linux S5R3 App 4.24 available for Beta test
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4312
Credit: 250267775
RAC: 35690
14 Jan 2008 5:11:07 UTC
Topic 193438
(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 BOINC Core Client became unresponsive (e.g. due to network access / problems).
This "standard" (non-SSE) App has the "linear SIN/COS" code working (many thanks to Akos and Bikeman) and should thus be somewhat faster than the 4.20.
We (Einstein@home and BOINC) are migrating to a new way of doing the graphics (actually BOINC has, I'm still working on Apps for Einstein@home). In the present state I couldn't get the "old-style" graphics to work, but I guess not many Linux users will look at it anyway. The next App release should have "APIv6 graphics".
Please test and report!
BM
BM
GNU/Linux S5R3 App 4.24 available for Beta test
)
I extracted this package to my project directory, but there were only two files in it contrary to the package description in the Linux section of the Beta Test Page. The md5sum came out right, but when I started the BOINC client back up, I got a message about a missing .so file.
Mon 14 Jan 2008 01:45:17 AM CST||file projects/einstein.phys.uwm.edu/einstein_S5R3_4.24_i686-pc-linux-gnu.so not found
Is this a problem, or is it even necessary without the graphics enabled? I have EAH_NO_GRAPHICS in the BOINC directory anyway, so if it's graphics related, then no harm anyway.
RE: I extracted this
)
Not a problem, the *.so files of the Linux apps contain the graphics code. This beta doesn't include graphics support, see Bernd's initial message as to why it was dropped for this particular built of the app.
Happy crunching
Bikeman
Just installed the Beta app
)
Just installed the Beta app on my laptop. I daresay if that box won't produce signal 11s it can't be done :-D
I installed the new app 4.24,
)
I installed the new app 4.24, the previously running task was resent and restarted from the beginning. No work was lost!
RE: I extracted this
)
Sorry, my fault (typical OOC error). The app_info.xml listed a einstein_S5R3_4.24_i686-pc-linux-gnu.so file. I updated the app_info.xml, the archive, the md5sum and the instructions on the webpage.
Thanks for reporting this.
BM
BM
RE: Sorry, my fault
)
That's what we're here for! My 4.14 task restarted running 4.24 without issue, but this host is rather slow, so it'll be a day or two before I can tell you how it validates. I won't bother updating my package since the file was graphics related as suspected.
Hi Bernd, not a problem
)
Hi Bernd,
not a problem really but I noticed sth odd: I'm still running Einstein under the debugger and with the new science app instead of starting up as soon as BOINC starts crunching an Einstein WU and running until the WU is done (or reboot) the debugger now starts, runs for a while (a few minutes) and gives an "exited normally" message. Then a new debugger starts. Looks like there's more than one process or so... was this to be expected?
RE: Hi Bernd, not a problem
)
I'm not sure I understand you correctly. It sounds like the App exits and is restarted rather often. Do you get a lot messages like "... exited with zero status but no 'finished' file" of the BOINC Client or see "no heartbeat from core client" in stderr.txt in the slot directory?
BM
BM
In fact, the message "no
)
In fact, the message "no heartbeat from core client" shows up all the time. "No heartbeat from core client for 30 seconds, exiting", then a restart of the science app, and the same again after some time. I'm talking about this WU:
http://einsteinathome.org/task/90979066
Please don't mind the user abort, that was just me being tired and hitting the wrong debugger button by accident.
BTW: The version of the BOINC
)
BTW: The version of the BOINC library in this App uses the 'old' method for determining the CPU time. This means that even on older kernels the CPU time should be updated correctly.
BM
BM