This is a very interesting observation! In one of my previous posts I described the fact that after the first unsuccessful resume and a following soft-reset with Alt+SysReq+B all subsequent resumes will succeed. My guess was that there was something changed in the GPU's hardware registers before or after the first resume. It cannot be any software influence since the software started again. After a cold reset the game starts again. My assumption was that the GPU's hardware register change was volatile.
Maybe the "AMD Driver Auto-detect tool" stores this one time change non- volatile in any kind of configuration storage element within the GPU. Then it behaves the same like you described. Currently I do not know of any dual use of drivers between Linux and Windows, but to have a built- in non-volatile configuration storage supporting the GPU is very likely. Unfortunately I do not have a dual boot machine. I'm running only Linux. So I'll try to create a USB-stick based Windows 10 to verify your experience. It will take some time. Again, very interesting ... -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kwin in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1849084/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
