Page 1 of 1

Possible bad WU

PostPosted: Mon Sep 29, 2014 2:16 am
by Brainiac5
Is this a bad work unit?

Code: Select all
00:56:07:WU01:FS01:0x15:Run: exception thrown in GuardedRun -- cannot continue further.
00:56:07:WU01:FS01:0x15:Going to send back what have done -- stepsTotalG=40000000
00:56:07:WU01:FS01:0x15:Work fraction=0.6389 steps=40000000.
00:56:11:WU01:FS01:0x15:logfile size=14743 infoLength=14743 edr=0 trr=23
00:56:11:WU01:FS01:0x15:+ Opened results file
00:56:11:WU01:FS01:0x15:- Writing 15279 bytes of core data to disk...
00:56:11:WU01:FS01:0x15:Done: 14767 -> 4789 (compressed to 32.4 percent)
00:56:11:WU01:FS01:0x15:  ... Done.
00:56:11:WU01:FS01:0x15:DeleteFrameFiles: successfully deleted file=01/wudata_01.ckp
00:56:11:WU01:FS01:0x15:Folding@home Core Shutdown: UNSTABLE_MACHINE
00:56:12:WARNING:WU01:FS01:FahCore returned: UNSTABLE_MACHINE (122 = 0x7a)
00:56:12:WU01:FS01:Sending unit results: id:01 state:SEND error:FAULTY project:7623 run:273 clone:0 gen:185 core:0x15 unit:0x0000010c664f2dd14fe4f9fe7ed1d77e

Re: Possible bad WU

PostPosted: Mon Sep 29, 2014 9:22 pm
by bruce
If possible, all WUs must be completed. That means when a WU fails, Stanford sends it to someone else to confrm whether it's an unstable WU or an unstable system. There's only one report of the WU being returned and although it indicates a failure, a single report is inconclusive. We'll have to wait until others have a chance to complete it.