CUDA apps continue to run on CPU in suspend mode

My CUDA apps will not stop running. They normally run on the GPU until I or a setting puts Boinc into suspend, then the CUDA app just runs on the CPU and ignores and violates my CPU % usage rules as well. This also happens if windows puts the monitor to sleep.

I noticed this the other night when I heard the CPU fan screaming all the way across the house. My CPU's are set to 20% max but when the monitor went to sleep the CUDA app started running on both CPU's at the same time between 60% and 100% constant. To alleviate this I just set window to not put the monitor to sleep.

Then today I noticed that while an exclusive an was running, the system was bogging down, I looked and again, although Bioinc was supposedly suspended, the CUDA app was running on both CPU's, but this time only at about 30%.

Is anyone else having these issues? Is there a fix for this?

This also happens if windows puts the monitor to sleep.

Because that is not the only time it happens.

The bigger concern is when it happens under suspension and then proceeds to ignore other settings and cook my CPU.

I have worked around the sleep bug, but have found no work around for what I will call the persistence bug. Except to quit running cuda for the time being and see if another project will play nicer with the GPU.

What means "happens under suspension"?
(and where do you look to see what happens)

When you say "cook my CPU" - is this a laptop? What is the CPU temp?

OK, try "another project" (that runs on CUDA/GPU), I will be surprised if "this" depends on project.

The CUDA app (of any project) will either:
- error out/crash the task (when CUDA disappears)
- stop computing until CUDA is available again
- "fall back on host CPU processing" as SETI app do


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

Thank you for your response, but you have overlooked the real problem.

1) That is, that the CUDA applications fail to stop running (entirely) when Boinc is in "suspend" mode (whether I put Boinc into suspend or a rule puts it into suspend, it does not matter). Instead of stopping completely, CUDA will instead quit running on the GPU and begin running on the CPU.

2) When CUDA applications are running on the CPU during times that they are not supposed to be running at all, they ignore the CPU settings of "max 20% CPU", and they use up to 100% on all cores.

So far there has been no damage because I have good cooling and I was near by and I heard the fans running at full speed and I intervened (I do not know what the temp was). Other may not have the same luck.

I then tried several troubleshooting steps and the condition continues to repeat itself.

I do suspect that it is an issue with CUDA which is why I posted it here, but you could be right and it could be an issue with GPU tasks in general which is why I am trying now is to see if another project does the same thing. I aborted all SETI CUDA tasks, and am now waiting for a GPU task to be assigned by Einstein. So far there are no new GPU tasks are in cue, so I am on hold.

when Boinc is in "suspend" mode (whether I put Boinc into suspend or a rule puts it into suspend, it does not matter).

Instead of stopping completely, CUDA will instead quit running on the GPU and begin running on the CPU.

2) When CUDA applications are running on the CPU during times that they are not supposed to be running at all, they ignore the CPU settings of "max 20% CPU", and they use up to 100% on all cores.

So far there has been no damage because I have good cooling and I was near by and I heard the fans running at full speed and I intervened (I do not know what the temp was).

Other may not have the same luck.

His first 3 CUDA units all fell back to CPU. stderr reported "emulation device, unusable". I've seen that one before, and IIRC, it's the sleep bug in 296.10. Interestingly, the last two CUDA's he reported both completed normally, though the 9400GT took awhile, and restarted several times (his suspension settings, no doubt). Then, he aborted the rest, so there's no way to know how they might have run.
____________

One of the tasks that started with "device 1 is emulation device and should not be used" but then continued (Restarted at 21.09 percent) normally (i.e. "using CUDA accelerated device GeForce 9400 GT"):
http://setiathome.berkeley.edu/result.php?resultid=2418530649

Advanced search for emulation device in the last 6 months shows only 3 results (not counting the one from this thread) 2 of which are yours:
http://setiathome.berkeley.edu/forum_thread.php?id=67194&nowrap=true#1204021
http://setiathome.berkeley.edu/forum_thread.php?id=67225&nowrap=true#1207308
http://setiathome.berkeley.edu/forum_thread.php?id=65352&nowrap=true#1217254

I don't know why people go for the "latest" driver if the previous worked OK
I also don't think that NVIDIA will add new features in the new drivers for older hardware (as GeForce 9400 GT) which is no longer in production.

266.58 was the driver recommended for a long time by many users here.
Which is the new "best" version? (meaning - no bugs noticed by anyone here)


____________



- ALF - "Find out what you don't do well ..... then don't do it!" :)

I don't know why people go for the "latest" driver if the previous worked OK
I also don't think that NVIDIA will add new features in the new drivers for older hardware (as GeForce 9400 GT) which is no longer in production.

266.58 was the driver recommended for a long time by many users here.
Which is the new "best" version? (meaning - no bugs noticed by anyone here)

I kept the 285.62 driver in-case I had issues with 296.10 which it seems now like I am having if I am reading you guys correctly.

Is there any comment on the 285.62 driver?