CL file build failure

Message boards : Number crunching : CL file build failure
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 1282
Credit: 187,688,550
RAC: 182
United States
Message 1718155 - Posted: 25 Aug 2015, 13:49:16 UTC

On this one computer of mine, (the same one that has a great number of ghosts on it) is now going through AP tasks which all are failing with Waiting to Run. The error from the log is 8/25/2015 9:33:38 AM Task postponed: CL file build failure
This is on computer http://setiathome.berkeley.edu/show_host_detail.php?hostid=5743750
Any help would be appreciated.

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1718155 · Report as offensive
Profile Zalster Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 27 May 99
Posts: 5517
Credit: 528,817,460
RAC: 242
United States
Message 1718157 - Posted: 25 Aug 2015, 13:56:21 UTC - in response to Message 1718155.  

Bill,

Have you installed Lunatics v43.b

It resolves the issue with kernal builds with the bool2 issues

Also, I noticed you are running 353.62 yet it says Opencl 1.1, starting with 350.12 it should be OpenCl 1.2

Might want to consider reinstalling your nvidia driver with a clean install. Don't install the latest driver as there seems to be some issues with it, at least what I see in the forums on nvidia.
ID: 1718157 · Report as offensive
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 1282
Credit: 187,688,550
RAC: 182
United States
Message 1718178 - Posted: 25 Aug 2015, 14:30:53 UTC - in response to Message 1718157.  
Last modified: 25 Aug 2015, 14:32:26 UTC

Bill,

Have you installed Lunatics v43.b

It resolves the issue with kernal builds with the bool2 issues

Also, I noticed you are running 353.62 yet it says Opencl 1.1, starting with 350.12 it should be OpenCl 1.2

Might want to consider reinstalling your nvidia driver with a clean install. Don't install the latest driver as there seems to be some issues with it, at least what I see in the forums on nvidia.

Rolled back to a known working driver (clean install) and it seems to be working now.
I do not know about the OpenCl version however and I will check later to see what Lunatics version I am running.
For now it looks ok to me. Thanks for the advice.

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1718178 · Report as offensive
rob smith Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer moderator
Volunteer tester

Send message
Joined: 7 Mar 03
Posts: 22160
Credit: 416,307,556
RAC: 380
United Kingdom
Message 1718182 - Posted: 25 Aug 2015, 14:35:23 UTC

Actaully Bill is running driver version 347.88, which is a good stable version:
[2] NVIDIA GeForce GT 630 (2048MB) driver: 347.88 OpenCL: 1.1


Running Lunatics installer v43.b will certainly overcome some/most/all of the issues some have suffered with the CL file not compiling correctly...
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?
ID: 1718182 · Report as offensive
Profile Bill G Special Project $75 donor
Avatar

Send message
Joined: 1 Jun 01
Posts: 1282
Credit: 187,688,550
RAC: 182
United States
Message 1718197 - Posted: 25 Aug 2015, 15:01:38 UTC - in response to Message 1718182.  

Yes Rob, that is what I rolled back to.

I just installed v43.b as I was running v43.a and I am still working just fine.
Again, Thanks

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours
ID: 1718197 · Report as offensive
Profile SciManStev Crowdfunding Project Donor*Special Project $75 donorSpecial Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 20 Jun 99
Posts: 6651
Credit: 121,090,076
RAC: 0
United States
Message 1718231 - Posted: 25 Aug 2015, 15:59:22 UTC

The same thing happened to me, after the latest lunatics build. At first I reverted to the described driver, then as it wasn't designed for Win 10, I went through the .CL file, and changed the rest of the bool2 to bool_2, and it fixed the problem. I can now use newer drivers designed for Win 10.

Steve
Warning, addicted to SETI crunching!
Crunching as a member of GPU Users Group.
GPUUG Website
ID: 1718231 · Report as offensive

Message boards : Number crunching : CL file build failure


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.