| Summary: | "New game" in stellaris triggers Assertion `rtex->surface.u.legacy.level[level].dcc_fast_clear_size' failed. | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Mariusz Ceier <mceier+freedesktop> |
| Component: | Drivers/Gallium/radeonsi | Assignee: | Default DRI bug account <dri-devel> |
| Status: | RESOLVED MOVED | QA Contact: | Default DRI bug account <dri-devel> |
| Severity: | normal | ||
| Priority: | medium | CC: | mceier+freedesktop |
| Version: | git | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Attachments: |
Backtrace
Detailed backtrace |
||
Created attachment 139535 [details]
Detailed backtrace
Seems like the workaround is to set "Multisample level" option to 0. Any other value (2,4,8) triggers the assertion.
Attached more detailed backtrace.
-- 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/1313. |
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.
Created attachment 139529 [details] Backtrace Stellaris triggers assertion when clicking on "New game" and mesa is built in debug mode: stellaris: /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/gallium/drivers/radeonsi/si_clear.c:256: vi_dcc_clear_level: Assertion `rtex->surface.u.legacy.level[level].dcc_fast_clear_size' failed. The comment above the assertion says: /* If this is 0, fast clear isn't possible. (can occur with MSAA) */ if it can occur with MSAA should it really be an assertion ? I have Radeon Fury X. Attaching backtrace.