System Environment: -------------------------- Arch: i386 Platform: Pineview Libdrm: (master)2.4.31-1-g2cfac57d364d0166ed9472b086c16aea376f495a Mesa: (8.0)e86d90eb208292916c8a04c5d75499492003dd16 Xserver: (server-1.11-branch)xorg-server-1.11.3 Xf86_video_intel: (master)2.17.0-644-g4d8369f8e60fd4f5a0ef49f3e9866ea5ecb21927 Kernel: (drm-intel-fixes) 617cf884810b44384fe8e9431e9babeb80a2ff37 Bug detailed description: ------------------------- It fails at mesa master and mesa 8.0 branch on pineview. Bisect fails due to some mesa commit build failure. The last known bad commit is caebd7929dca802ece8ef36b0f85094d66133b57, the last known good commit is 1b33ae3a7da160033a2dc7abe6ef46dee3730c2e. Reproduce steps: ---------------- 1. start X 2. ./oglconform -z -s -suite all -v 2 -test multitex basic.allCases
I don't understand what the problem was bisecting. I was able to bisect to commit 85a52bf7b5f5f0317d15a51f94f294fc5e72d936 Author: Ian Romanick <ian.d.romanick@intel.com> Date: Thu Jan 19 17:29:37 2012 -0800 swrast: Use fixed-function processing instead _TexEnvProgram for DrawPixels This is a hack to work around drivers such as i965 that: - Set _MaintainTexEnvProgram to generate GLSL IR for fixed-function fragment processing. - Don't call _mesa_ir_link_shader to generate Mesa IR from the GLSL IR. - May use swrast to handle glDrawPixels. Since _mesa_ir_link_shader is never called, there is no Mesa IR to execute. Instead do regular fixed-function processing. Even on platforms that don't need this, the software fixed-function code is much faster than the software shader code. NOTE: This is a candidate for the 8.0 branch. Signed-off-by: Ian Romanick <ian.d.romanick@intel.com> Reviewed-by: Brian Paul <brianp@vmware.com> Reviewed-by: Eric Anholt <eric@anholt.net> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=44749 (cherry picked from commit 9be3be3c6654da18466626c2d45ff4d06b5fb953) *** This bug has been marked as a duplicate of bug 45872 ***
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.