Nvsipl_query sample memory allocation error

Autonomous Vehicles DRIVE AGX Orin DRIVE AGX Orin General
1

Please provide the following info (tick the boxes after creating this topic):
Software Version
DRIVE OS 6.0.6
DRIVE OS 6.0.5
DRIVE OS 6.0.4 (rev. 1)
DRIVE OS 6.0.4 SDK
other

Target Operating System
Linux
QNX
other

Hardware Platform
DRIVE AGX Orin Developer Kit (940-63710-0010-300)
DRIVE AGX Orin Developer Kit (940-63710-0010-200)
DRIVE AGX Orin Developer Kit (940-63710-0010-100)
DRIVE AGX Orin Developer Kit (940-63710-0010-D00)
DRIVE AGX Orin Developer Kit (940-63710-0010-C00)
DRIVE AGX Orin Developer Kit (not sure its number)
other

SDK Manager Version
1.9.2.10884
other

Host Machine Version
native Ubuntu Linux 20.04 Host installed with SDK Manager
native Ubuntu Linux 20.04 Host installed with DRIVE OS Docker Containers
native Ubuntu Linux 18.04 Host installed with DRIVE OS Docker Containers
other

When running the sipl_query we get this error:

libnvsipl_query.so: CNvmQuery.cpp : 75: GetDriverLibraries -memory allocation error for ldLibraryBuffer
libnvsipl_query.so: CNvMQuery.cpp : 126: ParseDatabase: Failed to find query json librariesError parsing NvSIPL database. Error code10
2

Thank you for reaching out. Based on my initial assessment, there doesn’t seem to be an issue on my end. To assist you better, could you please provide the complete command line you used and the corresponding full output? This information would greatly help me understand the context and work towards resolving the issue. Thank you in advance for your cooperation.

3

Went to the folder:

/usr/local/driveworks/tools/sensors/

Ran the command

./nvsipl_query

This occasionally shows up, sometimes it works, sometimes it fails and presents the error.

4

It seems that the issue you’re experiencing is not reproducible on my end. I’ve tried running the command “nvsipl_query” multiple times, and it worked without any errors. In order to assist you further, could you please provide the full output of “nvsipl_query” when the issue occurs?

5

Seems like the issue just went away, and it is now launching correctly. Will reach out if it shows up again.
As for a solution, we didn’t change anything, just rebooted the device and it now functions.

Are there some memory limitations or constraints applied to the system that we should be aware of? Can we set a higher buffer?

6

The error is likely related to the length of the value assigned to the ‘LD_LIBRARY_PATH’ variable, which appears to exceed the allowed limit.

7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.