Continuous assignAllBuffersFromStream Logs During Streaming on JP 6.1 / L4T 36.4

Robotics & Edge Computing Jetson Systems Jetson AGX Orin
1

We are observing continuous log messages from nvargus-daemon during camera streaming on our Jetson AGX Orin system running JetPack 6.1 / L4T 36.4. The messages are of the following form:

assignAllBuffersFromStream if ii 0 stream 0xffffacc63ed0 and buffer (nil) 281473550487696meout 7ff0000097f

These logs are flooding the console whenever streaming is active. Our setup details are:

  • Jetson AGX Orin 64GB

  • JetPack 6.1 / L4T 36.4

  • Using cameras in trigger mode (IMX568)The logs appear continuously during streaming, even when no apparent error occurs

  1. Could you confirm where in the JP 6.1 / L4T 36.4 Argus source the assignAllBuffersFromStream print originates?

  2. Is this expected behavior, or is it possible to reduce or disable this logging?

  3. Are there any recommended patches or configuration changes to prevent this flood of log messages without affecting streaming functionality?

Any guidance would be greatly appreciated.

Thank you.

2

*** Please note that this reply is generated by LLM automatically ***

The issue you’re experiencing with continuous log messages during camera streaming on your Jetson AGX Orin system running JetPack 6.1 (L4T 34.1) is likely related to the RCE (Robotics and Edge Computing) firmware and the camera driver.

Comparing your setup with the context provided, it appears that you’re using a similar setup as the one described in the topic “[RCE] ISR PHY 0 CIL_A 0x88” where the user is experiencing issues with the EV9500M driver on Jetson Orin Nano with JetPack 6.2.

The logs you’re seeing are likely originating from the RCE firmware, which is responsible for handling the camera interface. The messages are probably being printed by the tegra_csi driver, which is part of the Argus source code.

To confirm this, you can check the Argus source code and look for the tegra_csi driver. You can also try to disable the logging by modifying the tegra_csi driver or by applying a patch to reduce the logging level.

However, before making any changes, it’s essential to understand that the logging is likely there for a reason, and disabling it might mask underlying issues. It’s recommended to investigate the root cause of the logs and address any potential problems before attempting to disable the logging.

In comparison, the topic “CSI-0 with MIPI 4 lane is not working properly” on Jetson Orin Nano with JetPack 6.2 also mentions issues with the camera interface, but the logs are different. This suggests that the issue you’re experiencing might be specific to your setup or the RCE firmware version.

To resolve the issue, you can try the following:

  1. Check the RCE firmware version and ensure it’s up-to-date.
  2. Verify that the camera driver is correctly configured and that the camera is properly connected.
  3. Investigate the root cause of the logs and address any potential problems.
  4. If necessary, modify the tegra_csi driver or apply a patch to reduce the logging level.

It’s also recommended to consult the Jetson AGX Orin documentation and the Argus source code for more information on the tegra_csi driver and the RCE firmware.

In summary, the continuous log messages during camera streaming on your Jetson AGX Orin system are likely related to the RCE firmware and the camera driver. To resolve the issue, you should investigate the root cause of the logs, verify the camera configuration, and consider modifying the tegra_csi driver or applying a patch to reduce the logging level.

*** Please give the thumbs up if you get answers you like. Or provide feedback to help us improve the answer. ***

4

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

6

We are still observing the same log prints while the camera streaming is active, which continuously fill up the journalctl logs. However, the streaming has been verified to be functioning correctly without any issues.

7

What’s the use case and reproduce steps?

8

We are using the cameras for object tracking. The issue can be reproduced by simply starting the camera stream in gstreamer, after which the nvargus-daemon continuously logs messages which can be seen in the journalctl

9

Single camera? How about simple command like below?

gst-launch-1.0 nvarguscamerasrc ! 'video/x-raw(memory:NVMM), width=(int)1920, height=(int)1080' ! nvvidconv ! fpsdisplaysink video-sink=fakesink
12

just an FYI,
the repeated message (i.e. assignAllBuffersFromStream) itself does not indicate a streaming failure or memory leak.

for those user need to stay on JetPack-6.1/r36.4.
here’s [Bug6840153_Sep29_2.zip (2.5 MB)] which removes specific debug prints to eliminate the log flooding, while retaining normal streaming behavior and other error logging.