Probably a good suggestion. I am out of town now but when I get back I can run the normal memory test and seagagte hardrive test to eliminate them as a possible problem. Unlikely that it is a motherobard or processor error but that is hard to prove. This machine only runs WCG so it is hard to tell if anything else is having a problem. It is not overclocked. My 2 AMD 1090s are not having a problem. I could do processor swaps to eliminate the MB, but that is a pain.

I will post what I find out when I am back on Thursday.

It did have 36 valid results yesterday, but a ton of errors. So it is an intermittent problem.

It is in a room with 6 other computers and they are all running fine and the air conditioner is on in that room (you should see my electrical bill).

Do you know how I can check the cpu temperature on a UBUNTU machine?

I use core temp on my windows machines.

I have checked my temperatures and they are 50 C so I should be ok.

I am now getting a mix of computation errors and valid results.

This computer is an AMD X6 1100, with a 320 GB HD, 4 gb of memory running UBUNTU 11.04.

I have run memtest and the memory tests ok, I have run Seagate Seatools and the disk tests ok, and I have run Mersenne Prime with no errors. I have reinstalled Ubuntu 11.04.

I have 19 other computers in the house with no problems, including two AMD X6 1090Ts. This machine only runs WCG nothing else, and nothing else was installed on it.

I get mix of computation errors and resuts that end Valid.

Anybody have any idea what else can I try? I would find it hard to believe that WCG is not compatable with an AMD X6 1100.

From CEP

Result Log

Result Name: E203001_ 912_ C.27.C23H15N3Si.00542769.3.set1d06_ 0--



<core_client_version>6.10.59</core_client_version>
<![CDATA[
<message>
process exited with code 195 (0xc3, -61)
</message>
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[15:32:04] Number of jobs = 16
[15:32:04] Starting job 0,CPU time has been restored to 0.000000.
[15:32:04] Starting new Job
[15:32:04] Qink name = fldman
[15:32:04] Qink name = gesman
[15:32:04] Qink name = scfman
Application exited with RC = 0xb
[15:32:23] Finished Job #0
15:32:23 (2404): called boinc_finish

</stderr_txt>
]]>

From HFCC


Result Log

Result Name: HFCC_ target-7_ 00180618_ target-7_ 0001_ 0--



<core_client_version>6.10.59</core_client_version>
<![CDATA[
<message>
process exited with code 193 (0xc1, -63)
</message>
<stderr_txt>
WARNING: I just prevented an attempt to take the arccosine of 1, a value greater than 1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.




autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of 1, a value greater than 1.



autogrid4: WARNING: I just prevented an attempt to take the arccosine of -1, a value less than -1.



autogrid: autogrid4: Successful Completion.
INFO:[15:33:28] End AutoGrid...
Beginning AutoDock...
INFO: Setting num_generations: 27000
WARNING! While doing proportional selection, worst ( nan) = avg ( nan).
This would cause a division-by-zero error.
All members of the population will be arbitrarily allocated 1 child each.
WARNING! The population appears to have converged, so this run will shortly terminate.

_maxGenSeenSoFar changed: 6750
SIGSEGV: segmentation violation
Stack trace (13 frames):
[0x80b3d1b]
[0x811ab78]
[0xf77ea400]
[0x80522f2]
[0x807158c]
[0x8059d01]
[0x8055fd9]
[0x804abf6]
[0x80886d2]
[0x80a5d69]
[0x80a6be3]
[0x811cc7a]
[0x8048131]

Exiting...

</stderr_txt>
]]>


Return to Top

I do not think it is a hard drive issue because I ran SeaTools Long version and the drive checked out ok.

I do think I may have found it though! I could think of nothing else to do, since I checked out the hardware and reinstalled the software, so I cleared CMSOS and took the battery out for 10 minutes.

I have had no errors for 24 hours! :)

I had previously checked the BIOS to make sure I was not overclocking and the BIOS looked fine, but clearing it out may have fixed the problem. I will need another 24 hours to make certain.

- Mitch

Glad it is working. If it doesn't, revisit my suggestion. The systems I tested had Hard Drives that past too, then they still failed because of IO burdens. Replacement of hard drives fixed it immediately on each of them.