Nvargus-daemon - longterm stability issue

Robotics & Edge Computing Jetson & Embedded Systems Jetson AGX Orin
1

Hello everyone,

we are currently developing an application which captures frames from four MIPI cameras for further image processing and streaming.
For the acquisition part we are using the Jetson Linux API.

We noticed that after several hours the nvargus-daemon goes into an error state and does not provide further images. The error message is something like:

Module_id 30 Severity 2 : (fusa) Error: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaViHandler.cpp 817
Module_id 30 Severity 2 : (fusa) Error: InvalidState  propagating from:/capture/src/fusaViHandler.cpp 759

To make everything work again, we need to restart the nvargus-daemon.

To take our application out of the equation, I tried streaming with the argus_multi_camera example. I also received the same error messages. The launch syntax was the following:

argus_multi_camera -n 4 -c 2592000

Do you have any solution for this problem? I already tried boosting the VI/CSI/ISP clocks. This didn’t fix the problem, however. In Topic 268519 you provided a modified version of the libnvargus.so which should improve the stability. Is this still the preferred solution or do you have any other fix?

Our HW setup:

  • Jetson AGX Orin Industrial
  • JetPack 5.1.2

Best regards and thanks for your help
Markus

4

hello mrorelmy,

please apply pre-built update from below discussion threads for JP-5.1.2 camera bug fixes.
for instance,
Topic 268833, JP-5.1.2 camera firmware to update deskew algorithm, and also stability fixes
Topic 268519, fix memory corruption within libnvargus.

5

Hello JerryChang,

thank you for the quick response.

I currently have no physical access to the test systems, so I cannot apply the fix from Topic268833. I’ll try that as soon as the systems are back.

Regarding the fix from Topic268519:

We will conduct longterm tests with a customer shortly. Do you see any risk switching out the library this close to the tests?

And will these modifications be part of an official JetPack release at some point?

Best regards
Markus

6

hello mrorelmy,

there’s no risk by applying memory corruption fix as long as you’re based-on same Jetpack release (i.e. JP-5.1.2/r35.4.1)
besides, all of above update has also included in Jetpack-5.1.3 release version.

7

Hello JerryChang,

thank you very much for your help. I’ll mark this thread as resolved.

Best regards
Markus

9

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