Use argus to capture the image ,sometimes stopped with RCE error log

[1520864691]

error log : [RCE ERROR]: camera-ip/vi5/vi5.c:[vi5_handle_eof] “General error queue is out of sync with frame queue. ts=2181339514016 sof_ts=2181340183936 gerror_code=2 gerror_data=400062 notify_bits=0”

we used R35.3.1 argus to capture the image and one camera is 4k@60fps (lane rate over 1.5G),the other is 1080P@60fps

This error occurs from time to time, somtimes several hours ,sometimes over 48 hours
we have boost the clk ,but still exist this issue .
can you offer us some advice or have you met this issue before? thanks in advance.

[1520864691]

when this error occured ,the argus freezed and we can’t quit the argus app

[MarkusHoHo]

Hi @1520864691,

can you please share which Jetson board you are using, then I can forward you to the correct sub-forum on the topic.

Thanks!

[1520864691]

orin 64GB

[1520864691]

upload another condition which also show the same log ,when we just plug in a usb device .

[TomNVIDIA]

Hi, I will move this topic to the proper Jetson category.

[ShaneCCC]

Enable the trace log to check if any clue.

echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable

echo > /sys/kernel/debug/tracing/trace

[1520864691]

trace.zip (10.5 MB)
trace log upload

[ShaneCCC]

1. boost the clocks to try.

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

2. Confirm if below command have the same problem.

v4l2-ctl -c byoass_mode=0 --stream-mmap 

3. Below message tell sensor output unsupport data type. Check below link for the detail.
   Jetson/l4t/Camera BringUp - eLinux.org

     kworker/4:2-36521   [004] ....  5953.154901: rtcpu_vinotify_error: tstamp:186794408318 cch:2 vi:1 tag:CHANSEL_NOMATCH channel:0x04 frame:239 vi_tstamp:5977421042176 data:0x0000000000000249

     kworker/4:2-36521   [004] ....  5913.795036: rtcpu_vinotify_event: tstamp:185564233942 cch:1 vi:0 tag:CHANSEL_NOMATCH channel:0x01 frame:244 vi_tstamp:5938055356448 data:0x00000000000006e9

[1520864691]

sudo nvpmodel -m 0
sudo jetson_clocks
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

i have tried the above command ,will try v4l2-ctl -c byoass_mode=0 --stream-mmap

[1520864691]

using v4l2-ctl -c byoass_mode=0 --stream-mmap command also have the same issue,but we can still continue to capture the image

[ShaneCCC]

Replace the lib at /usr/lib/aarch64-linux-gnu/tegra/libnvfusacap.so to try.

libnvfusacap.so.35.3.1 (193.6 KB)

[1520864691]

We replaced the new file ,it seems to become stable ,but still stoped after seven hours. error log shown as above.

[1520864691]

another problem is that we can only open argus one time after power on , even we killed the argus process ,we must restart the board.

[ShaneCCC]

Restart the daemon by command. (sudo service nvargus-daemon restart)
Please update to r35.4.1 to try.

[1520864691]

you mean just replace to R35.4.1 argus ?

[ShaneCCC]

I mean update the system image to J5.1.2