DS 4.0, cannot run demo apps on Tesla T4

Accelerated Computing Intelligent Video Analytics DeepStream SDK
1

Hi,

We have downloaded and installed the newly released DS 4.0 on a server with two T4 cards. The installation is smooth following the Guidance. However when trying to run the deepstream-app and deepstream-test1-app, these error occurred after pipeline is set to running:

ERROR from sink_sub_bin_encoder1: Device '/dev/nvhost-msenc' failed during initialization
Debug info: gstv4l2object.c(4050): got_v4l2_object_set_format_full (): /GstPipeline:pipeline/GstBin:processing_bin_0/GstBin:sink_bin/GstBin:sink_sub_bin1/nvv4l2h265enc:sink_sub_bin_encoder1:
Call to S_FMT failed for YM12 @ 1280x720: Unknown error -1

and this repeats a few times before the application quits.

We tried both H264 and H265 encoding, and switched between video file src and live RTSP stream, getting the same error.

So we tried again with gst-launch-1.0, copied the command from the FAQ, just got the same result. However, when replacing the sink with gst’s fakesink, the pipeline works (though nothing is displayed, of course). Disabled all sinks in config file of deepstream-app also results like this, running pipeline without error nor video stream, by using a default fakesink.

The dumped .dot graph shows the encoder nvv4l2h264enc tried to access device /dev/nvhost-msenc without success, just like the error above complained. It looks like the hardware encoder on T4.
But ls /dev/ cannot find such device, nor any other /dev/nvhost-* devices. A quick search reports such devices are used in Jetson, but no result in Tesla webpages.

Help is appreciated, thank you!

2

To add information to the above.

I get this exact same error running the docker container on ubuntu 18.04 as well. I’m using this container. nvcr.io/nvidia/deepstream:4.0-19.07.

There is no /dev/nvhost-msenc within the container, is something I’ve negelected to install on ubuntu?

3

For me, I only get the above error when I enable the RTSP sink in the config.

However, with the env variable GST_DEBUG=4, I get the following output when the RTSP sink is either enabled or disabled:

v4l2 gstv4l2object.c:2072:gst_v4l2_object_get_interlace_mode: Driver bug detected - check driver with v4l2-compliance from http://git.linuxtv.org/v4l-utils.git

It seems like these error messages might be related, but only crash the app when the RTSP sink is enabled.

4

Update:

After re-installing the latest Nvidia driver from official website (and reboot), the problem seems gone.

Both driver versions are 418.67, we don’t know the exact difference since previous installation is gone.
There is still no /dev/nvhost-msenc listed, but the program no longer complains about it.
Also the device="/dev/nvhost-msenc" property can be seen in dumped .dot graph, in sink_sub_bin_encoder1 of type nvv4l2h265enc as before.

Hope this helps.

5

Have the same issue with:

Tried re-install the driver, reboot system, update docker, etc… no result

running

deepstream-app -c configs/deepstream-app/source30_1080p_dec_infer-resnet_tiled_display_int8.txt

with RTSP out and receive the error:

ERROR from sink_sub_bin_encoder1: Device '/dev/nvhost-msenc' failed during initialization
Debug info: gstv4l2object.c(4050): gst_v4l2_object_set_format_full (): /GstPipeline:pipeline/GstBin:processing_bin_0/GstBin:sink_bin/GstBin:sink_sub_bin1/nvv4l2h264enc:sink_sub_bin_encoder1:
Call to S_FMT failed for YM12 @ 1280x720: Unknown error -1

Any help is highly appreciated.

6

Tested with DeepStream SDK 3.0 and nvcr.io/nvidia/deepstream:3.0-18.11
The rest is the same as in previous post.

deepstream-app -c configs/deepstream-app/source4_720p_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt
 deepstream-app -c configs/deepstream-app/source30_720p_dec_infer-resnet_tiled_display_int8.txt

Works with RTSP without any issues. Seems there is something wrong with nvcr.io/nvidia/deepstream:4.0-19.07

Can someonetake a look?

7

Well. After installing, rebooting, re-installing on host ubuntu everything I was able to run samples without issues. Not in docker container. I’ll test docker image a bit later.

Thanks :)

8

Receiving the same set of issues with deep stream container 4.0-19.07, whenever I enable sink[1] to write rendered out.mp4 file it gives me this error on Tesla T4.

9

Having the same issues with the following configuration:

nvv4l2h264enc:sink_sub_bin_encoder1:
Call to S_FMT failed for YM12 @ 1280x720: Unknown error -1
ERROR from sink_sub_bin_encoder1: Device '/dev/nvhost-msenc' failed during initialization
Debug info: gstv4l2object.c(4050): gst_v4l2_object_set_format_full (): /GstPipeline:pipeline/GstBin:processing_bin_0/GstBin:sink_bin/GstBin:sink_sub_bin1/

The following error occurs when using either save to file sink or rtsp stream sink.

10

same issue here: