Nvbuf_utils: dmabuf_fd -1 mapped entry NOT found

Hi,
I am supporting a camera module on B00/01 carrier of NANO.

  1. use the following command is OK :
    v4l2-ctl --set-fmt-video=width=2560,height=1440,pixelformat=BG10 --stream-mmap --set-ctrl=sensor_mode=0 --stream-count=1 --stream-poll -d /dev/video0 --stream-to=test.raw
    I got test.raw, but use 7yuv what it’s supposed to look like. so i use the second command.
  2. the second command as follows:
    gst-launch-1.0 nvarguscamerasrc num-buffers=200 ! ‘video/x-raw(memory:NVMM),width=2560, height=1440, framerate=30/1, format=NV12’ ! omxh264enc ! qtmux ! filesink location=test.mp4 -e
    The command fail, and the log as follows:
    $ gst-launch-1.0 nvarguscamerasrc num-buffers=200 ! ‘video/x-raw(memory:NVMM),width=2560, height=1440, framerate=30/1, format=NV12’ ! omxh264enc ! qtmux ! filesink location=test.mp4 -e
    Setting pipeline to PAUSED …

Using winsys: x11
Pipeline is live and does not need PREROLL …
Got context from element ‘eglglessink0’: gst.egl.EGLDisplay=context, display=(GstEGLDisplay)NULL;
Setting pipeline to PLAYING …
New clock: GstSystemClock
GST_ARGUS: Creating output stream
CONSUMER: Waiting until producer is connected…
GST_ARGUS: Available Sensor modes :
GST_ARGUS: 2560 x 1440 FR = 29.999999 fps Duration = 33333334 ; Analog Gain range min 1.000000, max 10.625000; Exposure Range min 13000, max 683709000;

GST_ARGUS: Running with following settings:
Camera index = 0
Camera mode = 0
Output Stream W = 2560 H = 1440
seconds to Run = 0
Frame Rate = 29.999999
GST_ARGUS: Setup Complete, Starting captures for 0 seconds
GST_ARGUS: Starting repeat capture requests.
CONSUMER: Producer has connected; continuing.
nvbuf_utils: dmabuf_fd -1 mapped entry NOT found
nvbuf_utils: Can not get HW buffer from FD… Exiting…
CONSUMER: ERROR OCCURRED
ERROR: from element /GstPipeline:pipeline0/GstNvArgusCameraSrc:nvarguscamerasrc0: CANCELLED
Additional debug info:
Argus Error Status
EOS on shutdown enabled – waiting for EOS after Error
Waiting for EOS…
(Argus) Error EndOfFile: Unexpected error in reading socket (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadCore(), line 266)
(Argus) Error EndOfFile: Receiving thread terminated with error (in src/rpc/socket/client/ClientSocketManager.cpp, function recvThreadWrapper(), line 368)
^C handling interrupt.
Interrupt: Stopping pipeline …
Interrupt while waiting for EOS - stopping pipeline…
Execution ended after 0:00:09.976269100
Setting pipeline to PAUSED …
Setting pipeline to READY …
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
GST_ARGUS: Cleaning up
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
(Argus) Error InvalidState: Receive thread is not running cannot send. (in src/rpc/socket/client/ClientSocketManager.cpp, function send(), line 96)
(Argus) Error InvalidState: (propagating from src/rpc/socket/client/SocketClientDispatch.cpp, function dispatch(), line 91)
Caught SIGSEGV
Caught SIGSEGV
[ 1255.010805] host1x 50000000.host1x: cdma_handle_timeout: timeout: 31 (54080000.vi_1) client 39, HW thresh 0, done 1
[ 1255.022457] host1x 50000000.host1x: cdma_handle_timeout: timeout: 35 (54080000.vi_4) client 39, HW thresh 0, done 1
[ 1255.032926] host1x 50000000.host1x: cdma_handle_timeout: timeout: 32 (54080000.vi_2) client 39, HW thresh 2, done 2
[ 1255.159614] host1x 50000000.host1x: cdma_handle_timeout: timeout: 17 (54680000.isp_0) client 32, HW thresh 9, done 10
[ 1255.170299] host1x 50000000.host1x: cdma_handle_timeout: timeout: 18 (54680000.isp_1) client 32, HW thresh 9, done 10
[ 1255.180932] host1x 50000000.host1x: cdma_handle_timeout: timeout: 20 (54680000.isp_3) client 32, HW thresh 9, done 10
[ 1255.191550] host1x 50000000.host1x: cdma_handle_timeout: timeout: 19 (54680000.isp_2) client 32, HW thresh 47, done 47

My question is what could possibly be causing this?
Thanks!

Have a check below command if able capture continuously.

v4l2-ctl --set-fmt-video=width=2560,height=1440,pixelformat=BG10 --stream-mmap --set-ctrl=sensor_mode=0 --stream-count=500

@ShaneCCC Thanks for your reply.
$ v4l2-ctl --set-fmt-video=width=2560,height=1440,pixelformat=BG10 --stream-mmap --set-ctrl=sensor_mode=0 --stream-count=500
[ 117.891662] vi 54080000.vi: tegra_channel_error_status:error 22 frame 0
<<<<<<<<< 7.40 fps
<<<<<<< 7.42 fps
<<<<<<<< 7.41 fps
<<<<<<< 7.40 fps
<<<<<<< 7.40 fps
<<<<<<<< 7.40 fps
<<<<<<< 7.40 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.40 fps
<<<<<<< 7.40 fps
<<<<<<<< 7.40 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.40 fps
<<<<<<<< 7.40 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<<<<<< 7.39 fps
<<<<<<< 7.39 fps
<<<

Looks like have chance capture failed. Maybe try modify the discontinuous_clk in device tree to try.

tegra_channel_error_status:error 22 frame 0

@ShaneCCC You are right. Great! Thanks for your reply.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.