Host and Target Systems are Stuck

Symptom:

The host and target machine seem hung/stuck and never run to completion.

On the host machine, the host application remains in the "Running" state, seems hung/stuck and never runs to completion or hits a breakpoint in the GPU. In addition, the target machine GFX display state seems frozen/hung.

Likely root-cause: missing/broken firewall rule for gdbserver (debug server) traffic on the target machine.

Solution:

  1. Release the target system: stop your debug session: in Visual Studio go to Debug > Stop Debugging
  2. Open the Debug Output pane: in Visual Studio go to Debug > Window > Output. You should see a message similar to the following:
    INTEL_GT_DEBUGGER: (2696194) Failed to connect to gdbserver at target_hostname:2530.
  3. Open the firewall exceptions page Start > Windows Firewall > Allow an app or feature through Windows Firewall.
  4. Click the Change Settings button.
  5. Click Allow another app > Browse > Select %INTELGTDEBUGGERROOT%target\bin\gdbserver.exe
    NOTE: Usually, the full path to it is C:\Program Files\Intel\Debugger for Heterogeneous Compute\target\bin\gdbserver.exe.
  6. Click Add.
  7. Select the network for which you want it enabled (Consult with your IT expert on the type of network that should be enabled).
  8. Click OK.
  9. Try again to connect.

 

To enable logging for the GPU kernel debugger, do the following:

  1. Visual Studio > Tools > Intel Code Builder for OpenCL API > OpenCL API Debugger > Options > Kernel Debugger
  2. Check Log to Output Debug Pane.
  3. Restart Visual Studio and start a new debug session.
    Now you should be able to see diagnostics from the GPU Kernel debugger in the output pane.