Bug 1084677 - Xv video corruption on Intel Haswell GPU
Summary: Xv video corruption on Intel Haswell GPU
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-05 10:59 UTC by Pasi Karkkainen
Modified: 2014-09-08 09:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-08 09:07:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pasi Karkkainen 2014-04-05 10:59:11 UTC
Description of problem:

Playing videos using either mplayer or vlc using Xv output results in totally corrupted (unwatchable) videos. There are multiple "planes" of corrupted video moving on the video window, from different moments of time, and sometimes all video output also just stops, even though the player is still playing the video. 

Using unaccelerated x11 output, or OpenGL output, works fine, the problem seems to be only with Xv output. This is on a Lenovo T440s laptop with Intel Haswell CPU/GPU.

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)

$ cat /proc/cpuinfo | grep Intel
vendor_id	: GenuineIntel
model name	: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
vendor_id	: GenuineIntel
model name	: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
vendor_id	: GenuineIntel
model name	: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz
vendor_id	: GenuineIntel
model name	: Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz


Version-Release number of selected component (if applicable):
xorg-x11-drv-intel-2.21.15-5.fc20.x86_64, Linux kernel 3.13.7-200.fc20.x86_64.

How reproducible:
Always.

Steps to Reproduce:
1. Try playing a video with mplayer or vlc using (default) Xv video output plugin: "mplayer video.mp4".

Actual results:
Video playback is all corrupted and unwatchable.

Expected results:
Video playback works OK, like it works with x11 or OpenGL output plugins.

Additional info:

$ rpm -qa | grep mplayer
mplayer-1.1-21.20140327svn.fc20.x86_64
mplayer-common-1.1-21.20140327svn.fc20.x86_64

$ rpm -qa | grep vlc
vlc-core-2.1.4-1.fc20.x86_64
vlc-2.1.4-1.fc20.x86_64


Example output from mplayer with the default Xv output (no errors visible, just corrupted output):

libavformat version 55.19.104 (external)
libavformat file format detected.
[lavf] stream 0: video (h264), -vid 0
[lavf] stream 1: audio (aac), -aid 0, -alang und
VIDEO:  [H264]  720x576  24bpp  50.000 fps  2998.9 kbps (366.1 kbyte/s)
Clip info:
 major_brand: isom
 minor_version: 1
 compatible_brands: isomavc1
 creation_time: 2009-04-12 13:41:24
Load subtitles in ./
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1
==========================================================================
Opening video decoder: [ffmpeg] FFmpeg's libavcodec codec family
libavcodec version 55.39.101 (external)
Selected video codec: [ffh264] vfm: ffmpeg (FFmpeg H.264)
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 48000 Hz, 2 ch, floatle, 157.4 kbit/5.12% (ratio: 19671->384000)
Selected audio codec: [ffaac] afm: ffmpeg (FFmpeg AAC (MPEG-2/MPEG-4 Audio))
==========================================================================
AO: [pulse] 48000Hz 2ch floatle (4 bytes per sample)
Starting playback...
Movie-Aspect is 1.25:1 - prescaling to correct movie aspect.
VO: [xv] 720x576 => 720x576 Planar YV12 


If I do "mplayer -vo gl" or "mplayer -vo x11" the same video file works perfectly OK.

Comment 1 Pasi Karkkainen 2014-09-08 09:07:05 UTC
I just noticed with the latest F20 updates (as of September 2014) xv video seems to work OK now without corruption.

So this issue seems to have been resolved.


Note You need to log in before you can comment on or make changes to this bug.