2 months later and I’m still suffering from the same problem 
.
@litemotiv you wrote here:
For that second issue a kernel driver update is needed that will likely land in kernel 6.11. This particular bug is a regression and does not occur in kernel 6.9, if you have an older kernel still installed you can boot into that to avoid it. Kernel 6.10 is affected, so for a more definitive fix you would have to wait until kernel 6.11.
I’m currently using the kernel 6.11.4-201.fc40.x86_64 and I still have the bug. Do you have any idea why? How has the situation evolved? 