Page 1 of 1
CPU bad work units
Posted: Sat May 28, 2016 6:38 pm
by LancerSykera
Hello,
I just built a new machine a few days ago and decided to get back in to folding. My 2x GTX 980 Ti are folding beautifully, but my i7-5960x refuses to. This is what I get in the log, roughly every 30 seconds, when I try to use my CPU:
18:20:13:WU02:FS00:0xa4:Folding@home Core Shutdown: EARLY_UNIT_END
18:20:13:WARNING:WU02:FS00:FahCore returned: BAD_WORK_UNIT (114 = 0x72)
18:20:13:WU02:FS00:Sending unit results: id:02 state:SEND error:FAULTY project:9032 run:154 clone:3 gen:164 core:0xa4 unit:0x000000bcab436c9e56983371fa072f4d
Re: CPU bad work units
Posted: Sat May 28, 2016 8:07 pm
by Joe_H
What settings are you using for your CPU slot? Please post the first 100 or so lines of your log file, include the system info and folding configuration.
Re: CPU bad work units
Posted: Sat May 28, 2016 8:53 pm
by LancerSykera
Here's what happens when I re-add the CPU slot:
http://dumptext.com/rYsGgMAt
Not sure how to include my sys info and config...
Re: CPU bad work units
Posted: Sat May 28, 2016 9:04 pm
by Joe_H
The Welcome to the Forum topic has directions on how to post a log file - viewtopic.php?f=61&t=26036#p261076. To include your system info and config, you either have to use the Refresh button and scroll back to the beginning in the log window of FAHClient, or open the log.txt file in a text editor.
Looking at what you posted on that site, your CPU setting is 14. Apparently the projects you are getting assignments from do not process well on a multiple of 7 during the decomposition stage. I would recommend setting the CPU thread count to 12.
P.S. Please change the logging level back to the default of 3. The higher level is rarely useful and gets in the way of troubleshooting.
Re: CPU bad work units
Posted: Sat May 28, 2016 9:18 pm
by Joe_H
Additional note, I have notified the manager of these projects of the apparent problem with a CPU:14 setting.
Re: CPU bad work units
Posted: Sun May 29, 2016 12:49 pm
by toTOW
Can you try another thread count setting for you CPU slot (12 for instance) ?
Re: CPU bad work units
Posted: Sun May 29, 2016 6:28 pm
by LancerSykera
Yep, 12 worked, thanks! It was default settings that put it on 14.
Re: CPU bad work units
Posted: Mon May 30, 2016 1:04 am
by sryckbos
Yeah that is a flaw in how I had the WS set up. I should just not let it assign to 7 or 14-CPU systems; that's kind of inherent to how the job works that those numbers wouldn't work. Thanks for posting about this. The problem should be fixed on the WS and that shouldn't happen anymore.