Nsight Systems does not show CUDA and other accelerator trace simultaneously

Developer Tools Nsight Systems Profiling Embedded Targets
1

Using the latest Jetpack on AGX Xavier and accompanying Host tools from the SDK Manager, the following happens:

I use the PVA via VPI and want to trace its behavior. I also need to profile the GPU via plain CUDA. Now, profiling each individually works fine. However both at the same time does not work. I attached some screenshots to showcase the behavior.

First: The project settings.

nsight_settings
nsight_settings373×1139 63.7 KB

If I profile the project like this, the timeline does not show the GPU row, only the other accelerators.

nsight_accel_timeline
nsight_accel_timeline601×674 40 KB

There are some warnings:

nsight_accel_messages
nsight_accel_messages870×462 68.7 KB

Now, if the Collect other accelerators trace setting is disabled, the GPU timeline shows up:

nsight_cuda_timeline
nsight_cuda_timeline508×645 36.1 KB

And there are no warnings:

nsight_cuda_messages
nsight_cuda_messages802×290 42.9 KB

I would like to have both the CUDA kernels and the PVA Tasks in one profiling session. In the future I also expect the DLA and possibly VIC to be used as well as the NVENC hardware.

Is the scenario of showing all of those at the same time supported? For now I would be already happy if the PVA and CUDA traces would show up simultaneously though.

Here some additional info to aid diagnosis:
# R32 (release), REVISION: 4.4, GCID: 23942405, BOARD: t186ref, EABI: aarch64, DATE: Fri Oct 16 19:37:08 UTC 2020

CUDA Version 10.2.89

Nsight systems about:
nsight_version

If further information is required I am happy to provide it.

2

Just checking back if there are any new insights on this. Is this issue reproducible for Nvidia? Or could it be a misconfigured system? If so, what could be possible causes? Thanks in advance :)

3

Hello tobias.fischer1. Sorry for the delay, Nsys dev team has started investigating your issue. Thank you for so detailed information. It really helps to get to the root cause faster.

4

FYI, I did not change anything specifically, but both the accelerator trace and the gpu trace show up now. So maybe it was some configuration issue on my side. I don’t want you to chase ghosts :)

5

Great, then we stop this chase for now. But if it arises again, please, do not hesitate to contact us. We appreciate you’re using Nsight Systems.

6

I’m running into the same / a similar issue on a TX2 (still running an old R28.2.1, can’t change this ATM) and Nsight Systems 2020.3.2 No combination of options has produced a CUDA trace so far

7

Same issue when generating the profile with nsys profile ... locally and importing the .qdrep

9

Unfortunately Anatoly is no longer on the team. @akostikov can you help assign this to the correct engineer?

10

After some offline conversations, I am referring this to @pkovalenko

11

Are you referring to missing nvmedia trace? If so, that’s a known issue and the library team is working on it.