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:
- Release the target system: stop your debug session: in Visual Studio
go to Debug > Stop Debugging
- 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.
- If there is no line that starts with INTEL_GT_DEBUGGER,
this means that you did not enable logging enabled for the GPU
kernel debugger. Follow the instructions below to enable logging.
- If you received a message starting with INTEL_GT_DEBUGGER,
continue to the next step.
- Open the firewall exceptions page Start > Windows Firewall
> Allow an app or feature through Windows Firewall.
- Click the Change Settings button.
- 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
.
- Click Add.
- Select the network for which you want it enabled (Consult with
your IT expert on the type of network that should be enabled).
- Click OK.
- Try again to connect.
To enable logging for the GPU kernel debugger, do the following:
- Visual Studio > Tools > Intel Code Builder for OpenCL
API > OpenCL API Debugger > Options > Kernel Debugger
- Check Log to Output Debug Pane.
- 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.