My S@H Cuda 6.06 stops running at 00:00:21 seconds....
My S@H Cuda 6.06 stops running at 00:00:21 seconds.... |
|
| log in |
Message boards : Number crunching : My S@H Cuda 6.06 stops running at 00:00:21 seconds....
| Author | Message |
|---|---|
|
I just discovered a quite serious problem - My Cuda Seti have stopped crunching - but it still seems active. I get the status running, then Cpu-time counts up to 00:19, freezes a second, the displays 00:21 and no work is done, a simple task keeps up running until i pause or abort it. I tried to leave it alone to see if it was crunching, but after 91:21:12 i aborted it. THe machine has been running fine before. Does anybody have a clue ??? | |
ID: 850219 ·  | |
|
Without seeing the tasks it's hard to say exactly what it is, but if it's a CUDA task, the most common reason for this type of behaviour is Very Low Angle Range, or VLAR ( angle ranges 0.1 and below), which CUDA is not able to run. If you could post a link to the task you're talking about or un-hide your pc, it would be more possible to verify. | |
| ID: 850233 · | |
|
I have the same problem - CUDA job stuck at 00:21. | |
| ID: 850242 · | |
I have the same problem - CUDA job stuck at 00:21. Of the MB tasks of yours that were aborted they all appear to be Very Low Angle Range. At this time aborting those tasks is about all you can do when running CUDA. You also have a number of AstroPulse tasks aborted too, but I'm not sure why those were a probmlrm for you. If they were stuck too, snoozing them and making sure you completely close down Boinc Manager and then restarting Boinc can sometimes get those going again. Sometimes even a reboot of the system after the previous suggestion fails, can do the trick too. ____________ | |
| ID: 850252 · | |
|
I aborted one of these 'frozen' CUDA work units, the system had completed no work for several hours :( | |
| ID: 850477 · | |
|
same happened to me had a task running next day same task was still running,so all i did was stop accepting cuda tasks and aborted all cuda tasks i had in stock,so back to crunching regular units now | |
| ID: 850492 · | |
|
someone had written and posted a script to end task when Cuda locked up. It was on this forum but I can't find it now. | |
| ID: 850494 · | |
|
VBScript thread link VBscript - It fights with CUDA app freezing | |
| ID: 850505 · | |
|
thats the one | |
| ID: 850513 · | |
|
Hi! | |
| ID: 852640 · | |
Hi! There are many threads that discuss the bugs that are causing problems in CUDA. This post probably describes what bug or bugs were in the tasks you had as well. As well as the VBscript you are running you should also use the batch file mentioned in several threads like this thread which will allow you to spot VLAR tasks and abort them before they run . ____________ | |
| ID: 852644 · | |
|
Byron S Goodgame wrote: As well as the VBscript you are running you should also use the batch file mentioned in several threads like this thread which will allow you to spot VLAR tasks before they run and abort them. Thats right. The script cant abort VeryLowAngleRange - WU's by clicking the button in Boinc-Manager. You must make that as it is explained in this thread. The script is helping you to avoid non-VLAR WU's that they get stuck and blocking your host ... And its written down often: You have to babysit seti-cuda. That means: Download some WU's (in cache), suspend computation, suspend networkactivity (better: set to no new tasks), check them for VLAR, abort VLAR, let them crunch the complete cache, resume networkactivitity, upload results, report results, start at the beginning at every time your cache is crunched (if you set NNT -> allow new tasks). kevin6912 wrote: VBScript thread link VBscript - It fights with CUDA app freezing Please do NOT use the script posted there, use this link ;) VBscript Fights Cuda - Thread @ lunatics ____________ | |
| ID: 852647 · | |
Message boards : Number crunching : My S@H Cuda 6.06 stops running at 00:00:21 seconds....
| Copyright © 2013 University of California |
