Forum > Linux
New compiles of Rev-2.2B code released
Simon:
Hi folks,
I've uploaded some new compiles of the Rev-2.2B apps.
Contrary to the initial apps, these will not be static/statified, but instead come in two flavours - Kernel-2.4 and Kernel-2.6.
Should you still have trouble with libraries and/or segfaults, please post in this thread; still, 2 versions per app should be enough, I hope.
The compilation platform we used, Suse 9.2, is really not all that current - if your libraries are still not recent enough, it's probably high time you upgraded.
The download links remain the same, if you had trouble with the initially released applications, please try these.
Also, the SSE3-P4 app that was initially released has some accuracy problems; if you're running it on any of your hosts, this version is a required upgrade - you'll lose credit and turn in invalid results if you don't upgrade.
Regards,
Simon.
clk:
Howdy,
It works, as long as you don't run more than one instance. On RHEL3 Kernel-2.4 on a P4 2.8GHz I tried both the SSE2-P4 and SSE3-P4. With one instance of Seti running everything was ok. But, since I'm running Hyper-Thread Boinc starts a second Seti task and instantly errors out with:
--- Quote ---2007-04-02 22:08:12 [SETI@home] Can't get shared memory segment name: can't get shared mem segment name
2007-04-02 22:08:12 [SETI@home] Unrecoverable error for result 16oc03ab.11131.5954.29822.3.78_1 (Couldn't start or resume: -202)
2007-04-02 22:08:12 [SETI@home] Deferring scheduler requests for 1 minutes and 0 seconds
2007-04-02 22:08:12 [---] Rescheduling CPU: start failed
2007-04-02 22:08:12 [SETI@home] Computation for task 16oc03ab.11131.5954.29822.3.78_1 finished
--- End quote ---
That is this result http://setiathome.berkeley.edu/result.php?resultid=510804716
Meanwhile the first, original, Seti workunit continues processing and eventually finishes.
The funny thing is, by playing with "suspend task" I can get BOINC to start a task for another project (Einstein in this case) and it will run ok in tandem with the first Seti task. You just cannot run two Seti tasks simultaneously.
At this point I've completed one workunit http://setiathome.berkeley.edu/workunit.php?wuid=122308461. Mine is the one for 11614 seconds. The workunit hasn't validated at this point in time, still waiting for another result. Hopefully it is ok.
But that still leaves the bigger question of why the shared memory fault.
Thanks again for all the effort you guys are putting into this work.
Best of Luck, and get some sleep.
Cheers, Chris
Metod, S56RKO:
--- Quote from: Simon on 02 Apr 2007, 04:08:06 pm ---Also, the SSE3-P4 app that was initially released has some accuracy problems; if you're running it on any of your hosts, this version is a required upgrade - you'll lose credit and turn in invalid results if you don't upgrade.
--- End quote ---
I guess this app for kernel 2.6 won't run on my 64-bit Debian Etch:
$ ldd KWSN-R2.2B-SSE3-P4
linux-gate.so.1 => (0xffffe000)
libdl.so.2 => /lib32/libdl.so.2 (0xf7ee8000)
libm.so.6 => /lib32/libm.so.6 (0xf7ec4000)
libgcc_s.so.1 => not found
libpthread.so.0 => /lib32/libpthread.so.0 (0xf7eb2000)
libc.so.6 => /lib32/libc.so.6 (0xf7d87000)
/lib/ld-linux.so.2 (0xf7f04000)
As you can see I don't have libgcc_s.so.1 for 32-bit. Can you link at least gcc libraries statically?
clk:
Howdy again,
Well, another variation. The new compile of SSE2-P4 runs a little better on a RHEL3 2.4 Kernel when used with Boinc 5.8.15 vs. 5.4.9 or 5.4.11 . This was tested on two separate boxes, but the results were about the same. On a Boinc 5.8.15 client when a series of Seti workunits are downloaded and work starts the first workunit runs ok, the second workunit crashes, but then the third workunit will run ok. So, on a hyperthread cpu you can get two seti workunits running simultaneously. This is better than on a Boinc 5.4.9 client where only the first Seti workunit will run, and any attempt to start another workunit will crash (note my previous post in this thread).
Continuing work on the Boinc 5.8.15 client, when one of the Seti workunits finishes, the next workunit will crash, but then a second attempt to start another workunit will run ok. Obviously, I'm not continuing at this time with this new code on the 2.4 Kernel, don't want to "error out" a bunch of workunits. Hopefully, this adds to the understanding and leads to a solution for the problem.
Two of the error workunits are:
http://setiathome.berkeley.edu/result.php?resultid=511457534
and, http://setiathome.berkeley.edu/result.php?resultid=511457667
The relevent log outputs:
--- Quote ---2007-04-03 16:22:50 [SETI@home] Starting 16oc03ab.11131.14736.840898.3.129_0
2007-04-03 16:22:50 [SETI@home] Deferring communication for 1 min 0 sec
2007-04-03 16:22:50 [SETI@home] Reason: Unrecoverable error for result 16oc03ab.11131.14736.840898.3.129_0 (Can't get shared memory segment
name: can't get shared mem segment name)
2007-04-03 16:22:51 [SETI@home] Computation for task 16oc03ab.11131.14736.840898.3.129_0 finished
2007-04-03 16:22:51 [SETI@home] Output file 16oc03ab.11131.14736.840898.3.129_0_0 for task 16oc03ab.11131.14736.840898.3.129_0 absent
--- End quote ---
and,
--- Quote ---2007-04-03 13:25:57 [SETI@home] Starting 16oc03ab.11131.14736.840898.3.157_3
2007-04-03 13:25:57 [SETI@home] Deferring communication for 1 min 0 sec
2007-04-03 13:25:57 [SETI@home] Reason: Unrecoverable error for result 16oc03ab.11131.14736.840898.3.157_3 (Can't get shared memory segment
name: can't get shared mem segment name)
2007-04-03 13:25:59 [SETI@home] Computation for task 16oc03ab.11131.14736.840898.3.157_3 finished
2007-04-03 13:25:59 [SETI@home] Output file 16oc03ab.11131.14736.840898.3.157_3_0 for task 16oc03ab.11131.14736.840898.3.157_3 absent
--- End quote ---
So, on a 2.4 Kernel with Boinc 5.8.15 basically the same shared memory fault, but not as often as with Boinc 5.4.9 (or 5.4.11).
I'm an experimental scientist so I'm always looking for more data. So, here are a couple of the "successful" workunits for completeness, maybe they will be of some use.
http://setiathome.berkeley.edu/result.php?resultid=511457685
http://setiathome.berkeley.edu/result.php?resultid=511457749
If I can help speed up the work I'll be happy to test anything you want to throw my way. We can see if it sticks to the wall.
Ciao, Chris
Ned Slider:
SSE client looking good so far on a couple CentOS 4 boxes, Athlon XP's (2.6 kernel). Seeing great speed improvements and no errors.
Great work everyone!
Regards,
Ned
Navigation
[0] Message Index
[#] Next page
Go to full version