Thou shalt not slæpan [sleep]

quakerdoomer

quakerdoomer

Sleep broken for anyone else?

One of my laptops is an old Dell system.
Received the April 2026 patches and now on FreeBSD 15 p5
Big mistake. Everything was working fine earlier.
RAM consumption has shot up and even 480p videos now crawl for the first few minutes.

This all is bearable BUT now the laptop refuses to sleep.
If I use the sleep option in KDE it does not go to sleep instead gets stuck either at 'cannot get token' kscreenlogin [ paraphrasing here ] or at

kscreenlocker_greet with "pam_sm_authenticate: pam_get_authtok(): Conversation failure"
proceeded by
"acpi0: suspend request time out."
AIGLX: Suspending AIGLX clients for VT switch

So something is definitely timing out. Not sure if it is KDE/plasma not playing well with the upgrade. Does this have something to do with drm-kmod?
Whatever it is, these days not enough testing is done and updates are pushed hurriedly.

zzz sometimes works better, but not always. Not sure why. I. Of course have to use it with slock, otherwise it does not lock the screen and just sleeps.
I have checked the rc.suspend script and played around with the acpi-config options. No luck.

To be clear this was working up until FreeBSD 15 p4. p5 broke stuff!

Anyone else having a problem with putting their laptops to sleep?
 
quakerdoomer said:
Received the April 2026 patches and now on FreeBSD 15 p5
Click to expand...
There were no OS patches in April.

quakerdoomer said:
To be clear this was working up until FreeBSD 15 p4. p5 broke stuff!
Click to expand...
You are definitely confusing the OS patches with the newly released 2016Q2 quarterly package branch. One is not related to the other.

Please understand there's a difference between the version of the OS (in your case 15.0-RELEASE-p5) and third-party software, i.e. ports and packages. Versions of third-party software have no relation to the version of the OS. As is common on most Linux distributions. This relationship never existed on FreeBSD. There is only one ports tree. All (supported) versions of FreeBSD use the one and same ports tree, thus have the same third-party software versions available to them.
 
Yes these were just 2016Q2 quarterly package, not security patches, agreed.

So, are you saying this Q2 update is not the reason sleep isn't working anymore? I fail to see how saving the state of RAM to disk and resumingback is a third party feature.
 
Understood, if these 4 are the only updates that led me to p5 then it is definitely something third party because the updates were well above 3GB. Thank you.
 
Have you looked at drsnx60 's suggestion? Apparently updating the seconds of the clock app sucks up a lot of CPU cycles. That might be the reason why everything else feels sluggish and the system refuses to sleep.
 
SirDice said:
Have you looked at drsnx60 's suggestion? Apparently updating the seconds of the clock app sucks up a lot of CPU cycles. That might be the reason why everything else feels sluggish and the system refuses to sleep.
Click to expand...
after updating to Plasma/KDE 6.6.2 / 6.6.3 the binary 'Plasmashell' occupies one thread on your CPU to 100 % for about 10 minutes after the startup of plasma/KDE. If you have an old DUAL CORE CPU with only four threads this would manifest itself in the manner you describe.
it's a bug and the workaround is to configure the digital clock in the toolbar to "NEVER SHOW Seconds ":
 
You must log in or register to reply here.
Back
Top