Bug 103824

Summary: [SNB] SynMark GSCloth test renders wrong
Product: Mesa Reporter: Eero Tamminen <eero.t.tamminen>
Component: Drivers/DRI/i965Assignee: Intel 3D Bugs Mailing List <intel-3d-bugs>
Status: RESOLVED MOVED QA Contact: Intel 3D Bugs Mailing List <intel-3d-bugs>
Severity: normal    
Priority: medium    
Version: git   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Attachments: Incorrect rendering screenshot
Screenshot of incorrect rendering

Description Eero Tamminen 2017-11-20 13:55:48 UTC
Created attachment 135603 [details]
Incorrect rendering screenshot

Mesa fails SynMark render validation for OglGSCloth test on SNB:
   ./synmark2 OglGSCoth

Rendering is obviously incorrect (see the the attachment).  Francesco's recent GEN6-7 Transform feedback optimization patch series seems to make this somewhat worse.

I don't know whether Mesa has ever rendered it correctly on SNB, the issue has been there at least a year.  Rendering is fine on GEN7+ (also with Francesco's patch series).

Unlike most of the other tests we run regularly (which work fine), GSCloth uses geometry shaders, streamout and transform feedback.  GfxBench Manhattan uses also transform feedback, but that at least didn't have obvious rendering issues on SNB like this test.
Comment 1 Eero Tamminen 2018-01-17 07:40:33 UTC
i965 still renders this wrong on SNB.
Comment 2 Eero Tamminen 2019-01-09 11:56:29 UTC
Created attachment 143034 [details]
Screenshot of incorrect rendering

Added screenshot from latest Mesa git version.  Output is now marginally better than year ago (all content is now in correct location), but still clearly broken.

PS. Not really related to this bug, but on SNB SynMark OglTerrain*Inst tests fail to:
"Cannot allocate memory for terrain data, need 1216 layers, available 512"
Comment 3 GitLab Migration User 2019-09-25 19:05:54 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1655.

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.