Camera failed: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaViHandler.cpp 817

Do you know what this message is about:
Nov 18 01:15:44 orin2 nvargus-daemon[1016]: Module_id 30 Severity 2 : (fusa) Error: InvalidState Status syncpoint signaled but status value not updated in:/capture/src/fusaViHandler.cpp 817
Nov 18 01:15:44 orin2 nvargus-daemon[1016]: Module_id 30 Severity 2 : (fusa) Error: InvalidState propagating from:/capture/src/fusaViHandler.cpp 759
Nov 18 01:15:44 orin2 nvargus-daemon[1016]: SCF: Error InvalidState: (propagating from src/services/capture/FusaCaptureViCsiHw.cpp, function waitCsiFrameEnd(), line 593)
Nov 18 01:15:44 orin2 nvargus-daemon[1016]: SCF: Error InvalidState: (propagating from src/common/Utils.cpp, function workerThread(), line 114)
Nov 18 01:15:44 orin2 nvargus-daemon[1016]: SCF: Error InvalidState: Worker thread ViCsiHw frameComplete failed (in src/common/Utils.cpp, function workerThread(), line 133)
It happens occasionally, sometimes after an hour or few hours of successfully running 2 MIPI cameras on Orin with “# R35 (release), REVISION: 1.0, GCID: 31346300, BOARD: t186ref, EABI: aarch64, DATE: Thu Aug 25 18:41:45 UTC 2022”

Thank you

hello jhnlmn,

can you confirm the camera functionality, is this only happened for long-run test?
those failure looks due to stream stability issue, that’s shown something wrong on the frame-end.
may I know what’s the camera sensor it is,
were they also tested on previous JetPack release on AGX Xavier series?

Hi,
Yes, I am now running long-run tests almost continuously and all kind of errors come out, most of them intermittently. fusaViHandler.cpp 817 is just one of them.
I am using a couple of different Omnivision sensors.
I am only testing with Orin.
Could you, please, tell me more about this stream stability?
Is there something I should pay attention to?
Could this particular error be caused by some camera error, like a missed frame or mipi noise, or could it be in processing, may be in Cuda?
Thank you

hello jhnlmn,

this may depends-on system configuration.
in order to narrow down the issue, please try below commands to boost all the VI/CSI/ISP clocks.
for example,

sudo su
echo 1 > /sys/kernel/debug/bpmp/debug/clk/vi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/isp/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/nvcsi/mrq_rate_locked
echo 1 > /sys/kernel/debug/bpmp/debug/clk/emc/mrq_rate_locked
cat /sys/kernel/debug/bpmp/debug/clk/vi/max_rate |tee /sys/kernel/debug/bpmp/debug/clk/vi/rate
cat /sys/kernel/debug/bpmp/debug/clk/isp/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/isp/rate
cat /sys/kernel/debug/bpmp/debug/clk/nvcsi/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/nvcsi/rate
cat /sys/kernel/debug/bpmp/debug/clk/emc/max_rate | tee /sys/kernel/debug/bpmp/debug/clk/emc/rate