R32.3.1.tx2-4g gstream app fails to run nvargus_daemon message

I am using a lumenera camera.

my gstreamer app will not start/restart 100% of the time, I found that restarting the nvargus_daemon after every run on my app helps but it is not 100%, using dmesg --follow will give me messages like:
[ 4116.848757] syncpt_thresh_cpu0_int_status(0) = 0x00000000
[ 4116.848761] syncpt_thresh_cpu0_int_status(1) = 0x00000000
[ 4116.848765] syncpt_thresh_cpu0_int_status(2) = 0x00000000
[ 4116.848769] syncpt_thresh_cpu0_int_status(3) = 0x00000000
[ 4116.848772] syncpt_thresh_cpu0_int_status(4) = 0x00000000
[ 4116.848776] syncpt_thresh_cpu0_int_status(5) = 0x00000000
[ 4116.848779] syncpt_thresh_cpu0_int_status(6) = 0x00000000
[ 4116.848783] syncpt_thresh_cpu0_int_status(7) = 0x00000000
[ 4116.848786] syncpt_thresh_cpu0_int_status(8) = 0x00000000
[ 4116.848790] syncpt_thresh_cpu0_int_status(9) = 0x00000000
[ 4116.848793] syncpt_thresh_cpu0_int_status(10) = 0x00000000
[ 4116.848797] syncpt_thresh_cpu0_int_status(11) = 0x00000000
[ 4116.848801] syncpt_thresh_cpu0_int_status(12) = 0x00000000
[ 4116.848804] syncpt_thresh_cpu0_int_status(13) = 0x00000000
[ 4116.848808] syncpt_thresh_cpu0_int_status(14) = 0x00000000
[ 4116.848811] syncpt_thresh_cpu0_int_status(15) = 0x00000000
[ 4116.848815] syncpt_thresh_cpu0_int_status(16) = 0x00000000
[ 4116.848818] syncpt_thresh_cpu0_int_status(17) = 0x00000000

[ 4116.849069] ---- channels ----
[ 4116.849079]
channel 2 - 15820000.se

[ 4116.849082] NvHost basic channel registers:
[ 4116.849086] CMDFIFO_STAT_0: 00002040
[ 4116.849090] CMDFIFO_RDATA_0: 3340223b
[ 4116.849095] CMDP_OFFSET_0: 00000000
[ 4116.849099] CMDP_CLASS_0: 00000000
[ 4116.849102] CHANNELSTAT_0: 00000000
[ 4116.849105] The CDMA sync queue is empty.

[ 4116.849111]
channel 3 - 15830000.se

[ 4116.849113] NvHost basic channel registers:
[ 4116.849117] CMDFIFO_STAT_0: 00002040
[ 4116.849120] CMDFIFO_RDATA_0: 80232812
[ 4116.849125] CMDP_OFFSET_0: 00000000
[ 4116.849128] CMDP_CLASS_0: 00000000
[ 4116.849132] CHANNELSTAT_0: 00000000
[ 4116.849134] The CDMA sync queue is empty.

[ 4116.849140]
channel 4 - 15840000.se

Is there a better nvargus_daemon or some library available to make things more stable.


hello terrysu50z,

may I have more details about this lumenera camera, is this supported by Jetson Camera Partners?

there’re sync-point timeout errors from your kernel logs. it’s due to camera stack cannot receive frame signaling within a while.
it’s Sensor Pixel Clock for camera stack for calculation, you may review the sensor timing since you’re able to restart nvargus_daemon service to make it work sometimes.

Lumenera is a nvidia partner, it is a 8M camera.

I have seen isp in the dmesg’s might be releated to the 8M

Also reviewing forums, it might be related to cpu usage. My video app is using 180% of 4 cores, I have two turned off. So is the “nice” of nvargus_daemon maybe a factor here?

I forwarded the email to lumenera, hoping they will get back on the Sensor Pixel clock


hello terrysu50z,

could you please use top commands, and switch the mode to Irix mode by “I” (shift+i) to get average CPU usage.
please also refer to https://www.freebsd.org/cgi/man.cgi?top(1)

so my VideoSystem is using 44.3% using the “i” option, and nvargus-daemon is directly under it at 5.1%


hello terrysu50z,

before lumenera reply your question,
please check Applications Using V4L2 IOCTL Directly by using V4L2 IOCTL to verify basic camera functionality.

I ran the vctl-ctl command, when I did a ctrl-c I got
[ 1980.019899] ------------[ cut here ]------------
[ 1980.024534] WARNING: CPU: 0 PID: 12029 at drivers/media/v4l2-core/videobuf2-core.c:1667 __vb2_queue_cancel+0x11c/0x188
[ 1980.035367] —[ end trace 5d4aae212b22cc26 ]—

in the serial console, also ov5693.raw is zero length file.

what next?


hello terrysu50z,

v4l2-ctl is direct v4l2 interface to access the camera sensor, it’s used to validate sensor drivers.
so, here should be stability issue of lumenera camera. please contact with them for investigation.

after talking to the camera vendor, they pointed out that nvargus-daemon was crashing. Please fix nvargus-daemon in r32.3.1

hello terrysu50z,

you may upgrade the JetPack release to include the fixes.

we’re having some fixes for camera stack, there’re changes included in the latest JetPack release.
please refer to r32.5 Release Notes for further details.

My camera driver only works and is released for on r32.3.1, so how do I update r32.3.1

Also other hardware support is only tested with r32.3.1, it is not possible to change releases at this time.


hello terrysu50z,

please check with sensor vendor, we had deliver error resilience patches to several camera partners based-on r32.3.1.