Anyone been getting computation errors on linux lately? I am seeking the cause of these errors.

I recently updated my glibc libraries to version 2.10.1-5, and I think that's when the computation errors started.

Here are a few WU as examples of what's gone wrong. My computer is 4965770--the only one with the errors.
http://setiathome.berkeley.edu/workunit.php?wuid=503212778
http://setiathome.berkeley.edu/workunit.php?wuid=503213032

Forgot to add previously:
Running Fedora 11 x86_64, kernel 2.6.30, on an Intel Core i7 CPU;
BOINC version 6.4.7; installed from RPM;
boinc daemon runs as boinc user;

<core_client_version>6.6.37</core_client_version>
<![CDATA[
<stderr_txt>
setiathome_enhanced 6.03 Revision: 306 g++ (Debian 4.3.1-6) 4.3.1
libboinc: BOINC 6.3.8

Work Unit Info:
...............
WU true angle range is : 0.387434
Optimal function choices:
-----------------------------------------------------
name
-----------------------------------------------------
v_BaseLineSmooth (no other)
v_vGetPowerSpectrumUnrolled 0.00066 0.00000
sse2_ChirpData_ak 0.01416 0.00000
v_vTranspose4 0.02247 0.00000
AK SSE folding 0.00155 0.00000

Flopcounter: 44906511469386.210938

Spike count: 0
Pulse count: 1
Triplet count: 0
Gaussian count: 2
called boinc_finish

</stderr_txt>
]]>

I seem to have no problems with regular seti wu - above is an example output.

wlh2008

The first one you gave was completed by another computer, so you have to look local. It can't be a bad batch of work then. So check those library files first, else check memory, swap file etc.

If everything runs normal again on older libraries, it is a problem with the new ones.

---

Yes, my Fedoras and OpenSuse's, 64 and 32, are getting computation errors on AP's also. I'm sure there were plenty of updates prior to me noticing this.

---