Created attachment 14612 [details] test case System Environment: -------------------------- --Platform: i915 i965 --Architecture(32-bit,64-bit,compatiblity): all --2D driver: commit 6935c732c351585f31e2094c4201a00e3d5529b3 --3D driver: commit 9bd2cb7f90ac434ec5be7d388f899976bf902dc1 --Xserver: commit aec0d06469a2fa7440fdd5ee03dc256a68704e77 --Drm: commit e87cec19687089f9f268ec0eb81b57e6fb8de6a9 Bug detailed description: ------------------------- This issue make glean test case api2 failed on i915 and i965. This issue seems introduced by following commit, and seems glStencilFuncSeparate in call table is correct set: commit dd1d66fc4ab5d7064113a2017a431c3461598b91 Author: Kristian Høgsberg <krh@redhat.com> Date: Fri Feb 22 18:06:19 2008 -0500 intel: Merge intel_context.c from i915 and i965. Reproduce steps: ---------------- 1. start X 2. compile and run attached test case Current result: ---------------- Mesa warning: couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable Mesa warning: User called no-op dispatch function (an unsupported extension function?) Mesa warning: User called no-op dispatch function (an unsupported extension function?) glStencilFuncSeparate not correct Expected result: ---------------- glStencilFuncSeparate should work correctly.
Created attachment 14613 [details] xorg log
Created attachment 14614 [details] xorg conf
Did the commit also introduce the libtxc_dxtn.so warning?
Commit 60c0f09abb9421de359cd92e094a943d650fc7fa should fix this.
(In reply to comment #3) > Did the commit also introduce the libtxc_dxtn.so warning? > no, it didn't
I tried git tip, this issue still exists on both i915 and i965
Oh, I made a mistake when I'm building it. it's already fixed by your commit. thanks
verified on both 915 and 965
(In reply to comment #7) > Oh, I made a mistake when I'm building it. > it's already fixed by your commit. thanks Ah phew :) Good news, thanks for testing.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.