<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC"
href="https://bugs.freedesktop.org/show_bug.cgi?id=82619">82619</a>
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>[regression] recent ABI changes in xorg-video-intel (intel_drv.so) breaks dual-head XBMC
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Reporter</th>
<td>martin.x.andersen@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>XOrg CVS
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr></table>
<p>
<div>
<pre>[This bug has been confirmed with the XBMC devs, and works on non-Intel
hardware. It appears to have been introduced some time after the 2.21.9 version
of the Intel Xorg driver. Versions after this are locked to using XBMC on 0,0
coordinates (left output) and the functionality is thus severly impaired.]
The scenario: running a dual-head setup with XBMC on the second display causes
it to output on the main screen regardless of which graphics port it is set to
output to.
I've done extensive testing on four different systems to try to get to the
bottom of which component introduced this. I have ruled out Window-managers,
libva, mesa and libdrm. That leaves the Xorg intel driver (intel_drv.so) from
xserver-xorg-video-intel / xf86-video-intel or the X server itself.
However, since I witnessed the same issue after compiling recent versions of
libdrm2, libva and xserver-xorg-video-intel without upgrading the X server,
Xorg itself does not seem to be at fault.
Current test system #1 (Haswell, i7-4765T):
- xorg-server 1.15.2-1
- lib32-libdrm 2.4.56-1
- libdrm 2.4.56-1
- xf86-video-intel 2.99.912-2
- lib32-mesa 10.2.4-1
- lib32-mesa-demos 8.2.0-1
- mesa 10.2.4-1
- mesa-demos 8.2.0-1
vainfo from the same system:
vainfo: VA-API version: 0.35 (libva 1.3.1)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Desktop - 1.3.2
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Simple : VAEntrypointEncSlice
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLD
I've also tested this on Ivy Bridge, Haswell and on Sandy Bridge systems using
various combinations of HDMI, VGA, DVI & DisplayPort outputs. They all behave
the same, regardless of distro (Ubuntu/ArchLinux) and kernel versions.
The 'last known good' config is as follows: (this is from a Ubuntu 13.04 system
running a 3.16.0 kernel)
- i965-va-driver_1.2.1-1
- libdrm2_2.4.46
- libva1_1.2.1-1
- xserver-xorg-core_1.13.3
- xserver-xorg-video-intel_2.21.9
I would be more than happy to provide any extra input, or test patches for this
issue. It should however be easily reproducible on any multi-headed system
using the built-in/on-CPU graphics.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>