I am reopening the bug report, as the bug came back in kernel 5.11.12 and is still happening with 5.11.15. It is still alright if I stay on kernel 5.11.6.