gstreamer/H264 spurious warnings "This is probably a driver bug"

Robotics & Edge Computing Jetson & Embedded Systems Jetson TX2
1

When sending a H264 stream like so:

gst-launch-1.0 videotestsrc ! 'video/x-raw, width=(int)1280, height=(int)720, format=(string)I420, framerate=(fraction)30/1' ! nvvidconv ! nvv4l2h264enc iframeinterval=1 preset-level=1 profile=0 quant-i-frames=20  ! 'video/x-h264, stream-format=(string)byte-stream' ! h264parse ! "video/x-h264, stream-format=byte-stream, alignment=nal"  ! rtph264pay ! udpsink host=127.0.0.1 port=5004

And receiving like so (notice GST_DEBUG=4):

GST_DEBUG=4 gst-launch-1.0 udpsrc address=127.0.0.1 port=5004 ! "application/x-rtp,encoding-name=H264" ! rtpjitterbuffer latency=100 ! rtph264depay ! "video/x-h264, stream-format=byte-stream, alignment=(string)nal" ! h264parse ! nvv4l2decoder enable-full-frame=true enable-max-performance=true disable-dpb=true ! nv3dsink sync=false

The following warnings are output on each GstBuffer:

.......
0:00:08.282293722 12907   0x558da44a30 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 1008 bytes used but memory is only 0B.  This is probably a driver bug.
0:00:08.314542049 12907   0x558da44a30 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 1008 bytes used but memory is only 0B.  This is probably a driver bug.
0:00:08.348103427 12907   0x558da44a30 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 1008 bytes used but memory is only 0B.  This is probably a driver bug.
0:00:08.382073029 12907   0x558da44a30 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 1008 bytes used but memory is only 0B.  This is probably a driver bug.
....

The video shows up just fine, but the warnings are flooding the log files.

Is this a known issue at NVIDIA?
Is there a work-around?

2

This is known and should be harmless. See the links here.

1 Like