<div dir="ltr">You probably want to install libglib2.0-0-dbg to resolve the "??"<div>Can you open a bug attaching full GST_DEBUG log, dmesg output (to get some info on the driver and kernel) and mesa version (or glxinfo output) ?</div><div>And output of "thread apply all bt" when it crashes.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 16 July 2017 at 12:41, rataj28 <span dir="ltr"><<a href="mailto:rataj28@gmail.com" target="_blank">rataj28@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hello,<br><br></div>I am writing and application which creates up to 12 encoding pipelines using vaapih264enc. It is working fine on Intel with i965 driver but it is very unstable on AMD using mesa gallium radeonsi driver. On radeonsi I can run up to 16 following pipelines as a separate gst-launch: <br><br>gst-launch-1.0 videotestsrc ! video/x-raw,width=1280,height=<wbr>1024 ! vaapih264enc ! testsink<br><br></div>I am not sure if it is relevant and gst-launch can be even used like this, but when I run it as a single gst-launch:<br><br>gst-launch-1.0 videotestsrc ! video/x-raw,width=1280,height=<wbr>1024 ! vaapih264enc ! testsink \<br> videotestsrc ! video/x-raw,width=1280,height=<wbr>1024 ! vaapih264enc ! testsink \<br> videotestsrc ! video/x-raw,width=1280,height=<wbr>1024 ! vaapih264enc ! testsink \<br> videotestsrc ! video/x-raw,width=1280,height=<wbr>1024 ! vaapih264enc ! testsink<br><br></div>I am able to run up to 6 pipelines with very unstable operation which is pretty much the same as I am getting from the real app. I am using latest mesa from git. <br><br>Setting pipeline to PAUSED ...<br>Pipeline is PREROLLING ...<br>Got context from element 'vaapiencodeh264-7': gst.vaapi.Display=context, gst.vaapi.Display=(<wbr>GstVaapiDisplay)"\(<wbr>GstVaapiDisplayDRM\)\ vaapidisplaydrm1";<br>0:00:01.726719568 5523 0x55b8d1a88b70 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa638002800<br>0:00:01.728399262 5523 0x55b8d1a88ad0 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa634002940<br>0:00:01.728645791 5523 0x55b8d1a88a30 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa640001c00<br>0:00:01.730375640 5523 0x55b8d1a8b8f0 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa63c002680<br>0:00:01.731129406 5523 0x55b8d1a8b8a0 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa624001d40<br>0:00:01.733516403 5523 0x55b8d1a88b20 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa61c001e80<br>0:00:01.740319994 5523 0x55b8d1a8b800 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa62c002a80<br>0:00:01.743724613 5523 0x55b8d1a8b850 ERROR vaapivideomemory gstvaapivideomemory.c:736:gst_<wbr>video_info_update_from_<wbr>surface: Cannot create a VA derived image from surface 0x7fa628001400<br>Pipeline is PREROLLED ...<br>Setting pipeline to PLAYING ...<br>New clock: GstSystemClock<br>Caught SIGSEGV<br>#0 0x00007fa66296a63d in poll () at ../sysdeps/unix/syscall-<wbr>template.S:84<br>#1 0x00007fa6632a5c16 in ?? () from /lib/x86_64-linux-gnu/libglib-<wbr>2.0.so.0<br>#2 0x00007fa6632a5fa2 in g_main_loop_run ()<br>#3 0x00007fa663a179c1 in gst_bus_poll (bus=0x55b8d18c9a30, <br>#4 0x000055b8cfb76bb0 in event_loop (pipeline=0x55b8d1ab21e0, blocking=1, <br>#5 0x000055b8cfb75b7e in main (argc=<optimized out>, argv=<optimized out>)<br><br>Vainfo output:<br><br>libva info: VA-API version 0.40.0<br>libva info: va_getDriverName() returns 0<br>libva info: User requested driver 'radeonsi'<br>libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/<wbr>radeonsi_drv_video.so<br>libva info: Found init function __vaDriverInit_0_40<br>libva info: va_openDriver() returns 0<br>vainfo: VA-API version: 0.40 (libva )<br>vainfo: Driver version: mesa gallium vaapi<br>vainfo: Supported profile and entrypoints<br> VAProfileMPEG2Simple <wbr> : VAEntrypointVLD<br> VAProfileMPEG2Main <wbr> : VAEntrypointVLD<br> VAProfileVC1Simple <wbr> : VAEntrypointVLD<br> VAProfileVC1Main <wbr> : VAEntrypointVLD<br> VAProfileVC1Advanced <wbr> : VAEntrypointVLD<br> VAProfileH264ConstrainedBaseli<wbr>ne: VAEntrypointVLD<br> VAProfileH264ConstrainedBaseli<wbr>ne: VAEntrypointEncSlice<br> VAProfileH264Main <wbr> : VAEntrypointVLD<br> VAProfileH264Main <wbr> : VAEntrypointEncSlice<br> VAProfileH264High <wbr> : VAEntrypointVLD<br> VAProfileH264High <wbr> : VAEntrypointEncSlice<br> VAProfileNone <wbr> : VAEntrypointVideoProc<br><br></div>What is the difference between running it as a single or separate processes in relation to vaapi? Do anyone have any experience with vaapi on radeonsi?<br><br></div>Thanks<br></div>Tomas<br><br></div>
<br>______________________________<wbr>_________________<br>
gstreamer-devel mailing list<br>
<a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.<wbr>freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/gstreamer-<wbr>devel</a><br>
<br></blockquote></div><br></div>