Created attachment 828247 [details] lspci -v log Description of problem: Fedora 20, fresh installation, up to date. I wanted to try launching some 3D-application via discrete card. Earlier I did so (on Fedora 19): $ xrandr --setprovideroffloadsink <prov_xid> <sink_xid> $ DRI_PRIME=<prov_num> <app_name> The numbers <prov_xid> and <sink_xid> were decimals (from xrandr --listproviders output). But now I have the following xrandr output (on Fedora 20): $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x7b cap: 0x0 crtcs: 2 outputs: 4 associated providers: 0 name:Intel Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 0 name:radeon The numbers <prov_xid> and <sink_xid> are the hexadecimals now. xrandr --setprovideroffloadsink fails with them: $ xrandr --setprovideroffloadsink 0x55 0x7b X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 34 () Value in failed request: 0x7b Serial number of failed request: 16 Current serial number in output stream: 17 _______________________ Version-Release number of selected component (if applicable): xorg-x11-server-utils-7.7-2.fc20.x86_64 kernel-3.11.8-300.fc20.x86_64 xorg-x11-drv-intel-2.21.15-4.fc20.x86_64 xorg-x11-drv-ati-7.2.0-3.20131101git3b38701.fc20.x86_64 mesa-dri-drivers-9.2.3-1.20131114.fc20.x86_64 kde-4.11.3-3.fc20.x86_64 _______________________ How reproducible: always _______________________ Steps to Reproduce: 1. $ xrandr --listproviders Providers: number : 2 Provider 0: id: 0x7b cap: 0x0 crtcs: 2 outputs: 4 associated providers: 0 name:Intel Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 0 name:radeon 2. $ xrandr --setprovideroffloadsink 0x55 0x7b X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 139 (RANDR) Minor opcode of failed request: 34 () Value in failed request: 0x7b Serial number of failed request: 16 Current serial number in output stream: 17 _______________________ Actual results: xrandr --setprovideroffloadsink <prov_xid> <sink_xid> fails. _______________________ Expected results: xrandr --setprovideroffloadsink <prov_xid> <sink_xid> works fine. _______________________ Additional info: Lenovo Y470p GPU 1: Intel HD3000 GPU 2: AMD Radeon HD 7690M
Created attachment 828248 [details] lsmod log
Created attachment 828249 [details] X.org log
Created attachment 828250 [details] dmesg log
Seems that bug in intel drivers
I've downgraded xorg-x11-drv-intel package to 2.21.14-1.fc20.x86_64 (I saved this build earlier) and now xrandr --setprovideroffloadsink 0x55 0x7b works fine. This bug is a regression at the xf86-video-intel-2.21.15 driver.
I've locally built xorg-x11-drv-intel-2.21.15-4 without both xwayland patches. Now xrandr --setprovideroffloadsink 0x55 0x7b works fine! $ xrandr --listproviders Providers: number : 3 Provider 0: id: 0x7b cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 2 outputs: 4 associated providers: 2 name:Intel Provider 1: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon Provider 2: id: 0x55 cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 6 outputs: 0 associated providers: 2 name:radeon $ xrandr --setprovideroffloadsink 0x55 0x7b There is no error output. That's DRI_PRIME=1 glxinfo output: $ DRI_PRIME=1 glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS OpenGL core profile version string: 3.1 (Core Profile) Mesa 9.2.3 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 9.2.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: This bug is located at the xwayland patches.
btw you shouldn't need to do any xrandr commands on Fedora, the server automatically links up new slaves.
oh I see the discussion now, yeah looks like naught wayland patches.
xorg-x11-drv-intel-2.21.15-5.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/xorg-x11-drv-intel-2.21.15-5.fc20
(In reply to Dave Airlie from comment #8) > oh I see the discussion now, yeah looks like naught wayland patches. Yes! xorg-x11-drv-intel-2.21.15-5.fc20 fixes this bug. Thanks a lot! (In reply to Igor Gnatenko from comment #4) > Seems that bug in intel drivers Thank you too! Well done!
Package xorg-x11-drv-intel-2.21.15-5.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xorg-x11-drv-intel-2.21.15-5.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-22110/xorg-x11-drv-intel-2.21.15-5.fc20 then log in and leave karma (feedback).
xorg-x11-drv-intel-2.21.15-5.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
Hi, this upgrade breaks the login to gnome on Fedora 20. Related bugs are: #1045464 #1056299 #1036377
The upgrade also breaks the login to Gnome on Fedora 20 on my machine (HP Pavilion DV6). So I cannot use the discrete graohics card because of the bug in xorg-x11-drv-intel-2-21-15-4, which I have to continue to use because of, for me, the serious problem with xorg-x11-drv-intel-2-21-15-5.