Page 1 of 1

KDE freezes after suspend (after update) [Solved-work around]

Posted: Wed Jan 01, 2020 20:02
by denijane
After my previous to last update (currently I'm with linux-sabayon-5.3.11), after waking up from suspend, there are visible freezes of the system. For example, when typing there is often (but not always) a delay on the screen, youtube videos would freeze every now and then, playing games is also not possible due to constant freezes. What's rather weird is that I can see this in Firefox or in Konsole (or say Kwrite), but I do not see it in Chrome. In Chrome youtube runs flawlessly and typing also works as expected. After restarting or logging off, system returns to its normal state. Or after an hour or so it may (or may not) fix itself.
I'm not sure how to debug this, I tried journalctl and I'm posting here what I get as messages. It seems very uninformative. So any ideas how to fix this will be welcome.
I'm double booting with NVIDIA but the freezes happen with and without the NVIDIA on.

Code: Select all

яну 01 21:36:21 sabayon sudo[22270]: pam_unix(sudo:session): session closed for user root
яну 01 21:37:12 sabayon org_kde_powerdevil[27854]: powerdevil: Scheduling inhibition from ":1.4642" "firefox" with cookie 800 and reason "video-playing"
яну 01 21:37:12 sabayon org_kde_powerdevil[27854]: powerdevil: Scheduling inhibition from ":1.4642" "firefox" with cookie 801 and reason "audio-playing"
яну 01 21:37:13 sabayon org_kde_powerdevil[27854]: powerdevil: Releasing inhibition with cookie  801
яну 01 21:37:13 sabayon org_kde_powerdevil[27854]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
яну 01 21:37:13 sabayon org_kde_powerdevil[27854]: powerdevil: Releasing inhibition with cookie  800
яну 01 21:37:13 sabayon org_kde_powerdevil[27854]: powerdevil: It was only scheduled for inhibition but not enforced yet, just discarding it
яну 01 21:37:16 sabayon org_kde_powerdevil[27854]: powerdevil: Enforcing inhibition from ":1.4642" "firefox" with cookie 800 and reason "video-playing"
яну 01 21:37:16 sabayon org_kde_powerdevil[27854]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
яну 01 21:37:16 sabayon org_kde_powerdevil[27854]: powerdevil: Enforcing inhibition from ":1.4642" "firefox" with cookie 801 and reason "audio-playing"
яну 01 21:37:16 sabayon org_kde_powerdevil[27854]: powerdevil: By the time we wanted to enforce the inhibition it was already gone; discarding it
яну 01 21:38:44 sabayon kio_http_cache_cleaner[7147]: QIODevice::skip (QBuffer): WriteOnly device
яну 01 21:38:44 sabayon kio_http_cache_cleaner[7147]: QIODevice::skip (QBuffer): WriteOnly device
яну 01 21:39:38 sabayon krunner[28970]: QCommandLineParser: argument list cannot be empty, it should contain at least the executable name
яну 01 21:39:41 sabayon kdeinit5[22437]: Qt: Session management error: networkIdsList argument is NULL
яну 01 21:39:58 sabayon kio_http_cache_cleaner[7147]: QIODevice::skip (QBuffer): WriteOnly device

Re: KDE freezes after suspend (after update)

Posted: Thu Jan 02, 2020 21:40
by joost
I can't reproduce this right now, but will keep an eye out.

Re: KDE freezes after suspend (after update)

Posted: Sat Jan 04, 2020 18:21
by denijane
Well, I realise this is hard to reproduce and it may as well be a kernel issue, because after wake up, I have to do
$rmmod i2c_hid
$modprobe i2c_hid
to awake the touchpad.
In system monitor I see a lot of irq processes (like irq/131-ELAN120, irq/126-mei_me, irq/123-aerdrv) which now say Nice: FIFO 50 and I haven't noticed that before.
So I guess there is something new about irq handling in the new kernel updates that totally messes up my system. What I completely cannot get is why Chrome is the only thing that doesn't make problems. So weird.

Re: KDE freezes after suspend (after update)

Posted: Tue Jan 07, 2020 10:30
by denijane
Update:
After reading somewhat on how to reset IRQs, it seemed that the easiest way to do it, is to switch between ctrl+alt+f1 and ctrl+alt+f2. That solved all my performance issues. This was suggested https://unix.stackexchange.com/question ... untu-16-04 and it seems to reset the problematic video driver. The touchpad driver I restart manually. I still think this is a problem of the update, but I guess it's easier to mend it than to try to debug it.