Yes, that's what I use.
The release is AFAIK less than two weeks away (barring delays), and
after that it's likely that a newer version will pass into testing. Once
a newer-enough version is available, it should resolve this.
For additional reference,
https://forums.lenovo.com/topic/view/27/5085655 has another report of
the issue, and links to
https://gitlab.freedesktop.org/drm/amd/-/issues/1632 as being an
upstream(?) bug report which covers it. Not sure how directly applicable
those are, but just in case...
Thanks! Looks like someone found one particular commit which causes
this. They say, that fixed commit will be in kernel 5.13. I hope this
will be imported to Debian's 5.10 LTS as well, so I can continue to use
5.10?
Should I report it somewhere as Debian bug, to make sure its being
backported?