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 775689 - vaapi: yocto: haswell: random hang
vaapi: yocto: haswell: random hang
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer-vaapi
1.8.0
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-12-06 09:23 UTC by tadala veerannababu
Modified: 2017-08-09 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description tadala veerannababu 2016-12-06 09:23:50 UTC
This is a little outline of my current investigations:

Observed random hang issue while using gstreamer-vaapi plugins(decoder, encoder, postproc and vaapisink) on intel haswell platform. This image was build using krogoth version(kernel-4.4) of yocto. 

Didn't observe the same when daisy version(kernel-3.10) of yocto get used on same platform.

Did the following tests but didn't helped.

1. Tried different version of gstreamer-vaapi that didn't helped.

2. Tried all by copying all the gstreamer-vaapi libs and its depends(libva and intel driver) from daisy to krogoth. 

I am currently looking for some suggestions from your side. Please let me know if you need more information.

Thanks In advance,
Veeranna.
Comment 1 Víctor Manuel Jáquez Leal 2016-12-06 10:02:45 UTC
We need to figure out the cause of the hang. What does exactly mean "hang"? Do you have a use case where the hang can be reproduced? What is the libva and libva-intel-driver version? what kernel version are you using now?

Did you report this to the yocto packagers? Have you tried with debian or fedora?
Comment 2 tadala veerannababu 2016-12-08 10:43:11 UTC
Observed system hang i.e need to restart it for further usage.I am using 1.7.0 version of libva ,libva-intel driver. kernel version is 4.4.

I have tried the kernel version 4.8, observed the same behaviour. Tried only debian and haven't reported to yocto packagers.
Comment 3 Víctor Manuel Jáquez Leal 2016-12-08 13:12:53 UTC
Are you using a specific board?

How to you reproduce the hang (a specific media with a specific pipeline)? 
What's in the kernel logs?

So far this bug report is very ambiguous.
Comment 4 tadala veerannababu 2016-12-08 16:52:34 UTC
I was building krogoth version of yocto project for haswell desktop version.

Ran the multiple instances of below pipeline to re create this issue.

gst-launch-1.0 rtspsrc location=rtsp://192.168.1.109:8558/pp ! rtph264depay ! h264parse ! 'video/x-h264, stream-format=byte-stream' ! vaapidecode ! queue ! vaapih264enc min-qp=20 dct8x8=TRUE ! h264parse ! 'video/x-h264, stream-format=byte-stream' ! filesink name=fs2 location=dump.264

Didn't observe any error logs from kernel.
Comment 5 Víctor Manuel Jáquez Leal 2017-01-18 17:13:14 UTC
Sorry for the late reply.

It's very difficult to know what is happening in your case without extra information. Or without a way to reproduce easily the problem.

Can you get gstreamer logs? GST_DEBUG=*:3,vaapi*:5
Comment 6 Víctor Manuel Jáquez Leal 2017-08-09 09:55:24 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!