compute-exclusive/compute-prohibited mode ignored

This is using 3.0 on Suse 11.1. I set the compute mode of all gpus in the system to compute prohibited, and then I try running any example from the sdk and it still works! I don’t understand why the compute mode rules seem to be ignored or what I can do to fix it…any help would be appreciated. I have a different 3.0/Suse 11.1 system where everything works fine (ie cuda doesn’t work) - that system has an amd chip and this broken one has an i7.

Sample output:

aaa@synergy:~/NVIDIA_GPU_Computing_SDK/C/bin/linux/release> nvidia-smi -a -s
COMPUTE mode rules for GPU 0: 2
COMPUTE mode rules for GPU 1: 2
COMPUTE mode rules for GPU 2: 2
aaa@synergy:~/NVIDIA_GPU_Computing_SDK/C/bin/linux/release> ./reduction
./reduction Starting…

Using Device 0: GeForce GTX 470

Reducing array of type int

16777216 elements
256 threads (max)
64 blocks

Reduction, Throughput = 118.5042 GB/s, Time = 0.00057 s, Size = 16777216, NumDevsUsed = 1, Workgroup = 256

GPU result = 2139353471
CPU result = 2139353471

PASSED

Press to Quit…

what driver version are you using?

what driver version are you using?

195.36.15 on both machines.

195.36.15 on both machines.

Pretty sure that was not intended for use with GF100. Can you try 195.36.24?

http://www.nvidia.com/object/linux-display…-195.36.24.html

Pretty sure that was not intended for use with GF100. Can you try 195.36.24?

http://www.nvidia.com/object/linux-display…-195.36.24.html

Thanks, I’ll try and let you know. That would explain it, the computer that works is using a 260.

If it is the case, maybe the download link here http://developer.nvidia.com/object/cuda_3_0_downloads.html should be updated to this newer version of the driver…

Edited: That did fix the problem. Thanks Tim.

Thanks, I’ll try and let you know. That would explain it, the computer that works is using a 260.

If it is the case, maybe the download link here http://developer.nvidia.com/object/cuda_3_0_downloads.html should be updated to this newer version of the driver…

Edited: That did fix the problem. Thanks Tim.