[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-09-11 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #10 from sk.griffi...@gmail.com --- Submitted to https://gitlab.freedesktop.org/drm/amd/-/issues/2845 -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-09-10 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=473734 Zamundaaa changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-09-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #8 from sk.griffi...@gmail.com --- (In reply to Zamundaaa from comment #7) > Please put `KWIN_DRM_NO_AMS=1` into /etc/environment, reboot and then check > if your workaround starts working again with that the workaround to switch tty to res

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-09-06 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #7 from Zamundaaa --- Sorry, it's been a busy week and I haven't been able to go through all my emails yet. The most suspicious things in your log are > [35707.959388] [drm] Fence fallback timer expired on ring sdma0 a bunch of times (which

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-09-06 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #6 from sk.griffi...@gmail.com --- Should I provide any further info? Had this issue again and lost data again. This is making it very difficult for me to use kde for any serious endeavour. If nothing, is there some way to remove flickering h

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-08-31 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #5 from sk.griffi...@gmail.com --- Created attachment 161308 --> https://bugs.kde.org/attachment.cgi?id=161308&action=edit dmesg log with bug reproduced Had this bug today after hibernating today -- You are receiving this mail because: Y

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-08-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #4 from sk.griffi...@gmail.com --- Created attachment 161180 --> https://bugs.kde.org/attachment.cgi?id=161180&action=edit dmsg log with bug NOT Reproduced I tried a couple of times but couldn't reproduce the bug. I am attaching dmsg log j

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-08-25 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #3 from Zamundaaa --- Yes, that is correct. > On running `modinfo -p drm`, I get a bunch of codes but 0x1FF is not one of > them. What does this code do? 0x1FF is just the combination of all the flags, with all bits set. The goal is to get

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-08-25 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=473734 --- Comment #2 from sk.griffi...@gmail.com --- (In reply to Zamundaaa from comment #1) > Please enable drm debug logging with > > echo 0x1FF | sudo tee /sys/module/drm/parameters/debug > start writing the log with > > sudo dmesg -w > dmesg.log > then rep

[kwin] [Bug 473734] Screen not restored after awakening from hibernate

2023-08-25 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=473734 Zamundaaa changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC|