You are not logged in.
Just this morning, my laptop overheated in my backpack, and after 20 minutes of being idle, it's already overheating and it gone down from 90% to 10%.
On kernel 6.6.1-arch1-1 this did not happen.
I tried using suspend, but I ended up masking the suspend targets, because it would freeze my system, with the fans on but "suspended", no reaction to keyboard input.
$ systemctl --version
systemd 254 (254.6-2-arch)
+PAM +AUDIT -SELINUX -APPARMOR -IMA +SMACK +SECCOMP +GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP -SYSVINIT default-hierarchy=unifieddmesg does not show anything interesting...
Offline
So you're hibernating it since resuming from suspend doesn't seem to work. Did you merely close the lid to send it to hibernation, or did you run systemctl hibernate? Has this happened more than once? If not, what was your approximate uptime prior to sending it to hibernation? If you simply closed the lid, I'd try to find out if your system does hybrid-sleep, or suspend then hibernate (these are different systemctl commands). Or is it just hibernate?
I'd try to reproduce it. If you're not able to reproduce the problem, it may have been some transient state of that boot. I'd look at the systemd journal for that boot (journalctl --list-boots, then journalctl --boot <boot number>), see if there are any clues (it may not have shown in dmesg, but the journal may tell otherwise).
If you're able to reproduce it, try downgrading the kernel to 6.6.1, see if the problem goes away. If it does, then you've likely identified a regression in 6.6.2. I'd check git.kernel.org, see if any commits for any of the code for your specific hardware has been updated (may need to look at lspci -k to see what kernel modules you have loaded). If you have any out-of-tree kernel modules (like nvidia, or anything you need to build with DKMS), try unloading them and see if you can reproduce the problem without them. Try to narrow it down to which module is causing it.
Offline
i understand, it's looping on suspend and it heats up the CPU...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission denied
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Suspending...
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Unit suspend.target is masked, refusing operation.
Nov 24 09:24:20 freedom-with-linux systemd-logind[393]: Failed to execute suspend operation: Permission deniedHow can i stop it from trying to suspend?
Hibernate is also masked by the way.
Last edited by SaltyRhino95857 (2023-11-24 08:03:00)
Offline
That just indicates that the suspend.target is masked, and your laptop keeps looping over that. If hibernation is masked as well, then your laptop isn't going to go into a low power mode when you want to travel with it.
So I'd figure out which operation (suspend, hibernate, hybrid-sleep, suspend-then-hibernate) works best for your laptop. Start with Laptop Power Management. I'd see if you can run the relevant sudo systemctl states, see which one works best for your hardware without too much trouble. You'd have to unmask the relevant targets.
Then tie that operation to what happens when you close the lid. But if some suspend/hibernate state was working prior to installing kernel 6.6.2, you may want to try and identify which module or kernel commit introduced the regression if you can.
Offline