The INvMCallback is not scheduled timely

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

Target Operating System
[√] Linux

Hardware Platform
NVIDIA DRIVE™ AGX Xavier DevKit (E3550)
[√] NVIDIA DRIVE™ AGX Pegasus DevKit (E3550)

SDK Manager Version

Host Machine Version
[√] native Ubuntu 18.04

Hi NVIDIA experts.
We have encountered some tricky issues.

We use the nvsipl::INvSIPLClient::INvMCallback method to receive the camera stream in driveos 5.2.0. This callback function is expected to be scheduled every 33ms (camera in 30FPS). In the vast majority of cases, callback functions can be scheduled for execution timely.

However, we occasionally encounter situations where callback functions are not scheduled for over a hundred milliseconds. For example, the nvmedia image timestamp is at the time point 1000ms, the callback function with this image is schedule at time point 1200ms.
We currently have no way to reproduce this problem. The cpu usage of the process is not high (abort 30%-40%).

May I ask if NVIDIA has encountered similar problems before and how did you solve them? Can you provide some methods and tools to further locate the problem?


Have you encountered this issue while using any sample applications, and do you have access to any relevant logs? Based on our records, we haven’t come across this particular issue. Also, we recommend upgrading to the latest version (5.2.6) to see if the issue persists.

Thanks @VickNV .
We could not reproduce this problem in sample case, and it is very difficult for us to upgrade 5.2.6.
I would like to ask how this INvMCallback callback is triggered in the framework of nvsipl? Will it be based on soft irqs? When the driver receive the image, how does it notify nvsipl’s callback to execute it?


Please elaborate on the issue and provide the logs to understand the problem first.
If you’re encountering issues with this callback, it would be helpful if you could provide more details about the problem you’re facing. Sharing logs or error messages related to the issue can assist in understanding the situation more effectively. This will enable us to provide you with more accurate guidance and solutions.

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