You are not logged in.
Pages: 1
Short Description
after running
sudo systemctl hibrenate
Laptop goes of properly, but when pressing the power button to wake up, laptop freezes and a reboot is needed.
Full info
My system:
> uname -r
6.7.6-arch1-1
and
> sudo dmidecode --type bios
Getting SMBIOS data from sysfs.
SMBIOS 3.2.0 present.
Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
Vendor: LENOVO
Version: DPCN39WW
Release Date: 01/15/2020
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 10 MB
Characteristics:
PCI is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for NEC 9800 1.2 MB is supported (int 13h)
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
8042 keyboard services are supported (int 9h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.39
Firmware Revision: 1.39
Handle 0x0021, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 8
en|US|iso8859-1,0
fr|FR|iso8859-1,0
zh|TW|unicode,0
ja|JP|unicode,0
it|IT|iso8859-1,0
es|ES|iso8859-1,0
de|DE|iso8859-1,0
pt|PT|iso8859-1,0
Currently Installed Language: en|US|iso8859-1,0
Looking at sleep support
> cat /sys/power/mem_sleep
[s2idle]
Which means I don't have support for deep mode. So I went for hibernate (is this a mistake?). Following Power management/Suspend and hibernate guide I set the following:
in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 resume=UUID=5d7df56c-2a6b-4c05-bdc4-a3545fe33010 quiet"
and in /etc/mkinitcpio.conf
HOOKS=(base udev autodetect modconf kms keyboard keymap consolefont block filesystems resume fsck)
where:
> lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:0 0 953.9G 0 disk
├─nvme0n1p1 259:1 0 9M 0 part
├─nvme0n1p2 259:2 0 500M 0 part /boot
├─nvme0n1p3 259:3 0 3.9G 0 part [SWAP]
├─nvme0n1p4 259:4 0 48.8G 0 part /
└─nvme0n1p5 259:5 0 900.6G 0 part /home
and
>ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 15 Feb 27 12:18 09ad7a9c-0794-46f9-a6bf-77999e904b9a -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 15 Feb 27 12:18 5023a35b-5627-49fe-aa2c-1cc1e98c3480 -> ../../nvme0n1p5
lrwxrwxrwx 1 root root 15 Feb 27 12:18 5d7df56c-2a6b-4c05-bdc4-a3545fe33010 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Feb 27 12:18 896a05e0-90cb-45aa-8f37-98a06135778a -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Feb 27 12:18 8EE9-726E -> ../../nvme0n1p2
Going into hibernation with
systemctl hibernate
Shuts down the laptop but when trying to resume witht he power button the laptop freezes.
Looking at logs
Feb 27 12:16:28 laptop systemd-logind[418]: The system will hibernate now!
Feb 27 12:16:28 laptop sudo[31143]: pam_unix(sudo:session): session closed for user root
Feb 27 12:16:28 laptop gnome-shell[1062]: ../glib/gobject/gsignal.c:2777: instance '0x565e30936dd0' has no handler with id '1'
Feb 27 12:16:28 laptop gnome-shell[1062]: ../glib/gobject/gsignal.c:2777: instance '0x565e30936dd0' has no handler with id '2'
Feb 27 12:16:28 laptop gnome-shell[1062]: Source ID 1515 was not found when attempting to remove it
Feb 27 12:16:28 laptop gnome-shell[1062]: Source ID 48358 was not found when attempting to remove it
Feb 27 12:16:28 laptop gnome-shell[1062]: Source ID 2782 was not found when attempting to remove it
Feb 27 12:16:28 laptop rtkit-daemon[838]: Successfully made thread 1092 of process 1062 owned by '1000' high priority at nice level 0.
Feb 27 12:16:28 laptop rtkit-daemon[838]: Supervising 9 threads of 6 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 8 threads of 5 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 8 threads of 5 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Successfully made thread 1092 of process 1062 owned by '1000' RT at priority 20.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 9 threads of 6 processes of 1 users.
Feb 27 12:16:29 laptop gnome-shell[1062]: Object St.Icon (0x565e30939910), has been already disposed — impossible to set any property on it. This might be caused by the object having been destroyed from C code using something such >
== Stack trace for context 0x565e2e9d0240 ==
#0 565e2ea97168 i file:///home/anastasia/.local/share/gnome-shell/extensions/espresso@coadmunkee.github.com/extension.js:518 (35cf2888fa10 @ 433)
#1 7ffc20b89480 b resource:///org/gnome/gjs/modules/core/_signals.js:130 (32305be968d0 @ 126)
#2 7ffc20b89560 b resource:///org/gnome/gjs/modules/core/_signals.js:119 (32305be967e0 @ 286)
#3 7ffc20b89640 b resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (32305be8a6a0 @ 39)
#4 565e2ea970d8 i resource:///org/gnome/shell/ui/init.js:21 (32305be70ba0 @ 48)
Feb 27 12:16:29 laptop systemd[1]: Reached target Sleep.
Feb 27 12:16:29 laptop systemd[1]: Starting System Hibernate...
Feb 27 12:16:29 laptop rtkit-daemon[838]: Successfully made thread 1092 of process 1062 owned by '1000' high priority at nice level 0.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 9 threads of 6 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 8 threads of 5 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 8 threads of 5 processes of 1 users.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Successfully made thread 1092 of process 1062 owned by '1000' RT at priority 20.
Feb 27 12:16:29 laptop rtkit-daemon[838]: Supervising 9 threads of 6 processes of 1 users.
Any help, pointers etc will be appreciated :-)
Uptade
It seems as if pressing the power button starts a reboot instead of a resume
Last edited by peace (2024-02-27 11:39:42)
Offline
sudo systemctl hibrenate
Laptop goes of properly
I bet you not
Which means I don't have support for deep mode. So I went for hibernate (is this a mistake?)
They're vastly different things, https://en.wikipedia.org/wiki/ACPI#Power_states
It seems as if pressing the power button starts a reboot instead of a resume
Yesno. The system shuts down, but on the next boot will ideally load the hibernation image into RAM and continue where you left.
Please post the complete journal after trying to wake from hibernation.
sudo journalctl -b | curl -F 'file=@-' 0x0.st
If you cannot boot directly after the hibernation because the system "freezes", check whether you can
1. reach a different
2. reboot w/ a short press on the power button or frenetic usage of ctrl+alt+del
3. use the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (use the kernel parameter to unconditionally enable it because you don't know when the boot "freezes")
Then post the journal of the previous boot (waking fomr hibernation)
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
Offline
Thank you Seth for your response and apologies for my delay
I am nor entirely sure I understand what you meant about the difference between deep sleep an hibernate.
From what I understand deep sleep is a state of the CPU and hibernate is the method to insure the OS resumes in a proper method from that state.
I was referring to this part of the
If your hardware does not advertise the deep sleep status, check first if your UEFI advertises some settings for it, generally under Power or Sleep state or similar wording, with options named Windows 10, Windows and Linux or S3/Modern standby support for S0ix, and Legacy, Linux, Linux S3 or S3 enabled for S3 sleep. Failing that, you can keep using s2idle, consider using hibernation or try to patch the DSDT tables (or find a patched version online).
I understood that if the the CPU doesn't advertise deep sleep then the best way to preserve power is by hibernating
sudo journalctl -b | curl -F 'file=@-' 0x0.st
Here is the second posting that you requested.
I was not 100% sure I understood what you advised so this is what I did:
1. in /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="loglevel=3 resume=UUID=5d7df56c-2a6b-4c05-bdc4-a3545fe33010 quiet sysrq_always_enabled=1"
and of course then run
sudo grub-mkconfig -o /boot/grub/grub.cfg
2. To activate in current seesion I ran
sudo sysctl kernel.sysrq=1
3.ran
sudo systemctl hibernate
4. rebooted by: short pressing power, which resulted in booting into grub and then a system freeze. So then I pressed a long press and restarted the system
5. ran
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st
Offline
I understood that if the the CPU doesn't advertise deep sleep then the best way to preserve power is by hibernating
"the best way to preserve power is by hibernating"
S2idle and S3 do not involve a complete power-off, both consume battery (S2idle typically slightly to much more than S3, depending on your hardware)
S4 powers down the system and on the next boot re-reads the previous state from an on-disk image.
S2 and S3 are technically somewhat similar, certainly compared to S4.
Edit: the second journal ends w/ initiating a hibernation.
The 1st one doesn't any hiberantory steps and neither contains the wakeup from a hibernation.
wrt:
4. rebooted by: short pressing power, which resulted in booting into grub and then a system freeze. So then I pressed a long press and restarted the system
The hibernation should have powered down the system, so the first power press would have powered up.
The plan would then have been to NOT use the power button, but the sysrq to get out of the freeze
Also you're hibernating out of a gnome session, try the behavior from the multi-user.target *only* (2nd link below)
Last edited by seth (2024-02-29 21:33:54)
Offline
So this is what I did:
1. set to boot into non graphical with:
systemctl set-default multi-user.target
2. rebooted into terminal login
3. went into hibernate with
sudo systemctl hibernate
4. Tried to wake the system with Alt+Fn+S and then Alt+b
5. System restarted but got stuck
6. Rebooted the system with a long press of the power button and logged in
7. Here is log from
sudo journalctl -b 0
8. Here is log from
sudo journalctl -b -1
Offline
Is it an Intel processor? Are you using IRST (Intel Rapid Start Technology)?
https://bbs.archlinux.org/viewtopic.php?id=278124
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
6. Rebooted the system with a long press of the power button and logged in
No, /that/ would be the stage to invoke sysrq+reisub
Offline
ewaller Thanks for joining the party. Looking in my BIOS/UEFI I don't see any options for IRST or VMD, so I suppose it's not relevant.
seth Hitting those keys give me nothing. The laptop remains frozen. That is why I hard reboot the laptop.
I did try them before I went to hibernation, just to make sure I am doing it correctly. The laptop rebooted as expected. It's just after going to hibernation that the computer stops responding to anything and needs a hard reboot.
Offline
Remove the quiet parameter and add https://wiki.archlinux.org/title/Genera … l_messages ("debug earlyprintk=vga,keep")
Resume from hibernation and take a picture of the monitor - if there're plenty of red lines flying by, you want to record that on video (eg. using your phone)
Use a tripod, if you dont have a tripod, stack the phone between two books, angling it at the monitor: -\_
(hand-held is likely gonna be unreadable)
Offline
So setting the parameters as you advised did give me a lot more prints, but I don't get any error messages. The laptop goes to hibernate but when I try resume it just gets stuck.
No error messages. Nothing. Just unresponsive.
The only way to get it to do something is hard reboot.
Offline
when I try resume it just gets stuck. No error messages. Nothing
You'll at some point see *somthing*?
Offline
After I do a hard reboot I get normal boot messages. I don't see any errors.
Do you want me to post them?
Offline
Yup, it'll at least tell us where the system halts.
Anything is better than nothing.
Offline
Here is log output of system going into hibernate
Here is log output of system booting (hard boot, since the system is not responsive after going into hibernate)
Offline
The interesting part is when you try to wake up from the hibernation and the system "stalls" - NOT the boot where you initiated and NOT after a hard reboot.
Offline
Pages: 1