I got this message for a 6.08 wu (using 6.6.37 BOINC) -

7/30/2009 3:26:42 AM SETI@home Aborting task 04dc08ah.16808.1299.15.10.131_0: exceeded elapsed time limit 16701.964037

Didn't expect to see this.
XP 32-bit, Q6600, GTX 260 - 216 (driver 182.15)

I've been unable to successfully process any GPUGRID wu, but that's another story. I see the occasional aborted SETI CUDA wu abort, but I caught this one in the messages.

Any info.? Is this related to the VLAR issue?

---

I got this message for a 6.08 wu (using 6.6.37 BOINC) -

7/30/2009 3:26:42 AM SETI@home Aborting task 04dc08ah.16808.1299.15.10.131_0: exceeded elapsed time limit 16701.964037

Didn't expect to see this.
XP 32-bit, Q6600, GTX 260 - 216 (driver 182.15)

I've been unable to successfully process any GPUGRID wu, but that's another story. I see the occasional aborted SETI CUDA wu abort, but I caught this one in the messages.

Any info.? Is this related to the VLAR issue?

Given your clues, I found the Task details 1320119915. It's not related to the VLAR issue, being a midrange "true angle range is : 0.432947". What happened was a failure to detect the GPU properly:

setiathome_CUDA: Found 1 CUDA device(s):
   Device 1 : Device Emulation (CPU) 
           totalGlobalMem = -1 

The emulation mode doesn't work, so eventually it gets to "Falling back to HOST CPU processing...", and that's a generic slow CPU version. The maximum elapsed time was set assuming the GPU would do the work, so wasn't enough for CPU fallback mode.

There are three other similar cases in that host's errored task list. I think others with similar problems have found updating to newer nVidia drivers helped.

                                                         Joe

Hi Josef,
I've been dealing with driver issues and GPUGRID. Have fallen back to this revision as it is the most stable at this time. I thought that 6.6.37 took care of this type of issue. I'll try a newer version of the driver and monitor. Thanks for the reply!

---

After posting this to another forum, which may have been wrong, I found this thread. Please help if you can....I am running the 190.&& nVidia drivers and just updated the CUDA .dll's to the neww ones posted via the lunatics web site. Got some fresh CUDA work and on my GeForce 9400 GT (driver version 19038, compute capability 1.1, 1024MB, est. 10GFLOPS) vid card, it is scheduled to take 13 HOURS to finish a batch! Any suggestions, or help IS GREATLY appreciated.

After posting this to another forum, which may have been wrong, I found this thread. Please help if you can....I am running the 190.&& nVidia drivers and just updated the CUDA .dll's to the neww ones posted via the lunatics web site. Got some fresh CUDA work and on my GeForce 9400 GT (driver version 19038, compute capability 1.1, 1024MB, est. 10GFLOPS) vid card, it is scheduled to take 13 HOURS to finish a batch! Any suggestions, or help IS GREATLY appreciated.

Well 10Gflops is not fast for a graphics card.

Its only an estimated time. It will need to work on a couple of them to get a better idea of how long they take. If it isn't a VLAR it will probably be a lot better than the 13 hour estimate.

---

BOINC blog

After posting this to another forum, which may have been wrong, I found this thread. Please help if you can....I am running the 190.&& nVidia drivers and just updated the CUDA .dll's to the neww ones posted via the lunatics web site. Got some fresh CUDA work and on my GeForce 9400 GT (driver version 19038, compute capability 1.1, 1024MB, est. 10GFLOPS) vid card, it is scheduled to take 13 HOURS to finish a batch! Any suggestions, or help IS GREATLY appreciated.

You could add <flops> to app_info.xml as described here http://setiathome.berkeley.edu/forum_thread.php?id=53593

@ John
Is it possible to shutdown Boinc and add FLOPS lines in app_info.xml then restart Boinc,and not loose tasks.
I have about 1000 tasks to be processed and it will take a few days.Or
would it be better to run the tasks out and then alter the .xml?
I know the second option is the best way but I would like the timings a bit better.

---

@ John
Is it possible to shutdown Boinc and add FLOPS lines in app_info.xml then restart Boinc,and not loose tasks.
I have about 1000 tasks to be processed and it will take a few days.Or
would it be better to run the tasks out and then alter the .xml?
I know the second option is the best way but I would like the timings a bit better.

Adding the flops line will not break anything as long as you are careful to re-save the .xml file as .xml and not as .txt.

F.

---

Thank's Fred

---