System Environment: -------------------------- Arch: x86_64 Platform: Ironlake Libdrm: (master)libdrm-2.4.46-2-gfea5408098c3c3057958e85ea9d7146f0b08749e Mesa: (master)00d32cd5b4119b8c477326d72ae8d069ea87b49e Xserver: (master)xorg-server-1.14.99.1-137-g74469895e39fa38337f59edd64c4031ab9bb51d8 Xf86_video_intel:(master)2.21.12-5-g34c9b759fbab8d548108e954d55de38c6f5bec31 Cairo: (master)03c81d414d4edb710c91f96ddb7dbf73e5432583 Libva: (staging)6ba83cd306629e7579912627edab7a86d8c9ae1c Libva_intel_driver:(staging)1caf179b1425b13cacaa421c688c6df8369668c6 Kernel: (drm-intel-nightly) 3765d09d59ffb7ee735ed8c393ffb4b1405ffd02 Bug detailed description: ------------------------- It fails on ironlake with SNA, It works well with UXA. spec_OpenGL_2.0_max-samplers also fail with same bisect commit. Bisect shows:34c9b759fbab8d548108e954d55de38c6f5bec31 is the first bad commit. commit 34c9b759fbab8d548108e954d55de38c6f5bec31 Author: Chris Wilson <chris@chris-wilson.co.uk> AuthorDate: Tue Jul 16 19:39:37 2013 +0100 Commit: Chris Wilson <chris@chris-wilson.co.uk> CommitDate: Tue Jul 16 19:39:37 2013 +0100 sna: Note that borderClip region may be more than a singular box If the child is obscured, then borderClip will contain a list of valid boxes rather a singular extents. I thought this was covered by the clipList, but I was wrong. Reported-by: Jesse Barnes <jbarnes@virtuousgeek.org> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=66970 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> output: The result should be a solid block of half-bright yellow color Probe color at (1,1) Expected: 0.500000 0.500000 0.000000 Observed: 0.000000 0.498039 0.000000 PIGLIT: {'result': 'fail' } Reproduce steps: ---------------- 1. xinit 2. gnome-session 3. ./fragment-and-vertex-texturing -auto
commit a764a6e69b23f644957cf3e4e98868464f458758 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Jul 17 10:51:56 2013 +0100 sna: Fix typo in computing box intersection
Verified.Fixed.
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.