Task postponed: CL file build failure

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

To post messages, you must log in.

AuthorMessage
Profile Cornhusker

Send message
Joined: 20 Apr 09
Posts: 41
Credit: 45,415,265
RAC: 37
United States
Message 1665644 - Posted: 15 Apr 2015, 15:03:52 UTC

What the dickens does "Task postponed: CL file build failure" mean?

For the last 2 days I haven't been able to run any AP tasks because they all give this message. My event log looks like this:

4/15/2015 9:50:17 AM | SETI@home | Task postponed: CL file build failure
4/15/2015 9:50:19 AM | SETI@home | Task postponed: CL file build failure
4/15/2015 9:50:21 AM | SETI@home | Task postponed: CL file build failure
4/15/2015 9:50:24 AM | SETI@home | Task postponed: CL file build failure

Any ideas? Thanks!
ID: 1665644 · Report as offensive
Profile Cornhusker

Send message
Joined: 20 Apr 09
Posts: 41
Credit: 45,415,265
RAC: 37
United States
Message 1665645 - Posted: 15 Apr 2015, 15:06:48 UTC - in response to Message 1665644.  

More info: It's happening only on NVIDIA AP tasks. I have 2 other machines that are CPU only that are running fine.
ID: 1665645 · Report as offensive
Werecow
Avatar

Send message
Joined: 13 Mar 05
Posts: 56
Credit: 4,917,657
RAC: 3
United States
Message 1665650 - Posted: 15 Apr 2015, 15:20:16 UTC - in response to Message 1665644.  

That issue is being covered here: http://setiathome.berkeley.edu/forum_thread.php?id=77133

Reverting to driver 347.88 seems to fix the issue for the time being.
ID: 1665650 · 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 1665652 - Posted: 15 Apr 2015, 15:34:05 UTC - in response to Message 1665650.  

Or you could go over to Beta and test out the new APs version on that driver and see if it works.
ID: 1665652 · Report as offensive
Profile Cornhusker

Send message
Joined: 20 Apr 09
Posts: 41
Credit: 45,415,265
RAC: 37
United States
Message 1665658 - Posted: 15 Apr 2015, 15:40:54 UTC - in response to Message 1665650.  

Thank you. I reverted to 347.88 and things seem to be working now.
ID: 1665658 · Report as offensive
spitfire_mk_2
Avatar

Send message
Joined: 14 Apr 00
Posts: 563
Credit: 27,306,885
RAC: 0
United States
Message 1686322 - Posted: 31 May 2015, 16:43:25 UTC

352.86 did not work either.

Will be using 347.88.
ID: 1686322 · Report as offensive
Chris Oliver Project Donor
Avatar

Send message
Joined: 4 Jul 99
Posts: 72
Credit: 134,288,250
RAC: 15
United Kingdom
Message 1700644 - Posted: 12 Jul 2015, 3:27:38 UTC - in response to Message 1686322.  

353.30 is a wash out also on my Titan. I was about to upgrade my GPU to a newer model but I guess thats on hold if I can't get drivers thats gonna work.
ID: 1700644 · 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 1700669 - Posted: 12 Jul 2015, 5:30:53 UTC - in response to Message 1700644.  

It has to do with the .cl for the knernal. Petri is aware of this and I think he will make a change in the next version of Lunatics if I remember correctly.

You can try to change it yourself, by replacing bool2 to bool_2 in the kernal.cl

I went the other route and use Raistmer's fix but I only was successful 1 time. Al the other times I got error, I ended up coping my app_info file. so it's not 100% fool proof.. And I am the FOOL!!!
ID: 1700669 · Report as offensive
Profile Raistmer
Volunteer developer
Volunteer tester
Avatar

Send message
Joined: 16 Jun 01
Posts: 6325
Credit: 106,370,077
RAC: 121
Russia
Message 1700707 - Posted: 12 Jul 2015, 11:02:22 UTC - in response to Message 1700669.  
Last modified: 12 Jul 2015, 11:05:57 UTC

It has to do with the .cl for the knernal. Petri is aware of this and I think he will make a change in the next version of Lunatics if I remember correctly.

You can try to change it yourself, by replacing bool2 to bool_2 in the kernal.cl

I went the other route and use Raistmer's fix but I only was successful 1 time. Al the other times I got error, I ended up coping my app_info file. so it's not 100% fool proof.. And I am the FOOL!!!

