[Mesa-dev] [Bug 90927] GLSL extensions are not routed from X-Server to client app
https://bugs.freedesktop.org/show_bug.cgi?id=90927 Ian Romanick changed: What|Removed |Added Severity|critical|enhancement --- Comment #1 from Ian Romanick --- Extensions need to have GLX protocol supported on the client and on the server. For some extensions this just means they need to be added to the known_gl_extensions in src/glx/glxextensions.c in Mesa. However, all of the GLSL related extensions need protocol implemented (e.g., glShaderSource). It's mostly just a lot of typing and testing. Patches welcome. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90905] mesa: Finish subdir-objects transition
https://bugs.freedesktop.org/show_bug.cgi?id=90905 --- Comment #3 from Emil Velikov --- Yes the situation is a "bit" messy, and considering the interesting use of xmlconfig by the loader (and effectively libGL) I intentionally stayed away from it. Anywho, I've picked Erik's approach, updated+tested the other two build systems and will send the patch to the ML in a second. Meanwhile Eric pushed some patches that make autotools complain about another subdir-objects issue. Will send a patch for that one as well. -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 Furkan changed: What|Removed |Added CC||bri...@vmware.com Component|Drivers/Gallium/radeonsi|Mesa core Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org|org QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop. |.org|org --- Comment #19 from Furkan --- I booted up a Haswell box from an Ubuntu 15.04 live USB, and was able to reproduce the same glitch. It looks like we can reproduce this on radeon, nouveau, and i965, but not llvmpipe. What does that mean? I am re-classifying this under Mesa core for now. Would it fit better under any other category? Can anybody confirm that this issue isn't present with the Nvidia proprietary driver? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #20 from Furkan --- I booted up a Haswell (i7-4770) machine from an Ubuntu 15.04 live USB, and was able to reproduce the same glitch. It looks like we can reproduce this on radeon, nouveau, and i965, but not llvmpipe. What does that mean? I re-classified this under Mesa core for now. Can anybody confirm that this issue isn't present with the Nvidia proprietary driver? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 28130] vbo: premature flushing breaks GL_LINE_LOOP
https://bugs.freedesktop.org/show_bug.cgi?id=28130 --- Comment #8 from marius predut --- My investigation till now : Because the test code call twice the glBegin(GL_LINE_LOOP);glVertex3fv(); glEnd() and then glFlush() if we add an intermediary glFlush() between those sequential call then the bug is fixed. Seems a trouble with last status of glBegin(GL_LINE_LOOP) after the same call, in case not flushing was done. -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 28130] vbo: premature flushing breaks GL_LINE_LOOP
https://bugs.freedesktop.org/show_bug.cgi?id=28130 --- Comment #9 from Roland Scheidegger --- (In reply to marius predut from comment #8) > My investigation till now : > Because the test code call twice the > glBegin(GL_LINE_LOOP);glVertex3fv(); glEnd() and then glFlush() > if we add an intermediary glFlush() between those sequential call then the > bug > is fixed. > Seems a trouble with last status of glBegin(GL_LINE_LOOP) after the same > call, in case not flushing was done. Pretty sure this is more or less coincidence, since in this example a single loop fits into the max size of some buffer before it will be flushed internally. Make it bigger and it will still fail. (Also see https://bugs.freedesktop.org/show_bug.cgi?id=81174 for a related bug and some mroe explanation). -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90905] mesa: Finish subdir-objects transition
https://bugs.freedesktop.org/show_bug.cgi?id=90905 Julien Isorce changed: What|Removed |Added CC||julien.iso...@gmail.com --- Comment #4 from Julien Isorce --- *** Bug 90310 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90310] Fails to build gallium_dri.so at linking stage with clang because of multiple redefinitions
https://bugs.freedesktop.org/show_bug.cgi?id=90310 Julien Isorce changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Julien Isorce --- *** This bug has been marked as a duplicate of bug 90905 *** -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90905] mesa: Finish subdir-objects transition
https://bugs.freedesktop.org/show_bug.cgi?id=90905 --- Comment #5 from Julien Isorce --- attachment 116377 works for me on osx with --enable-dri --disable-vdpau --disable-va --enable-asm --with-gallium-drivers=swrast --enable-gles2 --enable-gles1 --enable-glx --enable-opengl --enable-gallium-osmesa --with-egl-platforms=x11 --enable-debug --enable-gallium-llvm --disable-omx --disable-llvm-shared-libs -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 69101] prime: black window
https://bugs.freedesktop.org/show_bug.cgi?id=69101 --- Comment #27 from viktor --- Hi guys! Fedora 22 x86_64, kernel 4.0.4-303, KDE Frameworks 5.10.0, KWin 5.3.1-2, OpenGL 3.1 backend for KWin compositor, xorg-x11-drv-ati-7.5.0-3 and xorg-x11-drv-intel-2.99.917-10.20150526 vga drivers, XOrg-xserver 1.17.1-14, the second monitor is connected to the D-SUB output of my laptop (Lenovo G570) lspci gives: 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) Subsystem: Lenovo Device 397a Kernel driver in use: i915 Kernel modules: i915 -- 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Robson CE [Radeon HD 6370M/7370M] (rev ff) Kernel driver in use: radeon Kernel modules: radeon I've already done xrandr --setprovideroffloadsink radeon Intel The problem still remains: when I run glxgears (or another OpenGL app) without DRI_PRIME=1 all seems good but with that variable I get black screen. The problem disappears when I switch to another window and back. With XRender backend for KWin all works like a charm but I don't want to use XRender because of high CPU load and overheating. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 65525] [llvmpipe] lp_scene.h:210:lp_scene_alloc: Assertion `size <= (64 * 1024)' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=65525 --- Comment #2 from Vinson Lee --- mesa: 4d35eef326e49cc8da50879d30a1c5088d4775e1 (master 10.7.0-devel) This regression is still present on llvmpipe. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 71199] [llvmpipe] piglit gl-1.4-polygon-offset regression
https://bugs.freedesktop.org/show_bug.cgi?id=71199 --- Comment #9 from Vinson Lee --- mesa: 4d35eef326e49cc8da50879d30a1c5088d4775e1 (master 10.7.0-devel) This regression is still present on llvmpipe. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 69101] prime: black window
https://bugs.freedesktop.org/show_bug.cgi?id=69101 viktor changed: What|Removed |Added CC||linux...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 69101] prime: black window
https://bugs.freedesktop.org/show_bug.cgi?id=69101 --- Comment #28 from Tobias Klausmann --- (In reply to viktor from comment #27) > Hi guys! snip > > I've already done xrandr --setprovideroffloadsink radeon Intel > > The problem still remains: when I run glxgears (or another OpenGL app) > without DRI_PRIME=1 all seems good but with that variable I get black > screen. The problem disappears when I switch to another window and back. > With XRender backend for KWin all works like a charm but I don't want to use > XRender because of high CPU load and overheating. Its a known issue and i guess it wont get resolved (with DRI2), with DRI3 this does not happen, you don't depend on compositing as well with it. (And you are saved from the xrandr --setprovideroffloadsink dance as well!) -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 69101] prime: black window
https://bugs.freedesktop.org/show_bug.cgi?id=69101 --- Comment #29 from viktor --- As I know current mesa drivers for intel IGP doesn't support DRI3 by default for Fedora 22... but I can be wrong. Any ways to enable DRI3? -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89819] WebGL Conformance swrast failure in conformance/uniforms/uniform-default-values.html
https://bugs.freedesktop.org/show_bug.cgi?id=89819 --- Comment #6 from Luke --- Roland, Did I miss the commit or is your fix still in the process of being reviewed? I'd be glad to help test out your patch. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89819] WebGL Conformance swrast failure in conformance/uniforms/uniform-default-values.html
https://bugs.freedesktop.org/show_bug.cgi?id=89819 --- Comment #7 from Roland Scheidegger --- (In reply to Luke from comment #6) > Roland, > Did I miss the commit or is your fix still in the process of being reviewed? > I'd be glad to help test out your patch. The crash fix was 6e5970ffee0129fb94d8b7f0ebd4fac3992e7dce. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 42688] attribute can't be used when it used fixed function vertex
https://bugs.freedesktop.org/show_bug.cgi?id=42688 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 56836] xdemo/texture_from_pixmap failed to create drawable on swrast
https://bugs.freedesktop.org/show_bug.cgi?id=56836 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 62202] Mesa demo dest window of wincopy flickers while toggle f/b buffer on software render
https://bugs.freedesktop.org/show_bug.cgi?id=62202 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90797] [ALL bisected] Mesa change cause performance case manhattan fail.
https://bugs.freedesktop.org/show_bug.cgi?id=90797 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 54805] gl_ClipVertex support horribly broken with software TNL
https://bugs.freedesktop.org/show_bug.cgi?id=54805 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 79629] [Dri3 bisected] piglit glx_GLX_ARB_create_context_current_with_no_framebuffer fail
https://bugs.freedesktop.org/show_bug.cgi?id=79629 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 13978] [Mesa core] glGetIntegerv(GL_DRAW_BUFFER0) returns wrong buffer enum
https://bugs.freedesktop.org/show_bug.cgi?id=13978 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 29418] ARB_vp: large offsets when using relative addressing
https://bugs.freedesktop.org/show_bug.cgi?id=29418 Shuang He changed: What|Removed |Added CC||christophe.prig...@intel.co ||m -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 65525] [llvmpipe] lp_scene.h:210:lp_scene_alloc: Assertion `size <= (64 * 1024)' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=65525 José Fonseca changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|mesa-dev@lists.freedesktop. |jfons...@vmware.com |org | --- Comment #3 from José Fonseca --- Tentative fix out for review on http://lists.freedesktop.org/archives/mesa-dev/2015-June/086497.html -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 71199] [llvmpipe] piglit gl-1.4-polygon-offset regression
https://bugs.freedesktop.org/show_bug.cgi?id=71199
--- Comment #10 from José Fonseca ---
On me Mesa DRI Intel(R) Haswell Mobile I actually get the reverse problem:
$ ./bin/gl-1.4-polygon-offset -auto
Actual MRD is too large (may waste depth-buffer range)
Ideal MRD at near plane is 5.960283e-08 (nominally 1 bit)
Actual MRD at near plane is 1.192093e-07 (nominally 2 bits)
Ideal MRD at infinity is 4.353401e-08 (nominally 1 bit)
Actual MRD at infinity is 1.192093e-07 (nominally 2 bits)
PIGLIT: {"result": "fail" }
So the test itself doesn't seem to be limited to 1 bit as I considered.
Still no idea on how to fix it. I'm reluctant just to bump MRD on llvmpipe, as
I'm afraid it will cause problems with different state trackers.
It's not a huge deal neither.
In short, I'm afraid there's little chance for a fix any time soon..
--
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89819] WebGL Conformance swrast failure in conformance/uniforms/uniform-default-values.html
https://bugs.freedesktop.org/show_bug.cgi?id=89819 Luke changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Luke --- Verified fixed by 6e5970ffee0129fb94d8b7f0ebd4fac3992e7dce in both Firefox and Chrome. Great detective work Roland. Thanks! -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89818] WebGL Conformance conformance/textures/texture-size-limit.html -> OUT_OF_MEMORY
https://bugs.freedesktop.org/show_bug.cgi?id=89818 Luke changed: What|Removed |Added CC||srol...@vmware.com --- Comment #1 from Luke --- The test passes by forcing softpipe with: $ export LIBGL_ALWAYS_SOFTWARE=1 $ export DRAW_USE_LLVM=0 $ export GALLIUM_DRIVER=softpipe So for swrast, this is llvmpipe specific. Adding Roland to the case. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89818] WebGL Conformance conformance/textures/texture-size-limit.html -> OUT_OF_MEMORY
https://bugs.freedesktop.org/show_bug.cgi?id=89818 --- Comment #2 from Roland Scheidegger --- It is not really llvmpipe specific, it is more or less luck this passes with softpipe, the actual logic refusing too large textures is very similar. But softpipe announces a limit of 4k for cube maps, whereas llvmpipe says 8k. It is true though that with the memory limit we impose (1GB) we can't actually even handle a 2 (with mips) or 4 channel (even without mips) (with just 8 bits per channel, uncompressed) cube map, but this isn't required unless I'm missing something, and it is quite ok to simply say out_of_memory (this could be queried via proxy textures). That the test only ever tries to submit the smallest mip levels doesn't matter, we allocate the whole thing in any case. I'm inclined to mark this as NOTABUG, the test looks bogus. If you'd try the same with, say, RGBA32F textures, you'd see this fail on softpipe as well. (We could, of course, increase the limit, but even twice that would not quite be enough for what the tests wants - not sure if all the math would be unsigned-safe to increase it further to the required "some bytes more than than 2GB due to padding" but in any case I don't think we really want to do that.) -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89818] WebGL Conformance conformance/textures/texture-size-limit.html -> OUT_OF_MEMORY
https://bugs.freedesktop.org/show_bug.cgi?id=89818 --- Comment #3 from Roland Scheidegger --- Forgot to mention, I tested this with firefox. I am no longer able to use chromium at all for this with the xlib based driver - there's some error about threads in use "InitializeSandbox() called with multiple threads in process gpu-process" and it just seems to hang, with LP_NUM_THREADS=0 it gets past that but somehow llvm doesn't like getting used within the sandbox (I assume): "static llvm::sys::Path llvm::sys::Path::GetCurrentDirectory(): Assertion `false && "Could not query current working directory."' failed". But in any case the result should be the same if you somehow manage to use llvmpipe with chromium. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 89818] WebGL Conformance conformance/textures/texture-size-limit.html -> OUT_OF_MEMORY
https://bugs.freedesktop.org/show_bug.cgi?id=89818 Luke changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #4 from Luke --- Roland, Yes, chromium's sandbox can be a hassle if it gets misconfigured. When I was running daily builds, I configured it (also can be disabled) with this: https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment I'm currently using Chrome, which installs with a working/preconfigured sandbox. It still gives the "InitializeSandbox() called with multiple threads in process gpu-process" warning but still works. llvmpipe is working with both webgl demos and the webgl conformance tests. Thanks for investigating this issue. I'll close it as NOTABUG. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91014] Piglit regression: spec/!OpenGL 1.2/texture-packed-formats
https://bugs.freedesktop.org/show_bug.cgi?id=91014 Bug ID: 91014 Summary: Piglit regression: spec/!OpenGL 1.2/texture-packed-formats Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: brian.wil...@intel.com QA Contact: mesa-dev@lists.freedesktop.org Piglit test: spec/!OpenGL 1.2/texture-packed-formats We are seeing this Piglit regression on pineview (chromebook, the only chrome platform in our stable still using X and tested with Piglit) The version of Mesa that ChromeOS is currently using passes this test in piglit. It is based on the following commit plus an additional 34 patches: 1291788 glsl: Generate unique names for each const array lowered to uniforms [Nov 2014-ish] It fails in the following Mesa commit: c2a0600 i965: Don't set NirOptions for stages that will use the vec4 backend [May 2015-ish] It also fails in this recent Mesa commit: 1a6e4f46ed117b393e26aff326e5b05d4aea7fb0 (gallium: remove explicit values from PIPE_CAP_ enums) [~June 10, 2015] -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91015] Piglit regression: spec/ARB_occlusion_query2/api
https://bugs.freedesktop.org/show_bug.cgi?id=91015 Bug ID: 91015 Summary: Piglit regression: spec/ARB_occlusion_query2/api Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: brian.wil...@intel.com QA Contact: mesa-dev@lists.freedesktop.org Piglit test: spec/ARB_occlusion_query2/api We are seeing this Piglit regression on pineview (chromebook, the only chrome platform in our stable still using X and tested with Piglit) The version of Mesa that ChromeOS is currently using passes this test in piglit. It is based on the following commit plus an additional 34 patches: 1291788 glsl: Generate unique names for each const array lowered to uniforms [Nov 2014-ish] It fails in the following Mesa commit: c2a0600 i965: Don't set NirOptions for stages that will use the vec4 backend [May 2015-ish] It also fails in this recent Mesa commit: 1a6e4f46ed117b393e26aff326e5b05d4aea7fb0 (gallium: remove explicit values from PIPE_CAP_ enums) [~June 10, 2015] -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91016] Piglit regression: shaders/glsl-floating-constant-120
https://bugs.freedesktop.org/show_bug.cgi?id=91016 Bug ID: 91016 Summary: Piglit regression: shaders/glsl-floating-constant-120 Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: brian.wil...@intel.com QA Contact: mesa-dev@lists.freedesktop.org Piglit test: shaders/glsl-floating-constant-120 We are seeing this Piglit regression on pineview (chromebook, the only chrome platform in our stable still using X and tested with Piglit) The version of Mesa that ChromeOS is currently using passes this test in piglit. It is based on the following commit plus an additional 34 patches: 1291788 glsl: Generate unique names for each const array lowered to uniforms [Nov 2014-ish] It fails in the following Mesa commit: c2a0600 i965: Don't set NirOptions for stages that will use the vec4 backend [May 2015-ish] It also fails in this recent Mesa commit: 1a6e4f46ed117b393e26aff326e5b05d4aea7fb0 (gallium: remove explicit values from PIPE_CAP_ enums) [~June 10, 2015] -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91015] Piglit regression: spec/ARB_occlusion_query2/api
https://bugs.freedesktop.org/show_bug.cgi?id=91015 Kenneth Graunke changed: What|Removed |Added Component|Mesa core |Drivers/Gallium/i915g Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91014] Piglit regression: spec/!OpenGL 1.2/texture-packed-formats
https://bugs.freedesktop.org/show_bug.cgi?id=91014 Kenneth Graunke changed: What|Removed |Added Component|Mesa core |Drivers/Gallium/i915g Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91016] Piglit regression: shaders/glsl-floating-constant-120
https://bugs.freedesktop.org/show_bug.cgi?id=91016 Kenneth Graunke changed: What|Removed |Added Component|Mesa core |Drivers/Gallium/i915g Assignee|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org QA Contact|mesa-dev@lists.freedesktop. |dri-devel@lists.freedesktop |org |.org -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91020] Mesa's demo / tools won't compile since EGL changes
https://bugs.freedesktop.org/show_bug.cgi?id=91020 Bug ID: 91020 Summary: Mesa's demo / tools won't compile since EGL changes Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Demos Assignee: mesa-dev@lists.freedesktop.org Reporter: m...@fireburn.co.uk QA Contact: mesa-dev@lists.freedesktop.org Created attachment 116577 --> https://bugs.freedesktop.org/attachment.cgi?id=116577&action=edit Build logs Compile fails with EGL_SCREEN_BIT_MESA -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91020] Mesa's demo / tools won't compile since EGL changes
https://bugs.freedesktop.org/show_bug.cgi?id=91020 --- Comment #1 from Emil Velikov --- Mesa commit 7a58262e58d removed all the EGL_MESA_screen_surface definitions as it was never implemented (according to it). Seems like mesa-demos doesn't have the necessary compile guards. Something like the following should fix things #if EGL_MESA_screen_surface // code using the extension #endif Feel free to wrap up a patch and send it to mesa-dev ML. Thanks Emil -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90903] egl_dri2.c:dri2_load fails to load libglapi on osx
https://bugs.freedesktop.org/show_bug.cgi?id=90903 --- Comment #1 from Julien Isorce --- Created attachment 116583 --> https://bugs.freedesktop.org/attachment.cgi?id=116583&action=edit es2gears_x11 and es2_info with llvmpipe on osx Running gears with egl/gles2/x11 with llvmpipe software driver on osx. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91020] Mesa's demo / tools won't compile since EGL changes
https://bugs.freedesktop.org/show_bug.cgi?id=91020 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk --- Comment #2 from Mike Lothian --- I'm afraid that's beyond me - I've tried compiling without the egl utilities and now get: -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91020] Mesa's demo / tools won't compile since EGL changes
https://bugs.freedesktop.org/show_bug.cgi?id=91020 Mike Lothian changed: What|Removed |Added Attachment #116585|Buid log without EGL|Build log without EGL description|| -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91020] Mesa's demo / tools won't compile since EGL changes
https://bugs.freedesktop.org/show_bug.cgi?id=91020 --- Comment #3 from Mike Lothian --- Created attachment 116585 --> https://bugs.freedesktop.org/attachment.cgi?id=116585&action=edit Buid log without EGL -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91034] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91034 Bug ID: 91034 Summary: New account request Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Other Assignee: mesa-dev@lists.freedesktop.org Reporter: sarah.a.sh...@linux.intel.com QA Contact: mesa-dev@lists.freedesktop.org Created attachment 116603 --> https://bugs.freedesktop.org/attachment.cgi?id=116603&action=edit Public GPG key I've recently joined the Intel OTC graphics team. Please create a shell account on freedesktop.org for me. Name: Sarah Sharp Email: sarah.a.sh...@linux.intel.com Preferred account name: sarah GPG key fingerprint = 6ECC 8026 CD5B 35AC C5A9 1BAE 1306 58C2 E2D4 6739 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91034] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91034 --- Comment #1 from Sarah Sharp --- Created attachment 116604 --> https://bugs.freedesktop.org/attachment.cgi?id=116604&action=edit Public ssh key -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91038] X segfault when watching youtube
https://bugs.freedesktop.org/show_bug.cgi?id=91038 Bug ID: 91038 Summary: X segfault when watching youtube Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Other Assignee: mesa-dev@lists.freedesktop.org Reporter: 19.jaime...@gmail.com QA Contact: mesa-dev@lists.freedesktop.org Created attachment 116620 --> https://bugs.freedesktop.org/attachment.cgi?id=116620&action=edit AIGLX segfault I was watching youtube on fullscreen and X restarted. I got a segfault. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91039] [d3d9] D3D9 state tracker crashes due to stack misalignment if Mesa is compiled with -mfpmath=sse
https://bugs.freedesktop.org/show_bug.cgi?id=91039 Bug ID: 91039 Summary: [d3d9] D3D9 state tracker crashes due to stack misalignment if Mesa is compiled with -mfpmath=sse Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: xamaniqi...@gmail.com QA Contact: mesa-dev@lists.freedesktop.org Description: The "Nine" D3D9 state tracker crashes when Wine loads any D3D program if Mesa is compiled with -mfpmath=sse. This is because the Linux ABI assumes a stack alignment to 16 bytes, whereas the Win32 ABI assumes a stack alignment to 4 bytes. This causes a stack misalignment and thus a general protection fault. Additional information: Also see the following external bug reports: https://bugs.winehq.org/show_bug.cgi?id=22475 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40838 Specifications: OS: Gentoo GNU/Linux x86_64 Kernel version: Linux 4.0.4-hardened-r3 Mesa version: 10.6.0 Solution: The crashes no longer occur when Mesa's stack is realigned to 4 bytes. Therefore, always pass -mstackrealign to CFLAGS if -mfpmath=sse is enabled; this should probably be handled in the configure script. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91039] [d3d9] D3D9 state tracker crashes due to stack misalignment if Mesa is compiled with -mfpmath=sse
https://bugs.freedesktop.org/show_bug.cgi?id=91039 Itzamna changed: What|Removed |Added CC||xamaniqi...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91039] [d3d9] D3D9 state tracker crashes due to stack misalignment if Mesa is compiled with -mfpmath=sse
https://bugs.freedesktop.org/show_bug.cgi?id=91039 --- Comment #1 from Itzamna --- (In reply to Itzamna from comment #0) > Solution: > The crashes no longer occur when Mesa's stack is realigned to 4 bytes. > Therefore, always pass -mstackrealign to CFLAGS if -mfpmath=sse is enabled; > this should probably be handled in the configure script. Erratum: -mstackrealign realigns the incoming (4 byte-aligned) stack to 16 bytes, see https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html . -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91038] X segfault when watching youtube
https://bugs.freedesktop.org/show_bug.cgi?id=91038 Chris Wilson changed: What|Removed |Added Component|Other |Driver/intel Assignee|mesa-dev@lists.freedesktop. |ch...@chris-wilson.co.uk |org | Product|Mesa|xorg QA Contact|mesa-dev@lists.freedesktop. |intel-gfx-bugs@lists.freede |org |sktop.org -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 78318] [swrast] piglit glsl-kwin-blur-1 regression
https://bugs.freedesktop.org/show_bug.cgi?id=78318 Vinson Lee changed: What|Removed |Added Version|git |10.2 --- Comment #5 from Vinson Lee --- mesa: 717376155d2082d7bf94122a1e1d383b39e0b070 (master 10.7.0-devel) piglit glsl-kwin-blur-1 regression is still present. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 79706] [TRACKER] Mesa regression tracker
https://bugs.freedesktop.org/show_bug.cgi?id=79706 Bug 79706 depends on bug 86980, which changed state. Bug 86980 Summary: [swrast] piglit fp-rfl regression https://bugs.freedesktop.org/show_bug.cgi?id=86980 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 86980] [swrast] piglit fp-rfl regression
https://bugs.freedesktop.org/show_bug.cgi?id=86980 Vinson Lee changed: What|Removed |Added Status|NEW |RESOLVED Version|git |10.5 Resolution|--- |FIXED --- Comment #8 from Vinson Lee --- commit 88305dfd0b79ad5980d293e86712496f134347b4 Author: Roland Scheidegger Date: Sat Feb 14 16:34:04 2015 +0100 mesa: don't enable NV_fragment_program_option with swrast Since dropping some NV_fragment_program opcodes (commits 868f95f1da74cf6dd7468cba1b56664aad585ccb, a3688d686f147f4252d19b298ae26d4ac72c2e08) we can no longer parse all opcodes necessary for this extension, leading to bugs (https://bugs.freedesktop.org/show_bug.cgi?id=86980). Hence don't announce support for it in swrast (no other driver enabled it). (Note that remnants of some NV_fp/vp extensions remain, they could be dropped but are required as hacks for getting viewperf11 catia to run.) -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 77288] [swrast] piglit glean glsl1 regression
https://bugs.freedesktop.org/show_bug.cgi?id=77288 Vinson Lee changed: What|Removed |Added Version|git |10.2 --- Comment #6 from Vinson Lee --- mesa: 717376155d2082d7bf94122a1e1d383b39e0b070 (master 10.7.0-devel) piglit glean glsl1 regression on swrast is still present. -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91044] piglit spec/egl_khr_create_context/valid debug flag gles* fail
https://bugs.freedesktop.org/show_bug.cgi?id=91044
Bug ID: 91044
Summary: piglit spec/egl_khr_create_context/valid debug flag
gles* fail
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: EGL
Assignee: mesa-dev@lists.freedesktop.org
Reporter: stu_...@126.com
QA Contact: mesa-dev@lists.freedesktop.org
When running piglit test on egl_x11 platform, I accidentally noticed that
piglit test spec/egl_khr_create_context/valid debug flag gles{1,2,3} fail. The
reason is that mesa EGL gives unexpected EGL_BAD_ATTRIBUTE. Digging into the
EGL code, I found libEGL will give EGL_BAD_ATTRIBUTE when setting
EGL_CONTEXT_FLAGS_KHR in non-OpenGL contexts (including OpenGL ES context),
with the quote in comment:
/* The EGL_KHR_create_context spec says:
*
* "Flags are only defined for OpenGL context creation, and
* specifying a flags value other than zero for other types of
* contexts, including OpenGL ES contexts, will generate an
* error."
*/
However, I can't find the words quoted in the present EGL_KHR_create_context
spec. On the other hand, it allows creating debug context in OpenGL ES (i.e.
setting EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR in EGL_CONTEXT_FLAGS_KHR).
Should we just remove the non-OpenGL check or just allow
EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR in OpenGL ES context?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91044] piglit spec/egl_khr_create_context/valid debug flag gles* fail
https://bugs.freedesktop.org/show_bug.cgi?id=91044 --- Comment #1 from Emil Velikov --- Based of the patch date (17 July 2012) and the extension revision history I'd say that things were changed/nuked in Version 12 or later. With Version 15 being the prime suspect. As Intel is a Khronos member, you should have access to the SVN repo/history for the exact details. I'd assume that it would be the better option. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91044] piglit spec/egl_khr_create_context/valid debug flag gles* fail
https://bugs.freedesktop.org/show_bug.cgi?id=91044 --- Comment #2 from Boyan Ding --- (In reply to Emil Velikov from comment #1) > As Intel is a Khronos member, you should have access to the SVN repo/history > for the exact details. I'd assume that it would be the better option. Sorry if I caused confusion, but I'm not affiliated with Intel (or any other Khronos member). So I seem not able to access the spec history. I tried simply removing the non-OpenGL check, but it breaks another piglit test, namely spec/egl_khr_create_context/invalid flag gles, giving EGL_BAD_MATCH instead of EGL_BAD_ATTRIBUTE in some cases (I guess when the flag given is valid for OpenGL but not ES). And I saw that test was updated against version 15 of EGL_KHR_create_context_spec (commit 5f668b1 [1]). The comment there is explains /* According to the EGL_KHR_create_context spec, version 15, there * exists exactly one valid flag for OpenGL ES contexts: the debug * flag. * If the EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR flag bit is set in * EGL_CONTEXT_FLAGS_KHR, then a will be created. * [...] This bit is supported for OpenGL and OpenGL ES contexts. */ So it seems allowing EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR in OpenGL ES is more reasonable. If so, I'll work out a patch and send it to the ML. [1] http://cgit.freedesktop.org/piglit/commit/?id=5f668b118fed374a16d21ea1c0b2e82c0b658cc5 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91044] piglit spec/egl_khr_create_context/valid debug flag gles* fail
https://bugs.freedesktop.org/show_bug.cgi?id=91044 --- Comment #3 from Boyan Ding --- Found the exact reason why EGL_BAD_MATCH instead of EGL_BAD_ATTRIBUTE is given for unknown flags in OpenGL ES context. src/mesa/drivers/dri/common/dri_util.c gives __DRI_CTX_ERROR_BAD_FLAG when hitting unknown flag in OpenGL ES but gives __DRI_CTX_ERROR_UNKNOWN_FLAG in OpenGL instead. Looking into the history, some old comment seems to suggest that the error value has something to do with GLX_EXT_create_context_es2_profile. I don't know exactly what error should be given in that case. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91034] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91034 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Daniel Stone --- ah yes, graphics gets us all eventually - welcome! -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91044] piglit spec/egl_khr_create_context/valid debug flag gles* fail
https://bugs.freedesktop.org/show_bug.cgi?id=91044 --- Comment #4 from Emil Velikov --- Got confused there thinking that you're with Intel, sorry about that Boyan. As expected we're missing the v15 update of the spec in our libEGL. I will try to find some time and dig through the spec history late this week. This way we'll clearly see if there are other missing pieces ;-) And yes, allowing EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR for GLES seems like the correct thing to do here (as per the spec quote below) If the EGL_CONTEXT_OPENGL_DEBUG_BIT_KHR flag bit is set in EGL_CONTEXT_FLAGS_KHR, then a will be created... ... This bit is supported for OpenGL and OpenGL ES contexts. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90797] [ALL bisected] Mesa change cause performance case manhattan fail.
https://bugs.freedesktop.org/show_bug.cgi?id=90797 Tapani Pälli changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Assignee|mesa-dev@lists.freedesktop. |lem...@gmail.com |org | --- Comment #10 from Tapani Pälli --- Fixed in master: commit 7d88ab42b9dda825feddbae774a2a48ddf3cbec2 Author: Tapani Pälli Date: Tue Jun 16 13:46:47 2015 +0300 mesa: set override_version per api version override Before 9b5e92f get_gl_override was called only once, but now it is called for multiple APIs (GLES2, GL), version needs to be set always. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91077] dri2_glx.c:1186: undefined reference to `loader_open_device'
https://bugs.freedesktop.org/show_bug.cgi?id=91077 Bug ID: 91077 Summary: dri2_glx.c:1186: undefined reference to `loader_open_device' Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: bisected, regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: v...@freedesktop.org QA Contact: mesa-dev@lists.freedesktop.org CC: der...@osg.samsung.com, emil.l.veli...@gmail.com, k...@bitplanet.net mesa: 3fa9bb81ec8b21f472de32e08d0caf917239da08 (master 10.7.0-devel) 324ee9b391ea2db4b74709d30a131e79055bf071 is the first bad commit commit 324ee9b391ea2db4b74709d30a131e79055bf071 Author: Derek Foreman Date: Wed Jun 17 11:28:50 2015 -0500 glx: Use loader_open_device() helper We've moved the open with CLOEXEC idiom into a helper function, so call it instead of duplicating the code here. Signed-off-by: Derek Foreman Reviewed-by: Kristian Høgsberg Reviewed-by: Emil Velikov :04 04 57dcc9a36cb72627a1e91340f099355200434adb 180705d900106982a31274f4a068c8bc39526a7c Msrc bisect run success -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91077] dri2_glx.c:1186: undefined reference to `loader_open_device'
https://bugs.freedesktop.org/show_bug.cgi?id=91077 --- Comment #1 from Derek Foreman --- What configure options are you using? Can you attach a build log? Do you have any local changes? Having a hard time figuring this out, I can't reproduce it here, and dri2_glx.c uses other functions from loader.c so there should at least be a pile of other undefined references. Can you do a make clean and try again? Perhaps you have some kind of timestamp issue that led to a partial rebuild... -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91077] dri2_glx.c:1186: undefined reference to `loader_open_device'
https://bugs.freedesktop.org/show_bug.cgi?id=91077 --- Comment #2 from Vinson Lee --- Clean checkout and build on CentOS 6. $ ./autogen.sh --disable-dri3 --enable-sysfs --with-dri-drivers=swrast --with-gallium-drivers= $ make [...] CC XF86dri.lo dri_common.c: In function ‘dri2_convert_glx_attribs’: dri_common.c:469: warning: ‘profile’ may be used uninitialized in this function CCLD libglx.la CCLD libGL.la ./.libs/libglx.a(dri2_glx.o): In function `dri2CreateScreen': src/glx/dri2_glx.c:1186: undefined reference to `loader_open_device' collect2: ld returned 1 exit status -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91077] dri2_glx.c:1186: undefined reference to `loader_open_device'
https://bugs.freedesktop.org/show_bug.cgi?id=91077 --- Comment #3 from Julien Isorce --- Hi, I just sent a patch on the mailing list as I encountered the same problem on darwin. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90797] [ALL bisected] Mesa change cause performance case manhattan fail.
https://bugs.freedesktop.org/show_bug.cgi?id=90797 wendy.w...@intel.com changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #11 from wendy.w...@intel.com --- Bug has been verified as fixed with latest Mea master branch: Libdrm: (master)libdrm-2.4.61-13-g97be70b45eccc37e98a1cecf360593f36956ea42 Mesa:(master)028590cbc758e877b963ba430f0a0cb49e882a6b Xserver: (master)xorg-server-1.17.0-158-gfa12f2c150b2f50de9dac4a2b09265f13af353af Xf86_video_intel: (master)2.99.917-366-g87b5ca2c3ed45a46ac037e71e96922b1a7f8c10f Cairo:(master)2cf2d8e340a325adb205baf8e4bd64e1d1858008 Libva:(master)5d07b29687db6d17811b7ecf9b779377e9851a27 Libva_intel_driver:(master)0f6143e2e4bd70217887e1ad86a76200ad8b38a8 Kernel: (drm-intel-nightly)be39a7ed43b45f63aff1ad3b61008f67692db202 -- You are receiving this mail because: You are the QA Contact for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91079] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91079 Bug ID: 91079 Summary: New account request Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Other Assignee: mesa-dev@lists.freedesktop.org Reporter: marta.lofst...@linux.intel.com QA Contact: mesa-dev@lists.freedesktop.org Created attachment 116683 --> https://bugs.freedesktop.org/attachment.cgi?id=116683&action=edit Public ssh key -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91079] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91079 --- Comment #1 from Marta Löfstedt --- Created attachment 116684 --> https://bugs.freedesktop.org/attachment.cgi?id=116684&action=edit Public PGP key -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91079] New account request
https://bugs.freedesktop.org/show_bug.cgi?id=91079 Marta Löfstedt changed: What|Removed |Added CC||cwo...@cworth.org, ||marta.lofstedt@linux.intel. ||com --- Comment #2 from Marta Löfstedt --- Hi, I would like an account so that I can put up a public branch with my OpenGL ES 3.1 work. BR, Marta -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91077] dri2_glx.c:1186: undefined reference to `loader_open_device'
https://bugs.freedesktop.org/show_bug.cgi?id=91077 Emil Velikov changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Emil Velikov --- I do wonder if/when we can fold some of the conditional compilation mayhem in the loader, but until then I've pushed Julien's patch. Thanks for the prompt fix ! -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91098] vmwgfx null ptr dereference at vmw_screen_ioctl.c:76 due to ioctl failure
https://bugs.freedesktop.org/show_bug.cgi?id=91098 Bug ID: 91098 Summary: vmwgfx null ptr dereference at vmw_screen_ioctl.c:76 due to ioctl failure Product: Mesa Version: 10.6 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Other Assignee: mesa-dev@lists.freedesktop.org Reporter: freedesk...@pargon.nl QA Contact: mesa-dev@lists.freedesktop.org I'm experiencing occasional crashes of gnome-shell (3.16) due to failed ioctls requested by Mesa's vmware DRI backend. Any pointers on where I should take the apparent root issue would be appreciated - I have no idea whether Mesa or the kernel driver is at fault for the ioctl failing in the first place. Kernel logs (v4.0.5) report an ioctl failure: [15949.294396] [drm:vmw_generic_ioctl [vmwgfx]] *ERROR* Dropped master trying to access ioctl that requires authentication. [15949.294400] [drm] IOCTL ERROR Command 65, Error -13. [15949.296209] [drm:vmw_generic_ioctl [vmwgfx]] *ERROR* Dropped master trying to access ioctl that requires authentication. [15949.296214] [drm] IOCTL ERROR Command 65, Error -13. [15949.296468] [drm:vmw_generic_ioctl [vmwgfx]] *ERROR* Dropped master trying to access ioctl that requires authentication. [15949.296470] [drm] IOCTL ERROR Command 87, Error -13. [15949.296478] gnome-shell[337]: segfault at 20 ip 7ff502cb4680 sp 7ffeaeea96e8 error 4 in vmwgfx_dri.so[7ff50293f000+506000] Followed by a crash of gnome-shell, due to an apparent null pointer dereference: Core was generated by `gnome-shell --mode=gdm --wayland --display-server'. Program terminated with signal SIGSEGV, Segmentation fault. #0 vmw_region_size (region=0x0) at vmw_screen_ioctl.c:76 76 return region->size; (gdb) bt #0 vmw_region_size (region=0x0) at vmw_screen_ioctl.c:76 #1 0x7ff502cb65cc in vmw_svga_winsys_surface_create (sws=0x145aaa0, flags=(SVGA3D_SURFACE_HINT_TEXTURE | SVGA3D_SURFACE_HINT_RENDERTARGET), format=SVGA3D_A8R8G8B8, usage=0, size=..., numFaces=1, numMipLevels=1) at vmw_screen_svga.c:222 #2 0x7ff502cc0d46 in svga_screen_surface_create (svgascreen=svgascreen@entry=0x145b9c0, key=key@entry=0x1cc8c90) at svga_screen_cache.c:449 #3 0x7ff502cbf810 in svga_texture_create (screen=0x145b9c0, template=0x7ffeaeea9840) at svga_resource_texture.c:729 #4 0x7ff502b0797b in st_texture_create (st=st@entry=0x1536270, target=, format=format@entry=PIPE_FORMAT_B8G8R8A8_UNORM, last_level=last_level@entry=0, width0=width0@entry=16, height0=height0@entry=16, depth0=1, layers=1, nr_samples=0, bind=10) at state_tracker/st_texture.c:97 #5 0x7ff502ada27d in guess_and_alloc_texture (st=st@entry=0x1536270, stObj=stObj@entry=0x268bc00, stImage=stImage@entry=0x16b5060) at state_tracker/st_cb_texture.c:464 #6 0x7ff502ada3a5 in st_AllocTextureImageBuffer (ctx=0x150c200, texImage=0x16b5060) at state_tracker/st_cb_texture.c:517 #7 0x7ff502adcb9c in st_TexImage (ctx=0x150c200, dims=2, texImage=0x16b5060, format=6408, type=5121, pixels=0x1f3bc80, unpack=0x15273f8) at state_tracker/st_cb_texture.c:875 #8 0x7ff502a72e00 in teximage (ctx=0x150c200, compressed=compressed@entry=0 '\000', dims=dims@entry=2, target=3553, level=, internalFormat=, width=16, height=16, depth=1, border=0, format=6408, type=5121, imageSize=0, pixels=0x1f3bc80) at main/teximage.c:3364 #9 0x7ff502a740e0 in _mesa_TexImage2D (target=, level=, internalFormat=, width=, height=, border=, format=6408, type=5121, pixels=0x1f3bc80) at main/teximage.c:3403 #10 0x7ff513f093a3 in ?? () from /usr/lib/libcogl.so.20 #11 0x7ff513efed94 in ?? () from /usr/lib/libcogl.so.20 #12 0x7ff513f3008b in cogl_texture_allocate () from /usr/lib/libcogl.so.20 #13 0x7ff513f31880 in cogl_texture_2d_new_from_data () from /usr/lib/libcogl.so.20 #14 0x7ff5191a6b98 in pixbuf_to_cogl_texture (pixbuf=pixbuf@entry=0x2779de0) at st/st-texture-cache.c:473 #15 0x7ff5191a6bf1 in finish_texture_load (data=data@entry=0x2568a50, pixbuf=pixbuf@entry=0x2779de0) at st/st-texture-cache.c:518 #16 0x7ff5191a6daa in on_symbolic_icon_loaded (source=0x15f20f0, result=, user_data=0x2568a50) at st/st-texture-cache.c:553 #17 0x7ff516fcc1f3 in ?? () from /usr/lib/libgio-2.0.so.0 #18 0x7ff516fcc229 in ?? () from /usr/lib/libgio-2.0.so.0 #19 0x7ff51682490d in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #20 0x7ff516824ce0 in ?? () from /usr/lib/libglib-2.0.so.0 #21 0x7ff516825002 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #22 0x7ff518183326 in meta_run () from /usr/lib/libmutter.so.0 #23 0x0040208d in main (argc=1, argv=0x7ffeaeeaa028) at main.c:463 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-d
[Mesa-dev] [Bug 91099] [llvmpipe] piglit glsl-max-varyings >max_varying_components regression
https://bugs.freedesktop.org/show_bug.cgi?id=91099 Bug ID: 91099 Summary: [llvmpipe] piglit glsl-max-varyings >max_varying_components regression Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: v...@freedesktop.org QA Contact: mesa-dev@lists.freedesktop.org CC: jfons...@vmware.com, srol...@vmware.com mesa: e31bce4041122cd00712b60b4dc1eae6486f6579 (master 10.7.0-devel) $ ./bin/glsl-max-varyings --exceed-limits -auto Vertical axis: Increasing numbers of varyings. Horizontal axis: Which of the varyings contains the color. GL_MAX_VARYING_FLOATS = 128 glsl-max-varyings: src/mesa/state_tracker/st_glsl_to_tgsi.cpp:4655: ureg_dst dst_register(st_translate*, gl_register_file, unsigned int, unsigned int): Assertion `index < VARYING_SLOT_MAX' failed. Aborted (core dumped) (gdb) bt #0 0x7fc07799b267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7fc07799ceca in __GI_abort () at abort.c:89 #2 0x7fc07799403d in __assert_fail_base (fmt=0x7fc077af6028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fc076a3e67b "index < VARYING_SLOT_MAX", file=file@entry=0x7fc076a3d708 "src/mesa/state_tracker/st_glsl_to_tgsi.cpp", line=line@entry=4655, function=function@entry=0x7fc076a3ff00 "ureg_dst dst_register(st_translate*, gl_register_file, unsigned int, unsigned int)") at assert.c:92 #3 0x7fc0779940f2 in __GI___assert_fail (assertion=0x7fc076a3e67b "index < VARYING_SLOT_MAX", file=0x7fc076a3d708 "src/mesa/state_tracker/st_glsl_to_tgsi.cpp", line=4655, function=0x7fc076a3ff00 "ureg_dst dst_register(st_translate*, gl_register_file, unsigned int, unsigned int)") at assert.c:101 #4 0x7fc075bebc69 in dst_register (t=0xc31420, file=PROGRAM_OUTPUT, index=56, array_id=0) at src/mesa/state_tracker/st_glsl_to_tgsi.cpp:4655 #5 0x7fc075bec3aa in translate_dst (t=0xc31420, dst_reg=0xcda7d8, saturate=false, clamp_color=false) at src/mesa/state_tracker/st_glsl_to_tgsi.cpp:4756 #6 0x7fc075becb15 in compile_tgsi_instruction (t=0xc31420, inst=0xcda7c0, clamp_dst_color_output=false) at src/mesa/state_tracker/st_glsl_to_tgsi.cpp:4904 #7 0x7fc075beef45 in st_translate_program (ctx=0x7fc0784fe010, procType=1, ureg=0xe79180, program=0xe26870, proginfo=0xf08070, numInputs=3, inputMapping=0xf08448, inputSlotToAttr=0x0, inputSemanticName=0x0, inputSemanticIndex=0x0, interpMode=0x0, interpLocation=0x0, numOutputs=33, outputMapping=0xf08610, outputSlotToAttr=0xf086f0, outputSemanticName=0xf087d0 "", outputSemanticIndex=0xf08808 "", passthrough_edgeflags=0 '\000', clamp_color=0 '\000') at src/mesa/state_tracker/st_glsl_to_tgsi.cpp:5581 #8 0x7fc075a68de5 in st_translate_vertex_program (st=0xa64210, stvp=0xf08070, key=0x7ffe56dacd60) at src/mesa/state_tracker/st_program.c:348 #9 0x7fc075a69027 in st_get_vp_variant (st=0xa64210, stvp=0xf08070, key=0x7ffe56dacd60) at src/mesa/state_tracker/st_program.c:440 #10 0x7fc075bbe1f2 in update_vp (st=0xa64210) at src/mesa/state_tracker/st_atom_shader.c:158 #11 0x7fc075bb925b in st_validate_state (st=0xa64210) at src/mesa/state_tracker/st_atom.c:214 #12 0x7fc075a63e73 in st_draw_vbo (ctx=0x7fc0784fe010, prims=0x7ffe56dacf70, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=3, tfb_vertcount=0x0, indirect=0x0) at src/mesa/state_tracker/st_draw.c:199 #13 0x7fc075ba6212 in vbo_draw_arrays (ctx=0x7fc0784fe010, mode=5, start=0, count=4, numInstances=1, baseInstance=0) at src/mesa/vbo/vbo_exec_array.c:645 #14 0x7fc075ba6ca0 in vbo_exec_DrawArrays (mode=5, start=0, count=4) at src/mesa/vbo/vbo_exec_array.c:797 #15 0x00401ef2 in draw (num_varyings=33) at piglit/tests/shaders/glsl-max-varyings.c:233 #16 0x0040208c in piglit_display () at piglit/tests/shaders/glsl-max-varyings.c:273 #17 0x7fc078067f8e in run_test (gl_fw=0x976980, argc=2, argv=0x7ffe56dad448) at piglit/tests/util/piglit-framework-gl/piglit_winsys_framework.c:79 #18 0x7fc07804c999 in piglit_gl_test_run (argc=2, argv=0x7ffe56dad448, config=0x7ffe56dad300) at piglit/tests/util/piglit-framework-gl.c:191 #19 0x004014fd in main (argc=2, argv=0x7ffe56dad448) at piglit/tests/shaders/glsl-max-varyings.c:48 (gdb) frame 4 #4 0x7fc075bebc69 in dst_register (t=0xc31420, file=PROGRAM_OUTPUT, index=56, array_id=0) at src/mesa/state_tracker/st_glsl_to_tgsi.cpp:4655 4655assert(index < VARYING_SLOT_MAX); (gdb) print /d VARYING_SLOT_MAX $1 = 56 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. _
[Mesa-dev] [Bug 91098] vmwgfx null ptr dereference at vmw_screen_ioctl.c:76 due to ioctl failure
https://bugs.freedesktop.org/show_bug.cgi?id=91098 --- Comment #1 from Thomas Hellström --- Hi. Thanks for the bug report. I think the root problem is gnome-shell(gdm) dropping its master privileges and then trying to render. The reason this is not allowed in the vmwgfx driver is the following scenario: 1) A user switches away the X server VT and gets a console terminal. 2) User launches a DRM-aware malicious app that becomes master and authenticates itself. 3) The user switches back the X server 4) The malicious app can now open exported buffer objects at will and access or manipulate user private data. This is correctly blocked in the vmwgfx driver. So this is AFAICT a gnome-shell (gdm mode) bug. It shouldn't render when it drops its master privileges, so the gnome bugzilla would be good to start with. We'll follow up. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91099] [llvmpipe] piglit glsl-max-varyings >max_varying_components regression
https://bugs.freedesktop.org/show_bug.cgi?id=91099 Vinson Lee changed: What|Removed |Added Keywords||bisected CC||mar...@gmail.com --- Comment #1 from Vinson Lee --- 7ffc1fb928268f8493e88d45e9a006208d05f0f6 is the first bad commit commit 7ffc1fb928268f8493e88d45e9a006208d05f0f6 Author: Marek Olšák Date: Thu Mar 19 23:27:10 2015 +0100 gallium: bump shader input and output limits Reviewed-by: Roland Scheidegger Signed-off-by: Marek Olšák :04 04 c8ba9549231eff63c36137320a597d586a53298a a53d5640b434fc002eca189ffcb19aec79e1755a Msrc bisect run success -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91100] [softpipe] piglit egl-create-pbuffer-surface regression
https://bugs.freedesktop.org/show_bug.cgi?id=91100 Bug ID: 91100 Summary: [softpipe] piglit egl-create-pbuffer-surface regression Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: bisected, regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: v...@freedesktop.org QA Contact: mesa-dev@lists.freedesktop.org CC: bri...@vmware.com, mar...@gmail.com, martin.pe...@free.fr mesa: e31bce4041122cd00712b60b4dc1eae6486f6579 (master 10.7.0-devel) $ ./bin/egl-create-pbuffer-surface -auto egl-create-pbuffer-surface: sp_texture.c:360: softpipe_transfer_map: Assertion `box->x + box->width <= (int) u_minify(resource->width0, level)' failed. Aborted (core dumped) (gdb) bt #0 0x7f154073e267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7f154073feca in __GI_abort () at abort.c:89 #2 0x7f154073703d in __assert_fail_base (fmt=0x7f1540899028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7f153bb067b8 "box->x + box->width <= (int) u_minify(resource->width0, level)", file=file@entry=0x7f153bb06663 "sp_texture.c", line=line@entry=360, function=function@entry=0x7f153bb06a00 <__PRETTY_FUNCTION__.8823> "softpipe_transfer_map") at assert.c:92 #3 0x7f15407370f2 in __GI___assert_fail (assertion=0x7f153bb067b8 "box->x + box->width <= (int) u_minify(resource->width0, level)", file=0x7f153bb06663 "sp_texture.c", line=360, function=0x7f153bb06a00 <__PRETTY_FUNCTION__.8823> "softpipe_transfer_map") at assert.c:101 #4 0x7f153ba4dc10 in softpipe_transfer_map (pipe=0x417c, resource=0x1b1a1e0, level=0, usage=2, box=0x7ffd8acf97e0, transfer=0x1) at sp_texture.c:360 #5 0x7f153b97200b in pipe_transfer_map (transfer=0x7ffd8acf97d8, h=, w=, y=, x=, access=2, layer=0, level=0, resource=0x1b1a1e0, context=0x19adb20) at ../../../../src/gallium/auxiliary/util/u_inlines.h:447 #6 drisw_update_tex_buffer (drawable=, ctx=, res=0x1b1a1e0) at drisw.c:309 #7 0x7f153b9709a8 in dri_set_tex_buffer2 (pDRICtx=, target=3553, format=8410, dPriv=) at dri_drawable.c:245 #8 0x7f15410204a2 in dri2_bind_tex_image (drv=0x199fe50, disp=0x199f810, surf=0x1ac4720, buffer=12420) at egl_dri2.c:1288 #9 0x7f154101991a in eglBindTexImage (dpy=0x199f810, surface=, buffer=12420) at eglapi.c:948 #10 0x00402507 in draw (state=0x7ffd8acf9af0) at piglit/tests/egl/egl-create-pbuffer-surface.c:64 #11 0x00401d55 in event_loop (state=0x7ffd8acf9af0, test=0x7ffd8acf9b70) at piglit/tests/egl/egl-util.c:156 #12 0x004022fb in egl_util_run (test=0x7ffd8acf9b70, argc=2, argv=0x7ffd8acf9c88) at piglit/tests/egl/egl-util.c:302 #13 0x004026ef in main (argc=2, argv=0x7ffd8acf9c88) at piglit/tests/egl/egl-create-pbuffer-surface.c:100 (gdb) frame 4 #4 0x7f153ba4dc10 in softpipe_transfer_map (pipe=0x417c, resource=0x1b1a1e0, level=0, usage=2, box=0x7ffd8acf97e0, transfer=0x1) at sp_texture.c:360 360 assert(box->x + box->width <= (int) u_minify(resource->width0, level)); (gdb) print box->x $1 = 1 (gdb) print box->width $2 = 256 (gdb) print resource->width0 $3 = 256 (gdb) print level $4 = 0 184e4de3a126fa21945fe59f68b8a29977919fc4 is the first bad commit commit 184e4de3a126fa21945fe59f68b8a29977919fc4 Author: Martin Peres Date: Fri Jun 5 15:03:19 2015 +0300 main/version: make sure all the output variables get set in get_gl_override This fixes 2 warnings in gcc 5.1. Reviewed-by: Brian Paul Reviewed-by: Marek Olšák Signed-off-by: Martin Peres :04 04 d79f536961876f490be51ac2137ba8f18662bc49 cca6b9455a77b64fb2d684a9dd7b3edb20d533eb Msrc bisect run success -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91101] [softpipe] piglit glsl-1.50@execution@geometry@max-input-components regression
https://bugs.freedesktop.org/show_bug.cgi?id=91101 Bug ID: 91101 Summary: [softpipe] piglit glsl-1.50@execution@geometry@max-input-components regression Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: bisected, regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: v...@freedesktop.org QA Contact: mesa-dev@lists.freedesktop.org CC: mar...@gmail.com, srol...@vmware.com mesa: e31bce4041122cd00712b60b4dc1eae6486f6579 (master 10.7.0-devel) $ ./bin/shader_runner tests/spec/glsl-1.50/execution/geometry/max-input-components.shader_test -auto shader_runner: tgsi/tgsi_exec.c:1265: fetch_src_file_channel: Assertion `pos < 6 * 32' failed. Aborted (core dumped) (gdb) bt #0 0x7fc5c4efa267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 #1 0x7fc5c4efbeca in __GI_abort () at abort.c:89 #2 0x7fc5c4ef303d in __assert_fail_base (fmt=0x7fc5c5055028 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0x7fc5bfd54891 "pos < 6 * 32", file=file@entry=0x7fc5bfd5484f "tgsi/tgsi_exec.c", line=line@entry=1265, function=function@entry=0x7fc5bfd55230 <__PRETTY_FUNCTION__.7359> "fetch_src_file_channel") at assert.c:92 #3 0x7fc5c4ef30f2 in __GI___assert_fail (assertion=assertion@entry=0x7fc5bfd54891 "pos < 6 * 32", file=file@entry=0x7fc5bfd5484f "tgsi/tgsi_exec.c", line=line@entry=1265, function=function@entry=0x7fc5bfd55230 <__PRETTY_FUNCTION__.7359> "fetch_src_file_channel") at assert.c:101 #4 0x7fc5bfc0b9f7 in fetch_src_file_channel (mach=mach@entry=0x7fc5bdd36010, file=, swizzle=, index=index@entry=0x7ffd29c9e400, index2D=index2D@entry=0x7ffd29c9e410, chan=chan@entry=0x7ffd29c9e4d0, chan_index=0) at tgsi/tgsi_exec.c:1265 #5 0x7fc5bfc0c12d in fetch_source_d (mach=mach@entry=0x7fc5bdd36010, chan=chan@entry=0x7ffd29c9e4d0, reg=reg@entry=0x25bcf90, chan_index=chan_index@entry=0, src_datatype=TGSI_EXEC_DATA_FLOAT) at tgsi/tgsi_exec.c:1474 #6 0x7fc5bfc0c2d2 in fetch_source (mach=mach@entry=0x7fc5bdd36010, chan=chan@entry=0x7ffd29c9e4d0, reg=reg@entry=0x25bcf90, chan_index=chan_index@entry=0, src_datatype=src_datatype@entry=TGSI_EXEC_DATA_FLOAT) at tgsi/tgsi_exec.c:1490 #7 0x7fc5bfc0cdb8 in exec_vector_unary (mach=0x7fc5bdd36010, inst=inst@entry=0x25bcf60, op=op@entry=0x7fc5bfc09880 , src_datatype=src_datatype@entry=TGSI_EXEC_DATA_FLOAT, dst_datatype=TGSI_EXEC_DATA_UINT) at tgsi/tgsi_exec.c:2768 #8 0x7fc5bfc117e7 in exec_instruction (mach=mach@entry=0x7fc5bdd36010, inst=0x25bcf60, pc=pc@entry=0x7ffd29c9e734) at tgsi/tgsi_exec.c:4162 #9 0x7fc5bfc13827 in tgsi_exec_machine_run (mach=mach@entry=0x7fc5bdd36010) at tgsi/tgsi_exec.c:5151 #10 0x7fc5bfbdc615 in tgsi_gs_run (shader=, input_primitives=) at draw/draw_gs.c:216 #11 0x7fc5bfbdc6f0 in gs_flush (shader=0x25a3a20) at draw/draw_gs.c:415 #12 0x7fc5bfbdc9b8 in gs_tri_adj (shader=0x25a3a20, i0=, i1=, i2=, i3=, i4=, i5=5) at draw/draw_gs.c:517 #13 0x7fc5bfbdcd06 in gs_run (input_prims=, input_prims=, input_prims=, input_prims=, input_verts=, output_prims=, output_verts=, gs=) at draw/draw_decompose_tmp.h:342 #14 draw_geometry_shader_run (shader=0x25a3a20, constants=0x46f5, constants_size=0x6, input_verts=0x1, input_prim=0x7ffd29c9e9e0, input_info=0xb, output_verts=0x7ffd29c9e8c0, output_prims=0x7ffd29c9e900) at draw/draw_gs.c:638 #15 0x7fc5bfbee7a7 in fetch_pipeline_generic (middle=0x1e02080, fetch_info=0x46f5, fetch_info@entry=0x7ffd29c9e9c0, in_prim_info=0x7ffd29c9e9e0) at draw/draw_pt_fetch_shade_pipeline.c:290 #16 0x7fc5bfbeec16 in fetch_pipeline_linear_run (middle=, start=, count=6, prim_flags=) at draw/draw_pt_fetch_shade_pipeline.c:416 #17 0x7fc5bfbf4149 in vsplit_segment_simple_linear (vsplit=0x1eb6c40, vsplit=0x1eb6c40, icount=6, istart=0, flags=0) at draw/draw_pt_vsplit_tmp.h:240 #18 vsplit_run_linear (frontend=0x1eb6c40, start=0, count=6) at draw/draw_split_tmp.h:60 #19 0x7fc5bfbebb15 in draw_pt_arrays (draw=draw@entry=0x1df9d80, prim=12, start=0, count=count@entry=6) at draw/draw_pt.c:149 #20 0x7fc5bfbec143 in draw_vbo (draw=draw@entry=0x1df9d80, info=0x7ffd29c9eb10, info@entry=0x7ffd29c9ec10) at draw/draw_pt.c:564 #21 0x7fc5bfc8ff5a in softpipe_draw_vbo (pipe=0x1dedf10, info=0x7ffd29c9ec10) at sp_draw_arrays.c:147 #22 0x7fc5bfadbec0 in st_draw_vbo (ctx=, prims=, nr_prims=, ib=0x0, index_bounds_valid=, min_index=0, max_index=5, tfb_vertcount=0x0, indirect=0x0) at state_tracker/st_draw.c:286 #23 0x7fc5bfaa4de3 in vbo_draw_arrays (ctx=0x7fc5c5a5d010, mode=12, start=0, count=6, numInstances=1, baseInstance=0) at vbo/vbo_exec_array.c:645 #24 0x7fc5c553b103 in stub_g
[Mesa-dev] [Bug 90539] [softpipe] piglit varying-packing-simple dmat3 array regression
https://bugs.freedesktop.org/show_bug.cgi?id=90539 José Fonseca changed: What|Removed |Added Depends on||91099 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91099] [llvmpipe] piglit glsl-max-varyings >max_varying_components regression
https://bugs.freedesktop.org/show_bug.cgi?id=91099 José Fonseca changed: What|Removed |Added CC||i...@freedesktop.org Blocks||90539 --- Comment #2 from José Fonseca --- This is the same as bug 90539. And the change in http://cgit.freedesktop.org/~jrfonseca/mesa/commit/?h=max-varyings fixes the assertion. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106
Bug ID: 91106
Summary: glx: make check fails to build on osx
Product: Mesa
Version: git
Hardware: Other
OS: Mac OS X (All)
Status: NEW
Severity: normal
Priority: medium
Component: Mesa core
Assignee: mesa-dev@lists.freedesktop.org
Reporter: julien.iso...@gmail.com
QA Contact: mesa-dev@lists.freedesktop.org
Created attachment 116709
--> https://bugs.freedesktop.org/attachment.cgi?id=116709&action=edit
glx: fix unit tests build on osx
It fails because of missing symbols and some duplicated symbols.
The attached patch adds missing dependencies in tests/Makefile.am to fix some
missing symbols.
The attached patch also marks some functions with attribute weak to fix some
duplicated symbols due to redefinitions in the unit tests.
It allows to fix the build.
Then it passes some tests but crash around the 30th test
(glXCreateContextAttribARB_test.does_send_protocol):
It seems to crash when calling apple_cgl.choose_pixel_format. I investigated a
bit and glx/apple/apple_cgl.c::apple_cgl_init is not called (so
apple_cgl.choose_pixel_format = sym(h, "CGLChoosePixelFormat"); is not called).
backtrace with lldb:
* thread #1: tid = 0x86cd39, 0x, queue =
'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x
(lldb) bt
* thread #1: tid = 0x86cd39, 0x, queue =
'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
* frame #0: 0x
frame #1: 0x0001000879fa
glx-test`apple_visual_create_pfobj(pfobj=0x000100c22e88,
mode=0x000100c22328, double_buffered=0x000100c22ea4,
uses_stereo=0x000100c22ea5, offscreen=false) + 1610 at apple_visual.c:169
frame #2: 0x0001000833b9
glx-test`apple_glx_create_context(ptr=0x000100c22de8,
dpy=0x, screen=0, mode=0x000100c22328,
sharedContext=0x, errorptr=0x7fff5fbff09c,
x11errorptr=0x7fff5fbff09b) + 377 at apple_glx_context.c:161
frame #3: 0x0001000823ec
glx-test`applegl_create_context(psc=0x000100c22c90,
config=0x000100c22328, shareList=0x, renderType=0) + 332 at
applegl_glx.c:150
frame #4: 0x0001000439f3
glx-test`glXCreateContextAttribsARB(dpy=0x00010100e400,
config=0x000100c22328, share_context=0x, direct=0,
attrib_list=0x) + 451 at create_context.c:86
frame #5: 0x0001000155c1
glx-test`glXCreateContextAttribARB_test_does_send_protocol_Test::TestBody(this=0x000100c22310)
+ 97 at create_context_unittest.cpp:221
frame #6: 0x0001004a1f13 glx-test`void
testing::internal::HandleSehExceptionsInMethodIfSupported(object=0x000100c22310, method=0x0021,
location=0x00010057f3fd)(), char const*) + 131 at gtest.cc:2078
frame #7: 0x00010048c7b7 glx-test`void
testing::internal::HandleExceptionsInMethodIfSupported(object=0x000100c22310, method=0x0021,
location=0x00010057f3fd)(), char const*) + 119 at gtest.cc:2114
frame #8: 0x000100465b05
glx-test`testing::Test::Run(this=0x000100c22310) + 197 at gtest.cc:2150
frame #9: 0x000100466ddb
glx-test`testing::TestInfo::Run(this=0x000100c1a420) + 219 at gtest.cc:2326
frame #10: 0x000100467d07
glx-test`testing::TestCase::Run(this=0x000100c1a040) + 231 at gtest.cc:2444
frame #11: 0x0001004747f8
glx-test`testing::internal::UnitTestImpl::RunAllTests(this=0x000100c17590)
+ 952 at gtest.cc:4315
frame #12: 0x00010049ed93 glx-test`bool
testing::internal::HandleSehExceptionsInMethodIfSupported(object=0x000100c17590, method=0x000100474440,
location=0x00010057fabc)(), char const*) + 131 at gtest.cc:2078
frame #13: 0x00010048efc7 glx-test`bool
testing::internal::HandleExceptionsInMethodIfSupported(object=0x000100c17590, method=0x000100474440,
location=0x00010057fabc)(), char const*) + 119 at gtest.cc:2114
frame #14: 0x0001004743b6
glx-test`testing::UnitTest::Run(this=0x0001005b3458) + 422 at gtest.cc:3926
frame #15: 0x0001004ac491 glx-test`RUN_ALL_TESTS() + 17 at gtest.h:2288
frame #16: 0x0001004ac46c glx-test`main(argc=1,
argv=0x7fff5fbffac0) + 60 at gtest_main.cc:37
frame #17: 0x7fff886ee5c9 libdyld.dylib`start + 1
Also I tried to manually call __glXInitialize (because it is never called) in
tests/create_context_unittest.cpp::GetGLXScreenConfigs existing redefinition:
GetGLXScreenConfigs(Display * dpy, int scrn)
{
+ if(psc)
+ __glXInitialize(dpy);
But it still does not make "apple_cgl_init" to be called, because it crashes in
glxext.c:847: dpyPriv->codes = XInitExtension(dpy, __glXExtensionName);
* thread #1: tid = 0x86de8e, 0x000100989057 libX11.6.dylib`require_socket +
32, queue = 'com.apple.main
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #21 from Jose P. --- This seems to have been fixed, I can't see the corruption anymore. I'm using Chromium 43.0.2357.81 on Ubuntu 14.04 (64-bit) and Mesa 10.7.0-devel (git-20dca37 2015-06-23 trusty-oibaf-ppa). -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 Boyan Ding changed: What|Removed |Added CC||stu_...@126.com --- Comment #22 from Boyan Ding --- This bug also occur on my computer with Intel graphics. It seems that it only occur with DRI3 enabled, tested with both xf86-video-intel and xf86-video-modesetting drivers. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #23 from Furkan --- Still there for me. I'm using Ubuntu 15.04, Chrome 43.0.2357.130, Linux 4.1, and Mesa 10.7~git1506250730.d1663c~gd~v from oibaf ppa. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91111] [BYT regression] dEQP-GLES3.functional.shaders.texture_functions.texturelod.usamplercube_*
https://bugs.freedesktop.org/show_bug.cgi?id=9 Bug ID: 9 Summary: [BYT regression] dEQP-GLES3.functional.shaders.texture_functions.textur elod.usamplercube_* Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: brian.wil...@intel.com QA Contact: mesa-dev@lists.freedesktop.org Tested Mesa commit: c2a0600d5b0645533ba442b5ab879b23c2564a4d: "i965: Don't set NirOptions for stages that will use the vec4 backend." Plus patches: - 10.6-i965-do-not-round-line-width-when-multisampling-or-a.patch - 10.6-mesa-add-GL_RED-GL_RG-support-for-floating-point-tex.patch - 10.6-i965-Momentarily-pretend-to-support-ARB_texture_sten.patch - 10.6-Revert-i965-Advertise-a-line-width-of-40.0-on-Cherry.patch Testing a Mesa update on ChromeOS, the following dEQP tests fail on BYT: - dEQP-GLES3.functional.shaders.texture_functions.texturelod.usamplercube_vertex - dEQP-GLES3.functional.shaders.texture_functions.texturelod.usamplercube_fragment Sample failure: "Image comparison failed: difference = 450.979, threshold = 0.05" These tests pass on HSW, BDW and BSW, and passed on BYT with an older Mesa commit (November 18, 2014: 129178893b2260df22db96327c5ca9c2ce7db046 "glsl: Generate unique names for each const array lowered to uniforms" + ~10 patches) -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91112] [HSW/BYT] dEQP-GLES3.functional.uniform_api.random.23 test timeout
https://bugs.freedesktop.org/show_bug.cgi?id=91112 Bug ID: 91112 Summary: [HSW/BYT] dEQP-GLES3.functional.uniform_api.random.23 test timeout Product: Mesa Version: 10.6 Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: brian.wil...@intel.com QA Contact: mesa-dev@lists.freedesktop.org This isn't an outright test failure per-se, but dEQP is marking the test timeout as such. Timeout is on: dEQP-GLES3.functional.uniform_api.random.23 Mesa commit being tested: c2a0600d5b0645533ba442b5ab879b23c2564a4d: "i965: Don't set NirOptions for stages that will use the vec4 backend." Plus patches: - 10.6-i965-do-not-round-line-width-when-multisampling-or-a.patch - 10.6-mesa-add-GL_RED-GL_RG-support-for-floating-point-tex.patch - 10.6-i965-Momentarily-pretend-to-support-ARB_texture_sten.patch - 10.6-Revert-i965-Advertise-a-line-width-of-40.0-on-Cherry.patch This test passes on BDW and BSW, and passed on HSW/BYT with an older Mesa commit (November 18, 2014: 129178893b2260df22db96327c5ca9c2ce7db046 "glsl: Generate unique names for each const array lowered to uniforms" + ~10 patches) -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106 Julien Isorce changed: What|Removed |Added CC||bri...@vmware.com, ||emil.l.veli...@gmail.com, ||jerem...@freedesktop.org, ||jon.tur...@dronecode.org.uk ||, k...@bitplanet.net, ||matts...@gmail.com -- You are receiving this mail because: You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #24 from Boyan Ding --- Furkan, try launching chrome with LIBGL_DRI3_DISABLE=1 and see if the problem still persist. The problem at least went away on my machine when I disable DRI3. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #25 from Furkan --- I forgot to add, I have DRI3 disabled already. From my Xorg log: [12.974] (II) RADEON(0): [DRI2] Setup complete [12.974] (II) RADEON(0): [DRI2] DRI driver: radeonsi [12.974] (II) RADEON(0): [DRI2] VDPAU driver: radeonsi [12.974] (II) RADEON(0): Front buffer size: 9120K [12.974] (II) RADEON(0): VRAM usage limit set to 1857373K [12.974] (==) RADEON(0): DRI3 disabled -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90264] [Regression, bisected] Tooltip corruption in Chrome
https://bugs.freedesktop.org/show_bug.cgi?id=90264 --- Comment #26 from Eero Tamminen --- (In reply to Matt Whitlock from comment #15) > (In reply to Furkan from comment #14) > > For those of you who are using nouveau, does the problem go away after > > reverting the mesa commit that I bisected? > > > > http://cgit.freedesktop.org/mesa/mesa/commit/ > > ?id=95073a2dca03a48f4c77bc846a4a6d1f0eb81ae6 > > Yes, the problem goes away after reverting that commit on Mesa 10.5.6. > > The problem also goes away when using an old enough Chrome. Based on above comments, on Intel disabling DRI3 also makes the bug go away, but not on AMD. What about your Nouveau setup? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106 --- Comment #1 from Emil Velikov --- Hi Julien, I'm not sure how many people go bugzilla hunting for patches. Here are some things that stuck out: >From 2b424445a8c9028e72e2370da8dbdc969bb8717b Mon Sep 17 00:00:00 2001 From: Julien Isorce Date: Thu, 25 Jun 2015 08:59:27 +0100 Subject: [PATCH] glx: fix unit tests build on osx It fails because of missing symbols and some duplicated symbols. The patch adds missing dependencies in tests/Makefile.am to fix some missing symbols. The patch also marks some functions with attribute weak to fix some duplicated symbols due to redefinitions in the unit tests. Signed-off-by: Julien Isorce --- src/glx/glxcmds.c | 10 -- src/glx/glxcurrent.c | 8 +++- src/glx/glxextensions.c | 7 ++- src/glx/indirect_init.h | 2 ++ src/glx/tests/Makefile.am | 9 - 5 files changed, 31 insertions(+), 5 deletions(-) diff --git a/src/glx/glxcmds.c b/src/glx/glxcmds.c index 26ff804..f073ecb 100644 --- a/src/glx/glxcmds.c +++ b/src/glx/glxcmds.c @@ -55,6 +55,12 @@ #include #include +#if defined(GLX_USE_APPLEGL) +#define _ATTRIBUTE_WEAK __attribute__((weak)) +#else +#define _ATTRIBUTE_WEAK +#endif + (If we end up keeping this) Can we avoid redefining it X times ? Ian (the original author of these tests) should know the details as to why/how we don't end up with duplicated/conflicting symbols. --- a/src/glx/tests/Makefile.am +++ b/src/glx/tests/Makefile.am @@ -21,7 +21,6 @@ glx_test_SOURCES =\ enum_sizes.cpp\ fake_glx_screen.cpp\ fake_glx_screen.h\ -indirect_api.cpp\ mock_xdisplay.h\ query_renderer_unittest.cpp @@ -30,9 +29,17 @@ glx_test_SOURCES += \ query_renderer_implementation_unittest.cpp endif +if !HAVE_APPLEDRI +glx_test_SOURCES += indirect_api.cpp +endif + glx_test_LDADD = \ $(top_builddir)/src/glx/libglx.la \ $(top_builddir)/src/gtest/libgtest.la \ +$(top_builddir)/src/mapi/glapi/libglapi.la \ Which symbols are missing if we omit this ? Noone else seems to need it. $(top_builddir)/src/mapi/shared-glapi/libglapi.la \ +$(SHARED_GLAPI_LIB) \ Unset/empty variable. +$(GL_LIB_DEPS) \ Good catch, I think we can now nuke PTHEADS_LIBS below. Perhaps do this as a separate commit ? +$(X11_LIBS) \ Unset/empty variable. Upon closer look one can do a X11_* variable cleanup though mesa. $(PTHREAD_LIBS) endif -- 1.9.5 (Apple Git-50.3) -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106
--- Comment #2 from Emil Velikov ---
Although I would honestly suggest that one takes a closer look into
src/glx{,/apple} and give it some much needed love. Iirc Jon had some branches
which rework/clean things up which seems like the way forward imho.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91118] Skydrift (running in Wine) crashes on start
https://bugs.freedesktop.org/show_bug.cgi?id=91118 Bug ID: 91118 Summary: Skydrift (running in Wine) crashes on start Product: Mesa Version: 10.6 Hardware: Other URL: http://store.steampowered.com/app/91100/ OS: All Status: NEW Keywords: bisected, patch, regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: gyebr...@gmail.com QA Contact: mesa-dev@lists.freedesktop.org CC: imir...@alum.mit.edu, mar...@gmail.com Some of my games when running in Wine crash on start, either immediately on startup like Skydrift, or during the initial loading screen. Terminal output + Wine backtrace: http://pastebin.com/TDsv0ZTh The other game that crashes with an identical backtrace is named 'How to Survive', but no demo is available for this title. The crash is present with the software renderer too (LIBGL_ALWAYS_SOFTWARE=1) The problem doesn't occur with the binary Nvidia drivers (340.76), and reverting the following commit fixes the crash for me: commit 6b284f08ab399154ad10e2166440b44cbbdcb2c5 Author: Laura Ekstrand Date: Tue Feb 3 14:47:00 2015 -0800 main: _mesa_blit_framebuffer updates its arbitrary framebuffers. Previously, we used _mesa_update_state to update the currently bound framebuffers prior to performing a blit. Now that _mesa_blit_framebuffer uses arbitrary framebuffers, _mesa_update_state is not specific enough. To reproduce the problem in the demo version you need Wine (preferably the latest development version) and a Steam account. The game should run out-of-the-box after installation. This patch reliably fixes the problem for me: http://patchwork.freedesktop.org/patch/52969/ Please let me know if you need further logs. Fedora 22 32-bit Mesa 10.6-branchpoint-676-g7de8569 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) (prog-if 00 [VGA controller]) Kernel 4.0.5-300.fc22.i686+PAE xorg-x11-server-Xorg-1.17.2-1.fc22.i686 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91118] Skydrift (running in Wine) crashes on start
https://bugs.freedesktop.org/show_bug.cgi?id=91118 --- Comment #1 from Béla Gyebrószki --- The following patch by Ilia Mirkin also fixes the crash for me: diff --git a/src/mesa/main/context.c b/src/mesa/main/context.c index 79fa018..f7d8028 100644 --- a/src/mesa/main/context.c +++ b/src/mesa/main/context.c @@ -1638,6 +1638,8 @@ handle_first_current(struct gl_context *ctx) } } + _mesa_update_state(ctx); + /* We can use this to help debug user's problems. Tell them to set * the MESA_INFO env variable before running their app. Then the * first time each context is made current we'll print some useful The 2 different patches equally fix the crash for me in those 2 games. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91123] [swrast] piglit egl-create-pbuffer-surface regression
https://bugs.freedesktop.org/show_bug.cgi?id=91123 Bug ID: 91123 Summary: [swrast] piglit egl-create-pbuffer-surface regression Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Keywords: bisected, regression Severity: normal Priority: medium Component: Mesa core Assignee: mesa-dev@lists.freedesktop.org Reporter: v...@freedesktop.org QA Contact: mesa-dev@lists.freedesktop.org CC: emil.l.veli...@gmail.com, mar...@gmail.com mesa: 35d83793047b3de31a706fa2a62a233090ea7cfc (master 10.7.0-devel) $ ./bin/egl-create-pbuffer-surface -auto Segmentation fault (core dumped) (gdb) bt #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35 #1 0x7fc57c7f02b1 in memcpy (__len=262144, __src=, __dest=0x0) at /usr/include/x86_64-linux-gnu/bits/string3.h:53 #2 swrastGetImage (read=, x=, y=, w=, h=, data=0x0, loaderPrivate=0x977030) at platform_x11.c:175 #3 0x7fc5772ebbeb in swrastSetTexBuffer2 (pDRICtx=, target=, texture_format=8410, dPriv=0x977140) at swrast.c:110 #4 0x7fc57c7ed4a2 in dri2_bind_tex_image (drv=0x7b0e50, disp=0x7b0810, surf=0x977030, buffer=12420) at egl_dri2.c:1288 #5 0x7fc57c7e691a in eglBindTexImage (dpy=0x7b0810, surface=, buffer=12420) at eglapi.c:948 #6 0x00402507 in draw (state=0x7fff293a4900) at piglit/tests/egl/egl-create-pbuffer-surface.c:64 #7 0x00401d55 in event_loop (state=0x7fff293a4900, test=0x7fff293a4980) at piglit/tests/egl/egl-util.c:156 #8 0x004022fb in egl_util_run (test=0x7fff293a4980, argc=2, argv=0x7fff293a4a98) at piglit/tests/egl/egl-util.c:302 #9 0x004026ef in main (argc=2, argv=0x7fff293a4a98) at piglit/tests/egl/egl-create-pbuffer-surface.c:100 (gdb) frame 2 #2 swrastGetImage (read=, x=, y=, w=, h=, data=0x0, loaderPrivate=0x977030) at platform_x11.c:175 175 memcpy(data, idata, bytes); dd048543e944d95b4471572454cfa902392e3f61 is the first bad commit commit dd048543e944d95b4471572454cfa902392e3f61 Author: Marek Olšák Date: Tue May 26 12:47:03 2015 +0200 configure.ac: enable building GLES1 and GLES2 by default Reviewed-by: Matt Turner Reviewed-by: Emil Velikov :100644 100644 5594548ddfd174103f5c793a06504d25ea744d1b 84b404eb8b2b2985496ba4555fa301c50b66bc28 Mconfigure.ac bisect run success -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91123] [swrast] piglit egl-create-pbuffer-surface regression
https://bugs.freedesktop.org/show_bug.cgi?id=91123 --- Comment #1 from Marek Olšák --- The bisected commit can't have caused any regression. The problem is that you didn't enable GLES1 and GLES2 in Mesa, so the test skipped (or passed) before that. It's possible that this isn't even a regression, because swrast EGL support if pretty new. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 90817] swrast fails to load with certain remote X servers
https://bugs.freedesktop.org/show_bug.cgi?id=90817 --- Comment #5 from Jon TURNEY --- Something like this is also needed when the server is XWin on Cygwin/MinGW using WGL, where the set of fbConfigs comes from the native driver and don't match swrast's expectations. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106 --- Comment #3 from Jon TURNEY --- (In reply to Emil Velikov from comment #1) > +#if defined(GLX_USE_APPLEGL) > +#define _ATTRIBUTE_WEAK __attribute__((weak)) > +#else > +#define _ATTRIBUTE_WEAK > +#endif > + > (If we end up keeping this) Can we avoid redefining it X times ? Ian (the > original author of these tests) should know the details as to why/how we > don't end up with duplicated/conflicting symbols. These really are duplicates that the test harness provides to override the real versions. Unfortunately, ld on OSX doesn't behave that way, and the option -multiply_defined suppress seems to be obsolete. I'm not very keen on scattering __attribute__(weak) around to fix this, but I guess the only other approach is to split those symbols out into a separate object, which is linked with to produce libglx.a, but not into a convenience library which is used by the tests. > + $(top_builddir)/src/mapi/glapi/libglapi.la \ > Which symbols are missing if we omit this ? Noone else seems to need it. glapi_create_table_from_handle, which only exists on APPLE, if memory serves. But linking with glapi and shared-glapi doesn't seem right, so I think this is a sign that something else is wrong. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91106] glx: make check fails to build on osx
https://bugs.freedesktop.org/show_bug.cgi?id=91106 --- Comment #4 from Jon TURNEY --- (In reply to Emil Velikov from comment #2) > Iirc Jon had some > branches which rework/clean things up which seems like the way forward imho. Sorry, all the clean-up I did for __APPLE__ is already upstream, with the exception of the 2 patches which clearly need to be done in a better way. -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91130] Mesa's cl.h defines CL_VERSION_1_2 even though it is missing some OpenCL 1.2 functions
https://bugs.freedesktop.org/show_bug.cgi?id=91130 Bug ID: 91130 Summary: Mesa's cl.h defines CL_VERSION_1_2 even though it is missing some OpenCL 1.2 functions Product: Mesa Version: 10.5 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Other Assignee: mesa-dev@lists.freedesktop.org Reporter: devuran...@gmx.net QA Contact: mesa-dev@lists.freedesktop.org `clEnqueueFillBuffer` is part of OpenCL 1.2 [1] [2]. Mesa claims to support OpenCL 1.2: ``` # grep -B1 CL_VERSION /usr/include/CL/cl.h /* OpenCL Version */ #define CL_VERSION_1_0 1 #define CL_VERSION_1_1 1 #define CL_VERSION_1_2 1 ``` It declares `clEnqueueFillBuffer`: ``` # grep -B1 -A8 clEnqueueFillBuffer /usr/include/CL/cl.h extern CL_API_ENTRY cl_int CL_API_CALL clEnqueueFillBuffer(cl_command_queue /* command_queue */, cl_mem /* buffer */, const void * /* pattern */, size_t /* pattern_size */, size_t /* offset */, size_t /* size */, cl_uint/* num_events_in_wait_list */, const cl_event * /* event_wait_list */, cl_event * /* event */) CL_API_SUFFIX__VERSION_1_2; ``` But does not define it: ``` # scanelf -s clEnqueueFillBuffer /usr/lib/libOpenCL.so TYPE SYM FILE ET_DYN - /usr/lib/libOpenCL.so ``` Logically, it also seems to be missing in the API dispatcher [1]. I assume Mesa should not claim to support OpenCL 1.2 via `CL_VERSION_1_2`, if at least one of the OpenCL 1.2 functions is not implemented. [1]: https://www.khronos.org/registry/cl/sdk/1.2/docs/man/xhtml/clEnqueueFillBuffer.html [2]: https://www.khronos.org/registry/cl/specs/opencl-1.2.pdf#page=85 [3]: http://cgit.freedesktop.org/mesa/mesa/tree/src/gallium/state_trackers/clover/api/dispatch.cpp#n129 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] [Bug 91130] Mesa's cl.h defines CL_VERSION_1_2 even though it is missing some OpenCL 1.2 functions
https://bugs.freedesktop.org/show_bug.cgi?id=91130 Dennis Schridde changed: What|Removed |Added See Also||https://github.com/magnumri ||pper/JohnTheRipper/issues/1 ||470 -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
