Nsys profiler reports "No GPU associated to the given UUID" run in root

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Please provide the following info (check/uncheck the boxes after creating this topic):
Software Version
DRIVE OS Linux 5.2.6
DRIVE OS Linux 5.2.6 and DriveWorks 4.0
DRIVE OS Linux 5.2.0
DRIVE OS Linux 5.2.0 and DriveWorks 3.5
NVIDIA DRIVE™ Software 10.0 (Linux)
NVIDIA DRIVE™ Software 9.0 (Linux)
other DRIVE OS version
other

Target Operating System
Linux
QNX
other

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)
other

SDK Manager Version
1.9.1.10844
other

Host Machine Version
native Ubuntu 18.04
other

Hi,

Recently when we tried to profile a cuda program on Jetson Xavier, which runs JetPack 5.1.2 [L4T 35.4.1], we find there is no Nsight in our installed version of JetPack, so we downloaded the specific Linux Arm version of Nsight (NVIDIA Nsight Systems version 2024.4.1.61-244134315967v0) from official site and installed.

Then we entered the root mode and run nsys profile --output=report --trace=cuda,nvtx,osrt python3 test.py , where test.py consist numba invoke of cuda, and we try to generate a report file. The program run to the end without issues, but we got

FATAL ERROR: /dvs/p4/build/sw/devtools/Agora/Rel/QuadD_Main/QuadD/Common/GpuTraits/Src/GpuTicksConverter.cpp(371): Throw in function QuadDCommon::TimestampType GpuTraits::GpuTicksConverter::ConvertToCpuTime(const QuadDCommon::Uuid&, uint64_t&) const
Dynamic exception type: boost::wrapexcept<QuadDCommon::NotFoundException>
std::exception::what: NotFoundException
[QuadDCommon::tag_message*] = No GPU associated to the given UUID

error for the nsys. How to fix it? Could it be a problem that we installed a separate version of Nsight instead of installing a JetPack with Nsight with it?

Thanks,
Yingtian

2

Moved to Jetson Xavier forum(Jetson AGX Xavier - NVIDIA Developer Forums)

4

Hi,

Have you run the profiler with root?
The root authority is required to gather the GPU trace.

Thanks.

5

Hi,

We do have run the profiler with root. That’s what we have get after running with root. We were wondering if that is because we installed a separate version of Nsight instead of installing it through JetPack.

Thank you

6

There is no update from you for a period, assuming this is not an issue any more.
Hence we are closing this topic. If need further support, please open a new one.
Thanks

Is this still an issue to support? Any result can be shared?