Changes ALREADY MADE in sources. So any new build doesn't suffer from this issue.
And Petri doesn't maintain Lunatics installer so don't have any influence on this situation currently. Ball on Richard's side (regarding installer). And as I mentioned numerous of times there is separate package for update only AP part of Anonymous platform installation. I provided it months ago. And still no aceptance of proper ways to deal with this issue :/

Revert to stock - stock build released 23 Apr 2015, 18:50:41 UTC (July currently!) has this issue fixed.
ID: 1700707 · Report as offensive
BetelgeuseFive Project Donor
Volunteer tester

Send message
Joined: 6 Jul 99
Posts: 158
Credit: 17,117,787
RAC: 19
Netherlands
Message 1700993 - Posted: 13 Jul 2015, 6:37:18 UTC - in response to Message 1700644.  

353.30 is a wash out also on my Titan. I was about to upgrade my GPU to a newer model but I guess thats on hold if I can't get drivers thats gonna work.


I don't know what they messed up with the 35x drivers, but I would not recommend them. They are causing lots of system freezes on my GTX-750. I even tried a hotfix version (353.38), but it only reduces the number of system freezes, they still have not solved all of the problems. Went back to 347.88 and everything is find again.

My 2 cents: avoid the 35x drivers until these problems are solved.

Tom
ID: 1700993 · 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 1701125 - Posted: 13 Jul 2015, 18:13:57 UTC - in response to Message 1700993.  

I've noticed that my computer with 2 GTX 750Ti and new NV driver is constantly freezing with the APs.

My other machine with older driver and GTX 750 doesn't seem to be suffering that fate.

The last 2 machines both have high end GPUs and no freezing. So I have to wonder if there is something in the NV driver or the AP app that is causing the freeze up with the lower end GPUs.

I"m leaning toward the NV driver at this point.
ID: 1701125 · Report as offensive
Profile Cliff Harding
Volunteer tester
Avatar

Send message
Joined: 18 Aug 99
Posts: 1432
Credit: 110,967,840
RAC: 67
United States
Message 1701174 - Posted: 13 Jul 2015, 20:57:35 UTC - in response to Message 1701125.  

I've noticed that my computer with 2 GTX 750Ti and new NV driver is constantly freezing with the APs.

My other machine with older driver and GTX 750 doesn't seem to be suffering that fate.

The last 2 machines both have high end GPUs and no freezing. So I have to wonder if there is something in the NV driver or the AP app that is causing the freeze up with the lower end GPUs.

I"m leaning toward the NV driver at this point.


I had the a similar problem until I reverted to 347.88.


I don't buy computers, I build them!!
ID: 1701174 · Report as offensive
Wedge009
Volunteer tester
Avatar

Send message
Joined: 3 Apr 99
Posts: 451
Credit: 431,396,357
RAC: 553
Australia
Message 1703150 - Posted: 19 Jul 2015, 20:32:45 UTC

I'll add my experience to the previous posters: I know there are some GUI issues introduced with BOINC 7.6.x, but I still observed GUI issues with OpenCL (namely AstroPulse) after reverting to BOINC 7.4.42 (Fermi and Kepler cards). Reverting NV drivers to 347.88 appears to resolve this.

Makes me wonder what changed in the OpenCL 1.2 support introduced for 352/353.xx drivers.
Soli Deo Gloria
ID: 1703150 · Report as offensive
Profile Keith Myers Special Project $250 donor
Volunteer tester
Avatar

Send message
Joined: 29 Apr 01
Posts: 13161
Credit: 1,160,866,277
RAC: 1,873
United States
Message 1703172 - Posted: 19 Jul 2015, 21:54:50 UTC - in response to Message 1701174.  

I've been running the 353.30 NV drivers on my 970s with no problems for quite a while now. Was OK on BOINC 7.6.2 and now still OK on BOINC 7.6.6. The 7.6.6 version finally fixed the invalids over at MilkyWay and seems to have done the same here at SETI. Not having any kind of driver issues at all. In fact I haven't had a video driver fault since I installed them over a month ago. Wasn't the case with the older 350.12 drivers. I like them.
Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)
ID: 1703172 · Report as offensive

Message boards : Number crunching : Task postponed: 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.