Summary: | [regression,bisected] incomplete screenshots in some cases | ||
---|---|---|---|
Product: | Mesa | Reporter: | Igor Gnatenko <i.gnatenko.brain> |
Component: | Drivers/DRI/i965 | Assignee: | Jason Ekstrand <jason> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | idr, i.gnatenko.brain, laura, tiagomatos |
Version: | 10.5 | ||
Hardware: | Other | ||
OS: | All | ||
See Also: |
https://bugs.freedesktop.org/show_bug.cgi?id=89316 https://bugs.freedesktop.org/show_bug.cgi?id=89314 |
||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Igor Gnatenko
2015-02-24 04:32:21 UTC
oops. I did bad copy/paste. commit 9b8bd67768769b685c25e1276e053505aede5f93 Author: Kenneth Graunke <kenneth@whitecape.org> Date: Wed Dec 31 16:47:25 2014 -0800 i965: Show opt_vector_float() and later passes in INTEL_DEBUG=optimizer. In order to support calling opt_vector_float() inside a condition, this patch makes OPT() a statement expression: https://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html We've used that elsewhere already. Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Matt Turner <mattst88@gmail.com> This commit is in the 10.5 branch. Ken: Could you take a look at this? Igor: Can you try running Mesa with INTEL_DEBUG=vs,gs at commit 6171131 (the commit before your bisect) and at commit 9b8bd67 and attach the output? We ought to be able to figure out what went wrong by looking at the difference in generated GPU assembly. (In reply to Ian Romanick from comment #2) > This commit is in the 10.5 branch. > > Ken: Could you take a look at this? > > Igor: Can you try running Mesa with INTEL_DEBUG=vs,gs at commit 6171131 (the > commit before your bisect) and at commit 9b8bd67 and attach the output? We > ought to be able to figure out what went wrong by looking at the difference > in generated GPU assembly. you mean `export INTEL_DEBUG=vs,gs` and run `startx` or how I can set it? Thanks for the report. I'm doubtful that the bisected commit is at fault. It's just adding some extra debugging capabilities and shouldn't change anything else at all. Could you reconfirm the bisection? My bisect yielded: # bad: [d1e21325cf3c394f5fb28808a113826ea3b7f54b] gallium/hud: also try R8_UNORM format for font texture # good: [a4ffc2a445055a81a655e64d57ee393a14a2eb16] i965: Move fs_visitor ra pass to new fs_visitor::allocate_registers() git bisect start '10.5-branchpoint' '10.4-branchpoint' # good: [eaae92a349af1fd6641c4bdd4bfd1185b1b6fe3e] st/mesa: fix GL_PRIMITIVE_RESTART_FIXED_INDEX git bisect good eaae92a349af1fd6641c4bdd4bfd1185b1b6fe3e # good: [aa479a69d6c9710be4d1c63e706f869bb97ad127] nir: silence compiler warning from visit_src() call git bisect good aa479a69d6c9710be4d1c63e706f869bb97ad127 # bad: [291d7ef84dcd83962515cbd7ce91ce1ff70930ed] mesa: improve error messaging for format CSV parser git bisect bad 291d7ef84dcd83962515cbd7ce91ce1ff70930ed # bad: [8bbc5e27810a005b8e0c89ab1016a5ba6cff73d2] st/nine: Remove duplicated code for ps texcoord input declaration git bisect bad 8bbc5e27810a005b8e0c89ab1016a5ba6cff73d2 # good: [76086d7120152ebced634875889612d0c40a37bb] mesa: change assert to unreachable in two format functions git bisect good 76086d7120152ebced634875889612d0c40a37bb # bad: [d2f2a550cf590ec1c9c4d94e07e1f0a0c837f891] st/nine: Add new texture format strings git bisect bad d2f2a550cf590ec1c9c4d94e07e1f0a0c837f891 # bad: [ef0499af255ecd3a9abbd350ace5e00a744adc00] i965/pixel_read: Use meta_pbo_GetTexSubImage for PBO ReadPixels git bisect bad ef0499af255ecd3a9abbd350ace5e00a744adc00 # good: [404660e3c7bc6d13ae1d40185a02bfff6b956ac9] i965/mipmap_tree: Add a depth parameter to create_for_bo git bisect good 404660e3c7bc6d13ae1d40185a02bfff6b956ac9 # good: [e24d17e08cb19bbecadb22ed43b25eeec26cde27] formats: Use a hash table for _mesa_format_from_array_format git bisect good e24d17e08cb19bbecadb22ed43b25eeec26cde27 # good: [8546fe900ca4c6059614dae8a77b3a97fafeb629] meta: Add an implementation of GetTexSubImage for PBOs git bisect good 8546fe900ca4c6059614dae8a77b3a97fafeb629 # first bad commit: [ef0499af255ecd3a9abbd350ace5e00a744adc00] i965/pixel_read: Use meta_pbo_GetTexSubImage for PBO ReadPixels (In reply to Rui Tiago Matos from comment #5) > My bisect yielded: > > # first bad commit: [ef0499af255ecd3a9abbd350ace5e00a744adc00] > i965/pixel_read: Use meta_pbo_GetTexSubImage for PBO ReadPixels Thanks! That's much more believable. There have been some fixes specifically for this commit, so retesting master is probably advisable. I'm adding a couple of related bugs to the See Also field. This is a bug in the meta PBO path due to GNOME Shell's scissor settings affecting the download. I've put together a patch: http://lists.freedesktop.org/archives/mesa-dev/2015-February/078074.html (In reply to Jason Ekstrand from comment #7) > This is a bug in the meta PBO path due to GNOME Shell's scissor settings > affecting the download. I've put together a patch: > > http://lists.freedesktop.org/archives/mesa-dev/2015-February/078074.html That fixes it for me, thanks Should be fixed by commit b1ab02d9c0cc11ba8ef4efaba9452d644b6a0811 Author: Jason Ekstrand <jason.ekstrand@intel.com> Date: Fri Feb 27 12:29:03 2015 -0800 meta/TexSubImage: Stash everything other than PIXEL_TRANSFER/store in meta_begin |
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.