After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791551 - [gstreamer-vaapi-master][iHD_SKL] [MPEG2_decode] "mpegvparse0: Internal data stream error" error message occurs during run mpeg2 decode cases with iHD driver on SKL
[gstreamer-vaapi-master][iHD_SKL] [MPEG2_decode] "mpegvparse0: Internal data ...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-12-13 06:52 UTC by zj,wang
Modified: 2018-11-03 15:52 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description zj,wang 2017-12-13 06:52:58 UTC
Test Env:
============================================
Platform:               SKL
Arch:          		x86_64
Kernel:			4.12.0-rc2
libva:			master branch df544cd5a31e54d4cbd33a391795a8747ddaf789 
                        repo: https://github.com/01org/libva.git
media_driver:		master branch 81796c8a9e44b878e26064c898e0f4730e8220cf
                        repo: https://github.com/intel/media-driver
gmmlib:                 repo: https://github.com/intel/gmmlib
gst-vaapi:		master branch b0d41c5db8c29b3df2a5b23d3da55141d701b992


Reproduce Steps:
============================================
1. build env as above lists or according to wiki https://github.com/intel/media-driver
2. take one case for example, run command
gst-launch-1.0 -q filesrc location=/media//yami_mpeg2/sony-ct2.bits.mpeg2 '!' mpegvideoparse '!' vaapimpeg2dec '!' vaapipostproc format=i420 '!' checksumsink2 frame-checksum=FALSE file-checksum=TRUE plane-checksum=FALSE
3. error info. as below
0:00:00.041989190  3619      0x1336230 ERROR            vaapidecode gstvaapidecode.c:716:gst_vaapidecode_handle_frame: decode error -1
0:00:00.052408344  3619      0x1336230 ERROR       vaapivideomemory gstvaapivideomemory.c:278:map_vaapi_memory: failed to make image current
0:00:00.052434276  3619      0x1336230 ERROR                default video-frame.c:161:gst_video_frame_map_id: failed to map video frame plane 0
0:00:00.052461787  3619      0x1336230 ERROR          checksumsink2 gstchecksumsink.c:381:gst_cksum_image_sink_render:<cksumimagesink0> failed to map frame
ERROR: from element /GstPipeline:pipeline0/GstMpegvParse:mpegvparse0: Internal data stream error.
Additional debug info:
gstbaseparse.c(3597): gst_base_parse_loop (): /GstPipeline:pipeline0/GstMpegvParse:mpegvparse0:
streaming stopped, reason error (-5)
d41d8cd98f00b204e9800998ecf8427e
Comment 1 Víctor Manuel Jáquez Leal 2017-12-13 09:09:03 UTC
Hi,

As far as I know, the VPG driver should comply with gstreamer-vaapi. If the pipeline fails, what should be fixed is the driver, not gstreamer-vaapi.

Can you confirm?
Comment 2 sreerenj 2017-12-14 17:54:56 UTC
The first step should be to make sure libva-utils API conformance testing is giving 100% success rate. Unfortunately, it is not and AFAIK some of the VA APIs are not yet implemented by iHD driver.

So I would prefer to wait a bit more before digging into gstreamer-vaapi to see what is missing in iHD driver.
Comment 3 Víctor Manuel Jáquez Leal 2018-08-29 05:40:55 UTC
What's the status of this bug? Still persist?
Comment 4 GStreamer system administrator 2018-11-03 15:52:14 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/75.