[Bug 77094] PRIME/Hybrid graphics render offload issues with gen7

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Mon Apr 7 00:42:55 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=77094

Nathan Schulte <nmschulte at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |---
            Summary|uvd                         |PRIME/Hybrid graphics
                   |                            |render offload issues with
                   |                            |gen7

--- Comment #3 from Nathan Schulte <nmschulte at gmail.com> ---
I'm experiencing issues with Offload Sink/Source with an Intel HD 4600 (Core i7
4910MQ) and AMD Radeon HD 8970M.  The machine is a laptop, a Clevo P150SM based
machine (Sager NP8265), which has the screen connected via eDP to the
integrated Intel chip, and the discrete has no connected heads.  I'm running
Debian Sid, and experience the issue with the 13.13 and 13.14-rc7 kernels, with
Debian's Xorg, DDX, DRM, and Mesa: --

$ Xorg -version
X.Org X Server 1.15.0.901 (1.15.1 RC 1)
Release Date: 2014-03-21
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.12-1-amd64 x86_64 Debian
Current Operating System: Linux nms-debian 3.14-rc7-amd64 #1 SMP Debian
3.14~rc7-1~exp1 (2014-03-17) x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.14-rc7-amd64
root=UUID=74330f52-bac4-487d-9874-aa51e41d6b34 ro quiet
Build Date: 31 March 2014  10:25:32AM
xorg-server 2:1.15.0.901-1 (http://www.debian.org/support) 
Current version of pixman: 0.32.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.

$ glxinfo | grep 'version\|renderer '
server glx version string: 1.4
client glx version string: 1.4
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
GLX version: 1.4
    GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer, 
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile 
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.0
OpenGL core profile shading language version string: 3.30
OpenGL version string: 3.0 Mesa 10.1.0
OpenGL shading language version string: 1.30

I've also experienced the issue when building DRM/DRI, Mesa3D (classic
i915/i965 and Gallium w/ LLVM for radeonsi; no Gallium3D for Intel, only for
Radeon) and the DDXs (xf86-video-intel and xf86-video-ati) from mainline; same
issues it seems.

I received an error state dump at one point, which I have attached here.  Quite
honestly, I'm not certain if the dump is actually related to this issue, as
I've had issues with Xorg loading the system wide DRI regardless of how much I
tried to force it otherwise.  (Before giving up, I last simply copied the
drivers to both locations, but I was still receiving segfaults from many
applications: perhaps there is simply an issue with that particular build of
mainline, and it was nothing to do with different driver versions loading).

These are the commands I was running to test: --

$ cat go.sh 
#!/usr/bin/env bash

export LIBGL_DEBUG=verbose

echo "$(date +%H:%M:%S.%N) ---- setting up offload sink" >> /var/log/kern.log
xrandr --setprovideroffloadsink 0x45 0x6f

echo "$(date +%H:%M:%S.%N) ---- executing glxinfo" >> /var/log/kern.log
DRI_PRIME=1 glxinfo > glxinfo.out

After running these commands, X seems to crash, and I'm presented with my
greeter/face chooser again.  I seem to be able to repeat this as many times as
I like, though I believe I saw X initializing the cards in a different order
sometimes when doing so.

As well, I believe output delegation is working fine: when I setup output sink
for the discrete card, I was presented with a black screen with "INIT 2.88" (or
something similar) printed at the top left as though the screen was configured
with a console, but no text was printed after the initial framebuffer
initialization or something.  The machine seemed to respond as though nothing
bad had happened, and I was able to turn off the machine by typing switching to
vtty1 and typing the right things.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20140407/ecddf6d4/attachment.html>


More information about the intel-gfx-bugs mailing list