Suspend corrupts Digits

Every time when Digits is used after a wake up from a suspension mode,
it gives an error: error code-6:
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0504 12:30:02.978602 2662 common.cpp:163] Check failed: error == cudaSuccess (30 vs. 0) unknown error
*** Check failure stack trace: ***
cudaRuntimeGetVersion() failed with error #30

If I try ./deviceQuery,it gives:
cudaGetDeviceCount returned 30
-> unknown error

It seams in sleep mode, the system changes into power saving mode and use intel graphic card instead.
Since after reboot, everything works fine.
Is there any way to fix it?

Hi Jhon
I reproduce exactly the same problem after sending to sleep my laptop. I am using the Docker containers version the Digits Container seems to still alive but lose connection with the GPU. I had other errors then I’ve tryed to restart the Driver with

nvidia-docker-plugin | 2017/08/23 10:49:29 Loading NVIDIA unified memory
nvidia-docker-plugin | 2017/08/23 10:49:29 Loading NVIDIA management library
nvidia-docker-plugin | 2017/08/23 10:49:29 Discovering GPU devices
nvidia-docker-plugin | 2017/08/23 10:49:29 Provisioning volumes at /var/lib/nvidia-docker/volumes
nvidia-docker-plugin | 2017/08/23 10:49:29 Serving plugin API at /run/docker/plugins
nvidia-docker-plugin | 2017/08/23 10:49:29 Serving remote API at localhost:3476
nvidia-docker-plugin | 2017/08/23 10:49:29 Error: listen tcp 127.0.0.1:3476: bind: address already in use

ERROR: error code -6

Then i killed the process (docker-plugin) that was using the port 3476 (netstat -lpn |grep :3476) and restart driver but it still giving the same error.

libdc1394 error: Failed to initialize libdc1394
WARNING: Logging before InitGoogleLogging() is written to STDERR
F0823 08:39:44.152972 265 common.cpp:163] Check failed: error == cudaSuccess (30 vs. 0) unknown error
*** Check failure stack trace: ***
cudaRuntimeGetVersion() failed with error #30

I

Hi,

i have encountered the same problem.

sudo rmmod nvidia_uvm ; sudo modprobe nvidia_uvm

works for me…
maybe add it to a rc-wakeup script