Created attachment 16355 [details] Xorg.0.log System Environment: -------------------------- --Platform:965 --Architecture(32-bit,64-bit,compatiblity):32bit & 64bit --Kernel: 2.6.25-rc3 --2D driver: master a0ced923bb793aa22e6bfbeeec0888d3b42ce176 --3D driver: master 97709950e794ab24d3e1d5411a88e305f3878487 --Xserver: master 14396fdebac1868df17559220ed7aaa34c34251e --Drm: master 3ac74f3208ed15a990a0a26742fbfe566f08aa80 Bug detailed description: -------------------------- when run "./glean -o -r test.log -t vertattrib",test failed.follow is part of failure info: vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 4 is (0.2, 0, 0, 0) but expected (0, 0, 1, 0) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 5 is (0.6, 0, 0, 0) but expected (0, 0, 0, 0) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 6 is (0, 0, 0, 0) but expected (0, 1, 0, 0) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 7 is (0.498039, 0, 0, 0) but expected (0, 0, 0, 0) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 8 is (-1, 0, 0, 0) but expected (1, 0, 0, 0) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 9 is (0.4, 0, 0, 0) but expected (0, 0, 0, 1) (Testing glVertexAttrib4uivARB in display list mode) vertattrib: FAIL rgba8, win+pmap, id 76 Vertex Attribute 10 is (0.8, 0, 0, 0) but expected (0, 0, 0, 0) (Testing glVertexAttrib4uivARB in display list mode) Reproduce steps: ---------------- 1.xinit& 2../glean -r test.log -o -t vertattrib Current result: ---------------- test failed. Expected result: ---------------- pass
I can't reproduce it. Could you try the latest mesa code?
it's ok when using the latest code.
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.