Launchpad has imported 11 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=60052.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2013-01-30T03:26:35+00:00 Huax-lu wrote: System Environment: -------------------------- Arch: x86_64 Platform: Ivybridge Libdrm: (master)libdrm-2.4.41-4-g9dc0072e8d5a47fb0b2ada50fb897cb2c740bb40 Mesa: (master)9add4e803877f97ad7f6d479d81d537426f09b6f Xserver: (master)xorg-server-1.13.99.901-37-g7fe5e6dfa5c1e71d8b7540b28c1d508687a2fbee Xf86_video_intel:(master)2.20.19-38-g63c71bcd96202e6da44d6776d119a82f0c06d386 Cairo: (master)41ae904461e344fbfa3be3d276a7102bb4304b19 Libva: (staging)21649988d6b532cc96f633db017d1e4369f640e9 Libva_intel_driver:(staging)b7cb38772e6f73d3c1b3465e0bc6c0009c2f5634 Kernel: (drm-intel-nightly) 666476a090494e267f6c49197097c9740c1ed91c Bug detailed description: ------------------------- It fails on pineview,ironlake,sandybridge,ivybridge,haswell with mesa master branch. It also fails on 9.0 branch. Bisect shows:dbb2d192de33064ae6cdb799d71c5ac89a6ea8ff is the first bad commit. commit dbb2d192de33064ae6cdb799d71c5ac89a6ea8ff Author: Zack Rusin <za...@vmware.com> Date: Thu Jan 24 17:48:12 2013 -0800 glx: only advertise GLX_INTEL_swap_event if it's supported Only drivers supporting DRI2 version >=4 support GLX_INTEL_swap_event. So lets mark it as such otherwise applications which use this extension (i.e. everything based on Clutter, e.g. gnome-shell) break horribly on drivers supporting DRI2 versions only up to 3. Note: This is a candidate for the 9.0 branch. Reviewed-by: Brian Paul <bri...@vmware.com> output: GLX_INTEL_swap_event found in both client and server extension strings, but missing from unified string. PIGLIT: {'result': 'fail' } Reproduce steps: ---------------- 1. xinit 2. ./bin/glx-string-sanity Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/0 ------------------------------------------------------------------------ On 2013-01-30T06:07:27+00:00 Idr wrote: So, now the extension isn't advertised on drivers that do support it. :( That's no good. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/1 ------------------------------------------------------------------------ On 2013-01-30T06:11:14+00:00 Idr wrote: As far as I can tell by looking at dri_interface.h, __DRI_DRI2_VERSION only goes up to 3. There is no version 4. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/2 ------------------------------------------------------------------------ On 2013-01-30T07:02:25+00:00 Zackr wrote: (In reply to comment #2) > As far as I can tell by looking at dri_interface.h, __DRI_DRI2_VERSION only > goes up to 3. There is no version 4. Yea, you're right I was hoping the DRI2INFOREC_VERSION is propagated through it. It's the drivers supporting DRI2InfoRec::version >= 4 that implement it. We don't have access to either DRI2InfoRec::version or DRI2HasSwapControl both of which are used on server side, without them I actually don't know how Jesse, you and Kristian envisioned it to be tested for on this side. So the big question is: how did you want it to be tested for? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/3 ------------------------------------------------------------------------ On 2013-01-30T19:35:21+00:00 Idr wrote: (In reply to comment #3) > (In reply to comment #2) > > As far as I can tell by looking at dri_interface.h, __DRI_DRI2_VERSION only > > goes up to 3. There is no version 4. > > Yea, you're right I was hoping the DRI2INFOREC_VERSION is propagated through > it. It's the drivers supporting DRI2InfoRec::version >= 4 that implement > it. > We don't have access to either DRI2InfoRec::version or DRI2HasSwapControl > both of which are used on server side, without them I actually don't know > how Jesse, you and Kristian envisioned it to be tested for on this side. So > the big question is: how did you want it to be tested for? libGL only advertises the extension if both the client library and the server advertise it. If I'm reading this correctly, it sounds like the server is advertising the extension when it possibly shouldn't. If that's correct, we should revert this patch from Mesa and apply some sort of fix in the xserver. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/4 ------------------------------------------------------------------------ On 2013-01-30T21:13:13+00:00 Zackr wrote: (In reply to comment #4) > libGL only advertises the extension if both the client library and the > server advertise it. If I'm reading this correctly, it sounds like the > server is advertising the extension when it possibly shouldn't. If that's > correct, we should revert this patch from Mesa and apply some sort of fix in > the xserver. Yea, reporting of this extension is completely broken. Given all the moving pieces and that enabling it for drivers that don't support completely breaks desktop environments (the entire desktop just hangs because the swap event they're waiting for never gets there), I'd be really happy if we just disabled this extension completely at least for the stable 9.0.x series until this can be resolved. Jesse's initial patch to the server even had a fixme for properly reporting it. (http://cgit.freedesktop.org/xorg/xserver/commit/glx/glxdri2.c?id=84956ca43b087600d9db297cffd62e960c516d9e) then he removed it without actually fixing it http://cgit.freedesktop.org/xorg/xserver/commit/?id=165a4a9c7de0fcc6ef6a6421736b412ccb35965e , then someone realized that it breaks drivers so he manually disabled it for software rasterizers and then when Owen fixed reporting of this extension in Mesa everything broke. I'm ok with whatever that would make Fedora 18 not hang on startup and while this needs to be fixed in the Xserver I have no idea what are the Xserver release cycles nowadays and this is quite urgent. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/5 ------------------------------------------------------------------------ On 2013-01-31T17:32:37+00:00 Brianp-h wrote: Zack, as a temporary hack, could we just look if the driver == "vmwgfx" in the client side glx code and disable the extension there? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/6 ------------------------------------------------------------------------ On 2013-01-31T18:36:31+00:00 Zackr wrote: (In reply to comment #6) > Zack, as a temporary hack, could we just look if the driver == "vmwgfx" in > the client side glx code and disable the extension there? Yea, that's actually a pretty good idea. I'm not sure if any drivers are using the xorg state trackers which only supports dri2inforec version 3, or whether any other drivers also don't support version 4, but I'd be happy with having that hack in until we implement support for swap_event or/and the extension is fixed. Ian, are you ok with that? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/7 ------------------------------------------------------------------------ On 2013-02-19T20:52:06+00:00 Idr wrote: Fixed on master by the following commit. This commit has also been cherry picked to the 9.1 branch (as commit bdffccf) commit 076403c30d9f5cc79374e30d9f6007b08a63bf2d Author: Zack Rusin <za...@vmware.com> Date: Thu Feb 14 20:39:36 2013 -0800 DRI2: Don't disable GLX_INTEL_swap_event unconditionally GLX_INTEL_swap_event is broken on the server side, where it's currently unconditionally enabled. This completely breaks systems running on drivers which don't support that extension. There's no way to test for its presence on this side, so instead of disabling it uncondtionally, just disable it for drivers which are known to not support it. It makes sense because most drivers do support it right now. We'll be able to remove this once Xserver properly advertises GLX_INTEL_swap_event. Note: This is a candidate for stable branch branches. Signed-off-by: Zack Rusin <za...@vmware.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=60052 Reviewed-by: Jesse Barnes <jbar...@virtuousgeek.org> Reviewed-by: Brian Paul <bri...@vmware.com> Tested-by: Ian Romanick <ian.d.roman...@intel.com> Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/8 ------------------------------------------------------------------------ On 2013-02-21T01:52:06+00:00 Xunx-fang wrote: Verified it on mesa master and 9.1 branch. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/9 ------------------------------------------------------------------------ On 2013-02-21T15:39:29+00:00 Andreas-boll-dev wrote: Cherry-picked to the 9.0 branch: f84fe6aa2eac6984b77ca6da0c7e5a571b425827 It will be available in Mesa 9.0.3. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1136475/comments/10 ** Changed in: mesa Status: Unknown => Fix Released ** Changed in: mesa Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1136475 Title: clutter freezes due to unsupported GL extension in vmwgfx To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1136475/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
