[FFmpeg-user] Failed creating CUDA context for NVENC

Dennis Mungai dmngaie at gmail.com
Wed Jul 18 22:34:06 EEST 2018


NVENC runs on a discrete silicon IP core (SIP) block in the GPU, and not on
the GPU's shaders.
That SIP block has hard-coded limits (set in firmware) to ensure that these
who need more than the artificial limit buy Tesla-grade hardware.

Marketing shills by NVIDIA.

You can override this limit by using Keylase's nvidia patcher here:
https://github.com/keylase/nvidia-patch

On 18 July 2018 at 22:00, Yugandhar Veeramachaneni <hello at yugandhar.me>
wrote:

> I'm a little confused here because the GPU resource utilization is well
> below the hard limits.
>
> When I run nvidia-smi, this is what I get -
>
> yugandharv at eclairs:~$ nvidia-smi
> Thu Jul 19 00:29:45 2018
> +-----------------------------------------------------------
> ------------------+
> | NVIDIA-SMI 390.67                 Driver Version:
> 390.67                    |
> |-------------------------------+----------------------+----
> ------------------+
> | GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr.
> ECC |
> | Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute
> M. |
> |===============================+======================+====
> ==================|
> |   0  Quadro P4000        Off  | 00000000:02:00.0 Off |
> N/A |
> | 52%   55C    P0    38W / 105W |   6646MiB /  8117MiB |     25%
> Default |
> +-------------------------------+----------------------+----
> ------------------+
>
>
> +-----------------------------------------------------------
> ------------------+
> | Processes:                                                       GPU
> Memory |
> |  GPU       PID   Type   Process name
> Usage      |
> |===========================================================
> ==================|
> |    0       983      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0       995      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0      1010      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0      1012      C   /home/yugandharv/bin/ffmpeg
> 215MiB |
> |    0      1017      C   /home/yugandharv/bin/ffmpeg
> 235MiB |
> |    0      1986      C   /home/yugandharv/bin/ffmpeg
> 224MiB |
> |    0      8484      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0      8497      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0      8538      C   /home/yugandharv/bin/ffmpeg
> 225MiB |
> |    0     11097      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     11109      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     11121      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     11134      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11169      C   /home/yugandharv/bin/ffmpeg
> 225MiB |
> |    0     11175      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     11186      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11195      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11207      C   /home/yugandharv/bin/ffmpeg
> 224MiB |
> |    0     11222      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11226      C   /home/yugandharv/bin/ffmpeg
> 225MiB |
> |    0     11231      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11234      C   /home/yugandharv/bin/ffmpeg
> 225MiB |
> |    0     11235      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11237      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11240      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11252      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     11300      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> |    0     13264      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     14176      C   /home/yugandharv/bin/ffmpeg
> 193MiB |
> |    0     30258      C   /home/yugandharv/bin/ffmpeg
> 229MiB |
> +-----------------------------------------------------------
> ------------------+
>
>
> Thanks,
>
> Yugandhar
>
> On Wed, Jul 18, 2018 at 11:55 AM Dennis Mungai <dmngaie at gmail.com> wrote:
>
> > You mentioned 30 streams. And more cause this to "fail".
> >
> > Perhaps the Quadro line has a maximum simultaneous encoder limit of 30,
> > similar to the GeForce's limit of 2?
> >
> > On Wed, Jul 18, 2018, 19:28 Yugandhar Veeramachaneni <hello at yugandhar.me
> >
> > wrote:
> >
> > > Hello everyone,
> > >
> > > I'm currently using an NVIDIA Quadro P4000 GPU to transcode multicast
> UDP
> > > streams to RTMP streams. I have quite about 30 streams running in
> > parallel
> > > on this GPU and I have no problems so far. I tried adding more today
> and
> > > many of them are failing with this error.
> > >
> > > [h264_nvenc @ 0x55ef24458040] Loaded Nvenc version 8.1
> > > [h264_nvenc @ 0x55ef24458040] Nvenc initialized successfully
> > > [h264_nvenc @ 0x55ef24458040] 1 CUDA capable devices found
> > > [h264_nvenc @ 0x55ef24458040] [ GPU #0 - < Quadro P4000 > has Compute
> SM
> > > 6.1 ]
> > > [h264_nvenc @ 0x55ef24458040] Failed creating CUDA context for NVENC:
> 0x2
> > > [h264_nvenc @ 0x55ef24458040] No NVENC capable devices found
> > > [h264_nvenc @ 0x55ef24458040] Nvenc unloaded
> > >
> > > Full log is pasted at
> > > https://gist.github.com/yugandhar91/47a1c30482d1e89a47f7b6fb6dd420ca
> > >
> > > Can you please point me to my mistake?
> > >
> > > Thanks,
> > >
> > > Yugandhar
> > > _______________________________________________
> > > ffmpeg-user mailing list
> > > ffmpeg-user at ffmpeg.org
> > > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> > >
> > > To unsubscribe, visit link above, or email
> > > ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> > To unsubscribe, visit link above, or email
> > ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
>


More information about the ffmpeg-user mailing list