We are using the Jetson AGX Xavier with a camera carrier board from Leopard Imaging (LI-JXAV-MIPI-ADPT-4CAM V1.0) with 3 cameras connected. The Jetson AGX Xavier is running Jetson Linux release: R35.4.1 JetPack release: 5.1.2 built and deployed with Yocto based on the Kirkstone branch of meta-tegra. We are also running a custom driver supplied by Leopard Imaging on top of the Jetson Linux release.
With this setup we are currently seeing errors in the nvargus-daemon after anything from 20 minutes to several hours when running gstreamer video pipelines. The first error lines are usually the following:
Nov 27 12:25:35 E2-028 nvargus-daemon[1954291]: SCF: Error InvalidState: Corr Error Received for sensor 4 .. Continuing!
Nov 27 12:25:35 E2-028 nvargus-daemon[1954291]: (in src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 643)
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: SCF: Error Timeout: (propagating from src/components/amr/Snapshot.cpp, function waitForNewerSample(), line 91)
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: SCF_AutocontrolACSync failed to wait for an earlier frame to complete.
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: SCF: Error Timeout: (propagating from src/components/ac_stages/ACSynchronizeStage.cpp, function doHandleRequest(), line 126)
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: SCF: Error Timeout: (propagating from src/components/stages/OrderedStage.cpp, function doExecute(), line 137)
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: SCF: Error Timeout: Sending critical error event for Session 4
Nov 27 12:25:36 E2-028 nvargus-daemon[1954291]: (in src/api/Session.cpp, function sendErrorEvent(), line 1039)
Nov 27 12:25:39 E2-028 nvargus-daemon[1954291]: (Argus) Error OverFlow: Too many pending events, ignoring new events (in src/api/EventProviderImpl.cpp, function addEvent(), line 158)
Nov 27 12:25:39 E2-028 nvargus-daemon[1954291]: (Argus) Error OverFlow: Too many pending events, ignoring new events (in src/api/EventProviderImpl.cpp, function addEvent(), line 158)
Attached are the script used to start these pipelines, the logs from the gstreamer pipeline and the log from nvargus-daemon. When nvargus-daemon crashes we need to first stop the gstreamer application, then restart nvargus-daemon, then we can start the gstreamer pipeline again.
We can currently not run our camera stack since nvargus-daemon hangs after these errors and have to be restarted.
test_dual_argus.txt (937 Bytes)
crash_nvargus_daemon.txt (1.3 MB)
crash_client.txt (147.7 KB)