Thank you. So the software preemption can avoid GPU halt, right?
I have only the K600 inserted into the MOBO; the intel embedded gpu seems disabled so K600 is the display card. I checked all the options of Nsight 5.6 and found that, if I didn’t miss anything, the software preemption options are only available under:
- Monitor’s Options -> CUDA(Legacy) -> Desktop GPUs Must Use Software Preemption
- Monitor’s Options -> CUDA(Legacy) -> Headless GPUs Must Use Software Preemption
- Monitor’s Options -> CUDA(Legacy) -> TCC GPUs Must Use Software Preemption
- Option in Nsight menu -> CUDA -> CUDA Debugger (Legacy) -> Preemption Preference
- Option in Nsight menu -> CUDA -> CUDA Debugger (Legacy) -> Preemption Timeslicing
- Option in Nsight menu -> Graphics -> Shader Debugging -> Preferred Remote Shader Debugging
The settings of these options are shown in the screenshot. Because I have only one nVidia graphics card which is the display card, 2) and 3) are irrelevant. All other settings open the software preemption as much as possible. However, the Windows system is still dead when launching CUDA Debugging. I guess maybe software preemption was not implemented very well or even its support was terminated in recent versions of Nsight for Quadro K600. If that is the case, that’s a good news because that means the culpret is indeed GPU halt due to breakpoints. But a worse possibility is that there are bugs. My second Kepler graphics card is on the way. I will set up remote debugging when it arrives, when we’ll know if GPU halt is the cause. Let’s wait and see.