Bug 81404 - [IVB] ES3-CTS.gtf.GL3Tests.framebuffer_blit.framebuffer_blit_functionality_multisampled_to_singlesampled_blit hits assertion failure in blorp
Summary: [IVB] ES3-CTS.gtf.GL3Tests.framebuffer_blit.framebuffer_blit_functionality_mu...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-07-16 02:36 UTC by Ian Romanick
Modified: 2017-02-28 20:05 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Romanick 2014-07-16 02:36:14 UTC
On my IVB laptop with current Mesa master (9a723b970), I hit:

Test case 'ES3-CTS.gtf.GL3Tests.framebuffer_blit.framebuffer_blit_functionality_multisampled_to_singlesampled_blit'..
cts-runner: gen7_blorp.cpp:190: uint32_t gen7_blorp_emit_surface_state(brw_context*, const brw_blorp_params*, const brw_blorp_surface_info*, uint32_t, uint32_t, bool): Assertion `(fieldval & ~ (((1<<((13)-(0)+1))-1)<<(0))) == 0' failed.
Aborted (core dumped)

This is not a failure that I recall seeing before, so I think it is a recent change.  I have not had a chance to bisect yet.
Comment 1 Kenneth Graunke 2014-07-16 22:43:40 UTC
Bisecting may not be that useful - that assertion just means you're programming a value for a field which is too large to fit in the number of bits the hardware uses to represent it.

It will probably be pretty easy to fix upon inspection.
Comment 2 Matt Turner 2017-02-28 19:45:29 UTC
Mark, I see that we're running this test in CI on HSW, BDW, and SKL. Why isn't it being run on IVB?
Comment 3 Mark Janes 2017-02-28 20:05:24 UTC
This tests passes in CI on a nightly basis.


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.