Thanks for sharing the result. I’m not seeing a problematic GPU device based on the log, however I do see the system calls that caused the long delay:
ioctl(3, _IOC(_IOC_READ|_IOC_WRITE, 0x46, 0x2a, 0x20), 0x7ffe4da090b0) = 0 <8.005325>
...
ioctl(4, _IOC(_IOC_NONE, 0, 0x25, 0), 0x7ffe4da0c350) = 0 <24.041903>
and tracking back I can see the FDs they were trying to control were nvidiactl and nvidia-uvm:
openat(AT_FDCWD, "/dev/nvidiactl", O_RDWR) = 3 <0.000019>
...
openat(AT_FDCWD, "/dev/nvidia-uvm", O_RDWR|O_CLOEXEC) = 4 <0.000020>
Unfortunately this is out of the scope of Nsight Systems development, I suggest reporting the issue to CUDA - NVIDIA Developer Forums and see if they have a suggestion. As long as the long delay for cuInit() can be eliminated, Nsys should work well.
On our side we can provide the WAR to increase the timeout limit as mentioned in Nsight system fails to connect to daemon - #11 by liuyis. Are you an NDA customer?