Summary: | [swrast] SIGSEGV swrast/s_texfilter.c:3000 | ||
---|---|---|---|
Product: | Mesa | Reporter: | Vinson Lee <vlee> |
Component: | Mesa core | Assignee: | Brian Paul <brianp> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | critical | ||
Priority: | medium | ||
Version: | git | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Bug Depends on: | |||
Bug Blocks: | 30124 |
Description
Vinson Lee
2010-10-04 13:44:11 UTC
The crash occurs before and after the glsl2 merge. git bisect bad 6c03c576cc49bbb008de66d374f4302ff0fe0390 git bisect bad 15a3b42e135a3a2cb463ec3cff80a55dd8528051 The crash occurs at the shader-file-reorg merge (2010 Jun 11). git bisect bad ec2b92f98c2e7f161521b447cc1d9a36bce3707c The crash occurs at the graw-tests merge (2010 May 14). git bisect bad c7ac03d3964400169ba0dd769e06796c9830aee1 piglit glsl-fs-shadow2d-bias passes at the gallium-dynamicstencilref merge (2010 Feb 12). git bisect good 0087f9dc0690e5de139f89ea4577b1824b918757 2b5de09b3ea8754fb004d4f216bca29303f99490 is the first bad commit commit 2b5de09b3ea8754fb004d4f216bca29303f99490 Author: Brian Paul <brianp@vmware.com> Date: Tue Mar 23 17:55:41 2010 -0600 swrast: improve depth texture mipmap selection We still don't do proper min/mag filtering but this is better than just sampling the base mipmap level all the time. Fixes piglit depth-level-clamp test. Fixes fd.o bug 27256. :040000 040000 df45cad5ad0657b356c7472c5eea1a1e9052a303 9a4258e852c08e4d8934765d29c4cc7c9a6f2a82 M src bisect run success Looks like the Sep 30 change to the test itself exposed this bug. Fixed in Mesa/master with commit fb5e6f88fc426e53af26e98d1c336222a8952cc5. I'll cherry-pick this to the 7.9 branch after you verify the fix, Vinson. mesa: 2cf3199ee3b0014bc426bc3163dfa279c00eabb3 (master) Verified that the crash is fixed. OK, cherry-picked to 7.9 now too. mesa: 34c518be52958c9facd294955a81286293a6ed0b (7.9) Verified fixed on 7.9 branch. |
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.