I don't even know if I can answer that. As Debian's firmware even in sid is ancient I'm using the ones from
kernel.org, so the old firmware can't really be the issue like the gitlab entry suggests. But my issue always was that it only happened when I least expected it. It never was reproducible by no means. So with the last few firmware updates, the situation probably has gotten better, but I can't tell for sure if the issue is fully fixed. The last logs I saved are from May, but for sure this also has happened afterwards. Question is if it happened after installing the firmware files from the June drop. To be honest, I just can't really tell. It only happened quite regularly with like the March or April firmware, it has gotten much better since. But I'd wait another month or two to make sure it's actually gone.