V4l2bufferpool warning with RTSP Stream?

• Jetson Xavier NX
• DeepStream Version:5
• JetPack Version: 4.4

I have a deepstream-test5 modified app with a IP camera rtsp streaming inputs, but when I use GST_DEBUG=3, it always shows the following WARNING, how can I resolve this issue?

0:00:22.528577963 18730   0x55636370f0 WARN          v4l2bufferpool gstv4l2bufferpool.c:1480:gst_v4l2_buffer_pool_dqbuf:<sink_sub_bin_encoder2:pool:sink> V4L2 provided buffer has bytesused 0 which is too small to include data_offset 0
0:00:22.528710445 18730   0x55636370f0 WARN          v4l2bufferpool gstv4l2bufferpool.c:1480:gst_v4l2_buffer_pool_dqbuf:<sink_sub_bin_encoder2:pool:sink> V4L2 provided buffer has bytesused 0 which is too small to include data_offset 0
0:00:22.528770382 18730   0x55636370f0 WARN          v4l2bufferpool gstv4l2bufferpool.c:1480:gst_v4l2_buffer_pool_dqbuf:<sink_sub_bin_encoder2:pool:sink> V4L2 provided buffer has bytesused 0 which is too small to include data_offset 0
0:00:22.563724545 18730   0x7eec099800 FIXME              h265parse gsth265parse.c:1798:gst_h265_parse_parse_frame:<h265-parser> Implement timestamp/duration interpolation based on SEI message
0:00:22.564696622 18730   0x7eec099800 WARN           v4l2allocator gstv4l2allocator.c:1492:gst_v4l2_allocator_dqbuf:<sink_sub_bin_encoder2:pool:src:allocator> V4L2 provided buffer has bytesused 0 which is too small to include data_offset 0
0:00:22.564776495 18730   0x7eec099800 WARN          v4l2bufferpool gstv4l2bufferpool.c:1480:gst_v4l2_buffer_pool_dqbuf:<sink_sub_bin_encoder2:pool:src> V4L2 provided buffer has bytesused 0 which is too small to include data_offset 0
0:00:22.565385015 18730   0x55636370f0 FIXME              h265parse gsth265parse.c:1798:gst_h265_parse_parse_frame:<h265-parser> Implement timestamp/duration interpolation based on SEI message
0:00:22.575092888 18730   0x55636370a0 WARN          v4l2bufferpool gstv4l2bufferpool.c:1491:gst_v4l2_buffer_pool_dqbuf:<nvv4l2decoder0:pool:sink> v4l2 provided buffer that is too big for the memory it was writing into.  v4l2 claims 64 bytes used but memory is only 0B.  This is probably a driver bug.

Just ignore the warning is OK. The HW decoder does not support SEI header parsing, it will not impact decoding. DeepStream does not use any SEI information, so the warning is just to remind you that there is SEI in the stream. You can just ignore the warnings.

1 Like