| Summary: | ANV regression: Assertion `pass->attachment_count == framebuffer->attachment_count' failed | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Eero Tamminen <eero.t.tamminen> |
| Component: | Drivers/Vulkan/intel | Assignee: | Bas Nieuwenhuizen <bas> |
| Status: | VERIFIED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
| Severity: | normal | ||
| Priority: | medium | CC: | jason |
| Version: | git | Keywords: | regression |
| Hardware: | Other | ||
| OS: | All | ||
| See Also: | https://bugs.freedesktop.org/show_bug.cgi?id=111522 | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | |||
| Bug Blocks: | 111444 | ||
|
Description
Eero Tamminen
2019-05-27 10:01:24 UTC
Bas, this assertion hits due to your commit: 4689e98fe8:vulkan/wsi: Set X11 minImageCount to 3 If No Mans Sky is any indication, this is likely an issue where the app does not account for the increased number of images. Sadly, I still have no access to Aztec Ruins, so really cannot debug this ... (In reply to Bas Nieuwenhuizen from comment #2) > If No Mans Sky is any indication, this is likely an issue where the app does > not account for the increased number of images. If there are two apps with this bug, there are likely to be more. What would be best way to deal with this: - drop minImageCount to 2 (is this something app request?) - driconf variable for buggy apps - something else ? > Sadly, I still have no access to Aztec Ruins, so really cannot debug this ... Mark, can you check that? (Jason has looked more into AztecRuins and I think he has some contact at Kishonti to ask whether they will ever release a newer / fixed version. If not, probably better to drop AztecRuins.) On Wed, May 29, 2019 at 9:59 AM <bugzilla-daemon@freedesktop.org> wrote: > > Comment # 3 on bug 110765 from Eero Tamminen > > (In reply to Bas Nieuwenhuizen from comment #2) > > If No Mans Sky is any indication, this is likely an issue where the app does > > not account for the increased number of images. > > If there are two apps with this bug, there are likely to be more. Yeah .. It is clearly allowed by spec though and NMS had other issues too (could not deal with maxImageCount = 0). NMS is actually fixed these days and does not break anymore with high minImageCount. > > What would be best way to deal with this: > - drop minImageCount to 2 (is this something app request?) Thing is only having 2 images can really hurt performance in fullscreen. > - driconf variable for buggy apps That was what I was going for. > - something else > ? > > > > Sadly, I still have no access to Aztec Ruins, so really cannot debug this ... > > Mark, can you check that? > > (Jason has looked more into AztecRuins and I think he has some contact at > Kishonti to ask whether they will ever release a newer / fixed version. If > not, probably better to drop AztecRuins.) > > ________________________________ > You are receiving this mail because: > > You are the assignee for the bug. (In reply to Bas Nieuwenhuizen from comment #4) > > Comment # 3 on bug 110765 from Eero Tamminen > > - driconf variable for buggy apps > > That was what I was going for. In AztecRuins case, there's a problem that GfxBench is a benchmark with multiple test-cases, and workaround is needed only for AztecRuins test (which is in the latest version the only test supporting Vulkan). For the command line version of GfxBench, such option would need to match also command line options ("vulkan_5_*"). Ping. Do we have a driconf variable for this? Does someone just need to wire up the driconf stuff in anv? (In reply to Eero Tamminen from comment #5) > (In reply to Bas Nieuwenhuizen from comment #4) > > > Comment # 3 on bug 110765 from Eero Tamminen > > > - driconf variable for buggy apps > > > > That was what I was going for. > > In AztecRuins case, there's a problem that GfxBench is a benchmark with > multiple test-cases, and workaround is needed only for AztecRuins test > (which is in the latest version the only test supporting Vulkan). Additionally, the names of the binaries for all GfxBench versions are the same, and there are two of those binaries, GUI and command line version. > For the command line version of GfxBench, such option would need to match > also command line options ("vulkan_5_*"). Or "vulkan_*", if this is a generic issue on GfxBench Vulkan backend. Not sure what to do with the GUI version. Verified that Eric's MR would fix this also for me: https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1819 Eric merged his MR and onscreen Vulkan Aztec Ruins test works again. |
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.