Bug 79660 - low ssim value with hhi_burst_long.bits and hhi_burst_short.bits
Summary: low ssim value with hhi_burst_long.bits and hhi_burst_short.bits
Status: CLOSED NOTOURBUG
Alias: None
Product: libva
Classification: Unclassified
Component: intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: ykzhao
QA Contact: Sean V Kelley
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-05 03:05 UTC by zhixinx.liu
Modified: 2014-07-10 01:35 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description zhixinx.liu 2014-06-05 03:05:15 UTC
low ssim value when decoding hhi_burst_long.bits. 
random issue(test 5 times, this issue only arise 1 time), the ssim is:
e.g.
filename  Y SSIM extreme Y SSIM average U SSIM extreme U SSIM average V SSIM extreme V SSIM
hhi_burst_long.bits 0.239132 0.368341 0.720362 0.813650 0.785594 0.86527

1. Testing Env:
========================================================================
Libva:                  (staging)35e70cb9b9c77dfb99fb370e319ed501f0c31b17
Libva_intel_driver:     (staging)fbbe401aa28a0b3859d587ef08f0df15a2f7c8f2
Gstreamer10:            (1.0)4e880d4d1e151ea64f83c28b5c3e1bbc06c57903
Gst_plugins_base10:     (1.0)2dd3f028c1e6dea799d7496639f53220818b20b1
Gst_plugins_good10:     (1.0)643d425f51f81b56deec16c01162637546708ee5
Gst_plugins_bad10:      (1.0)0587ab41b4f9979e9cfc11011ed5c970569ee3d3
Gst_plugins_ugly10:     (1.0)c7c911b8320576429e4a4234a1e29ec7436e6814
Gst_plugins_vaapi10:    (master)f0d3d9cd3c2fa852e71198184336b31259762a25
Gstreamer010:           (0.10)76fc67b18c38e7f6c9cfacc4e4d0ed11d3b2c548
Gst_plugins_base010:    (0.10)1e1e6eaf3f0dd11f6618154d9739cbe3e007d206
Gst_plugins_good010:    (0.10)5af6f5bfb6c3619a9ccc3b1681579aeb90e8b89a
Gst_plugins_bad010:     (0.10)cef47d85294a0dca38631f938b81a3f0dd6891bd
Gst_plugins_ugly010:    (0.10)5ddd97ff27ffeb03298be3a02ed18e8c2674d365
Gst_plugins_vaapi010:   (0.4)90713fdc442f27b4ea449b92660a294f7796f83e

2. Testing Steps:
========================================================================
    1.run command "gst-launch-1.0 filesrc location=/root/media_tools/decoder/bitstreams/hhi_burst_long.bits '!' mpegvideoparse '!' vaapidecode '!' vaapisink sync=false"
	2.run command "/root/media_tools/decoder/video/decoder/mpeg2decode -b hhi_burst_long.bits -f -r -o0 hhi_burst_long.bits%d"
	3.judge the YUV file that create by above command to get ssim value.
	
3. Debug Information:
it's intel driver's issue, git bisect information is:
fbbe401aa28a0b3859d587ef08f0df15a2f7c8f2 is the first bad commit
commit fbbe401aa28a0b3859d587ef08f0df15a2f7c8f2
Author: Sreerenj Balachandran <sreerenj.balachandran@intel.com>
Date:   Wed May 28 15:02:41 2014 -0600

    Fix the segfault while encoding multiple slice per frame.
    Zero initialize the packed raw data index array and
    packed slice header index array during each preallocation.
    Signed-off-by: Sreerenj Balachandran <sreerenj.balachandran@intel.com>
    Reviewed-by: Zhao, Yakui <yakui.zhao@intel.com>

3. Frequency of Occurence:
========================================================================
20%
Comment 1 zhixinx.liu 2014-06-06 07:11:27 UTC
after reboot test machine, cannot reproduce this problem anymore.
this problem found on the nightly test. before running this case, the test machine already ran A large number of tests case. so maybe this fail depend on other problem.
change Importance from high to medium as it's very difficult to reproduce.
Comment 2 haihao 2014-06-20 01:55:44 UTC
According to comment 1, closed it as invalid. Feel free to reopen it if you can reproduce it again.
Comment 3 zhixinx.liu 2014-06-24 08:18:17 UTC
use command:
mplayer -nosound -fps 30 -vo vaapi -va vaapi hhi_burst_long.bits
to reproduce this problem. sometimes(test 20 times, only arise 1 times) mplayer will display following message.

[root@x-hswmedia tmp]# mplayer -nosound -fps 30 -vo vaapi -va vaapi /root/media_tools/decoder/bitstreams/hhi_burst_long.bits
MPlayer SVN-r36265-4.8.1 (C) 2000-2013 MPlayer Team

Playing /root/media_tools/decoder/bitstreams/hhi_burst_long.bits.
libavformat version 55.7.100 (internal)
libavformat file format detected.
[lavf] stream 0: video (mpeg2video), -vid 0
VIDEO:  [MPG2]  720x576  0bpp  25.000 fps    0.0 kbps ( 0.0 kbyte/s)
Load subtitles in /root/media_tools/decoder/bitstreams/
libva info: LIBVA_TRACE is on, save log into /root/trace_test/tracelog.13149.7fc03c507940
libva info: VA-API version 0.35.2
libva info: va_getDriverName() returns 0
libva info: Trying to open /opt/X11R7/lib/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_0_35
libva info: va_openDriver() returns 0
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 55.9.100 (internal)
Selected video codec: [ffmpeg2] vfm: ffmpeg (FFmpeg MPEG-2)
==========================================================================
Audio: no sound
FPS forced to be 30.000  (ftime: 0.033).
Starting playback...
[VD_FFMPEG] Trying pixfmt=0.
[VD_FFMPEG] XVMC-accelerated MPEG-2.
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [vaapi] 720x576 => 1024x576 MPEG-2 VA-API Acceleration
[vo_vaapi] Using 1:1 VA surface mapping
[VD_FFMPEG] XVMC-accelerated MPEG-2.
mplayer: libvo/vo_vaapi.c:2516: get_surface: Assertion `mpi->number < va_num_surfaces' failed.



MPlayer interrupted by signal 6 in module: decode_video
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.
Comment 4 zhixinx.liu 2014-07-10 01:35:33 UTC
it's mplayer-vaapi's issue. not our bug. so close it, only test the two cases with gstreamer.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.