Created attachment 85406 [details]
with the patch

Created attachment 85407 [details]
without the patch

Anuj, can you look at this?  The break bisects to your commit.

Yes, I'll investigate it soon.

Armin, Can you take an apitrace of the attached frame? This will help me reproduce it on SNB.

apitrace output is about 282 MB uncompressed, 66 MB compressed with xz -9. I don't think I can post such a large file here.

I can upload it somewhere else if you desire.

In Qt gui program, running retrace I noticed this

Medium severity API unknown issue 1, FBO incomplete: Unsupported HW texture/renderbuffer format attached: MESA_FORMAT_AL88
Medium severity API unknown issue 2, FBO incomplete: driver marked FBO as incomplete [-1]
Medium severity API unknown issue 1, FBO incomplete: Unsupported HW texture/renderbuffer format attached: MESA_FORMAT_SL8
Medium severity API unknown issue 2, FBO incomplete: driver marked FBO as incomplete [-1]
Medium severity API unknown issue 1, FBO incomplete: Unsupported HW texture/renderbuffer format attached: MESA_FORMAT_SLA8
Medium severity API unknown issue 2, FBO incomplete: driver marked FBO as incomplete [-1]

etc ...

(In reply to comment #6)

> I can upload it somewhere else if you desire.
I'm okay if you can share the file somewhere else (google drive etc.).
 
> In Qt gui program, running retrace I noticed this
> 
> Medium severity API unknown issue 1, FBO incomplete: Unsupported HW
> texture/renderbuffer format attached: MESA_FORMAT_AL88
I looked at these error messages. They are coming from _mesa_CheckFramebufferStatus() => _mesa_test_framebuffer_completeness() => intel_validate_framebuffer() in i965/intel_fbo.c.
Few questions for you:
- Do you see these errors only during retrace or even with normal game playing?
- Do you see these errors with and without mesa commit 079bdba...?

Above two questions will help me figure out if these error messages have anything to do with mesa commit 079bdba or an apitrace retracing issue.

http://www.sendspace.com/file/iicja3

Here's the compressed data file from apitrace.

I see the warnings/errors only when running retrace ... Even with LIBGL_DEBUG=verbose it's silent at runtime (minus wine direct3d warnings).

I'll rebuild mesa without the mentioned commit later and report again.

I've built

commit dbc1f3677c1deb32358a6a53f0ad3638a78c7c4f
Author: José Fonseca <jfonseca@vmware.com>
Date:   Mon Oct 7 17:09:46 2013 -0700

    util/u_math: Fix C++ include of u_math.h on MSVC.
    
    GNU C++ compiler declares the C99 lrint, etc. when _GNU_SOURCE is
    defined, but MSVC does not.
    
    Trivial.

And reverted the commit mentioned in the first comment. Couldn't revert it in any later revision because first revision after this one changes the same files as the mentioned commit did.

However, the warnings mentioned in Comment 6 still exist when doing retrace of the now correctly working game.

Thanks for the trace file. Warnings produced by apitrace look unrelated to this issue on SNB. I was able to reproduce it on SNB as well as on IVB. I'm working on it.

I've posted a patch to fix the issue on mesa-dev mailing list: "i965: Do not set bilinear_filter flag in case of multisample blits". Could you please test the patch?

Issue is gone after applying the patch. Thanks!

mesa master commit logs:

commit f278d49c4bcfedbda10cb224cb251e3755e88288
Author: Anuj Phogat <anuj.phogat@gmail.com>
Date:   Fri Oct 18 16:07:42 2013 -0700

    i965: Do not set bilinear_filter flag in case of multisample blits

    Setting bilinear_filter flag in case of multisample blits with
    GL_LINEAR filter causes incorrect behavior in translate_dst_to_src()
    function. This broke Modern Warfare (1, 2 and 3) on SNB, IVB and HSW.
    
    Tested on SNB and IVB, no Piglit regressions. Trace file of the game
    (taken with apitrace) works fine with this patch.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=69078
    Cc: mesa-stable@lists.freedesktop.org
    Signed-off-by: Anuj Phogat <anuj.phogat@gmail.com>
    Reported-by: Armin K <krejzi@email.com>
    Tested-by: Armin K <krejzi@email.com>
    Reviewed-by: Paul Berry <stereotype441@gmail.com>