[Bug 106493] "New game" in stellaris triggers Assertion `rtex->surface.u.legacy.level[level].dcc_fast_clear_size' failed.
https://bugs.freedesktop.org/show_bug.cgi?id=106493
Bug ID: 106493 Summary: "New game" in stellaris triggers Assertion `rtex->surface.u.legacy.level[level].dcc_fast_clear_si ze' failed. Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/radeonsi Assignee: dri-devel@lists.freedesktop.org Reporter: mceier+freedesktop@gmail.com QA Contact: dri-devel@lists.freedesktop.org
Created attachment 139529 --> https://bugs.freedesktop.org/attachment.cgi?id=139529&action=edit 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.
https://bugs.freedesktop.org/show_bug.cgi?id=106493
Mariusz Ceier mceier+freedesktop@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #139529|0 |1 is obsolete| |
--- Comment #1 from Mariusz Ceier mceier+freedesktop@gmail.com --- Created attachment 139535 --> https://bugs.freedesktop.org/attachment.cgi?id=139535&action=edit 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.
https://bugs.freedesktop.org/show_bug.cgi?id=106493
GitLab Migration User gitlab-migration@fdo.invalid changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |MOVED Status|NEW |RESOLVED
--- Comment #2 from GitLab Migration User gitlab-migration@fdo.invalid --- -- 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.
dri-devel@lists.freedesktop.org
-
bugzilla-daemon＠freedesktop.org