Bug 79154

Summary: [Tesseract Game] 4xMSAA Causes Visible Wireframes
Product: Mesa Reporter: mmstickman
Component: Drivers/Gallium/r600Assignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact:
Severity: normal    
Priority: medium    
Version: git   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:
Attachments: Screenshot of the wireframes

Description mmstickman 2014-05-23 21:56:24 UTC
Created attachment 99678 [details]
Screenshot of the wireframes

Currently running the latest mesa git with a Radeon HD 7950. Simply set MSAA to 4x to experience this bug.
Comment 1 mmstickman 2014-05-23 22:31:56 UTC
After testing on a Radeon HD 6850 and 4870 machine, this bug exists on r600 as well.
Comment 2 smoki 2014-05-24 01:35:39 UTC
 Again like in bug 79155, you seems to use spill-fixes and bug is related to that - so you should mention that i think :).

 Without spill-fixes MSAA 2x works for me on Radeon 8400, but with MSAA 4x there is crash when loading 'complex' map with message "LLVM ERROR: ran out of registers during register allocation".
Comment 3 mmstickman 2014-05-24 01:42:42 UTC
I don't think it would be related to that considering this also happens on my Radeon HD 4870 and 6850 machines which do not use LLVM.
Comment 4 smoki 2014-05-24 01:54:56 UTC
 OK then better open bug against r600 for that issue - that is clear case :). But this bug against radeonsi and bug 79155 are reletad because they are blocked by bug 75276, because currently you cannot see them without experimental code from that bug.
Comment 5 GitLab Migration User 2019-09-18 19:16:25 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/513.

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.