We use the xavier module to connect 4 cameras.
With JetPack 4.6.1 , Use v4l2-ctl to capture the image, it stucks after a while with error log "tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 512 "or “tegra-camrtc-capture-vi tegra-capture-vi: corr_err: discarding frame 0, flags: 0, err_data 131072”
Top tools show the vi-ouput use system resource 100%
Here is the trace log: vi-output_100%.log (59.0 MB)
Yes, it outputs frames to CSI channel. Enable test-pattern, this issue did not reproduce.
The log shows" err_data 131072 (2000h) and 512 (200h) " when the mipi signal is bad, then vi-output thread goes to unnomal state.
I think it needs to reset vi channel and nvcsi stream when it happens.
am I understand correctly there’s MIPI signaling intermittent of your real use-case?
please see-also Topic 243051.
there’s known issue of nvarguscamera doesn’t recover from single NVCSI failure.
it turns out an issue of Argus error handling regression.
we’ve arrange resources for investigation, you should also expect this error handling mechanism won’t be fix soon.