[support] sleep/suspend/hibernate don't
This PC is my brother's, originally installed 24 months ago by myself with 15.1. He claims sleep/hibernate used to work before the upgrade to 15.2, and now 15.3. He wants hibernate/sleep to work again. So far, I haven't found the secret to success. # inxi -Fxzy System: Kernel: 5.3.18-lp152.41-default x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: KDE Plasma 5.18.6 Distro: openSUSE Leap 15.3 Machine: Type: Desktop Mobo: ASRock model: N68C-GS FX serial: N/A BIOS: American Megatrends v: P1.40 date: 10/31/2012 CPU: Info: 6-Core model: AMD Phenom II X6 1055T bits: 64 type: MCP arch: K10 rev: 0 cache: L2: 3 MiB flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 33754 Speed: 803 MHz min/max: 800/2800 MHz boost: enabled Core speeds (MHz): 1: 803 2: 1470 3: 804 4: 1772 5: 1667 6: 1675 Graphics: Device-1: NVIDIA C61 [GeForce 7025 / nForce 630a] vendor: ASRock driver: nouveau v: kernel bus-ID: 00:0d.0 Display: x11 server: X.Org 1.20.3 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1680x1050~60Hz OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 20.2.4 direct render: Yes Audio: Device-1: NVIDIA MCP61 High Definition Audio vendor: ASRock driver: snd_hda_intel v: kernel bus-ID: 00:05.0 Sound Server-1: ALSA v: k5.3.18-lp152.41-default running: yes Sound Server-2: PulseAudio v: 14.2-rebootstrapped running: no Sound Server-3: PipeWire v: 0.3.24 running: no Network: Device-1: NVIDIA MCP61 Ethernet vendor: ASRock 939NF6G-VSTA Board type: network bridge driver: forcedeth v: kernel port: e080 bus-ID: 00:07.0 IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter> Drives: Local Storage: total: 111.79 GiB used: 204.73 GiB (183.1%) ID-1: /dev/sda vendor: A-Data model: SU650 size: 111.79 GiB Partition: ID-1: / size: 17.18 GiB used: 9.41 GiB (54.8%) fs: ext4 dev: /dev/sda3 ID-2: /home size: 51.45 GiB used: 14.53 GiB (28.2%) fs: ext4 dev: /dev/sda5 Swap: ID-1: swap-1 type: partition size: 4 GiB used: 0 KiB (0.0%) dev: /dev/sda2 Sensors: System Temperatures: cpu: 33.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 191 Uptime: 1h 16m Memory: 3.59 GiB used: 816 MiB (22.2%) Init: systemd runlevel: 5 Compilers: gcc: N/A Packages: 2580 Shell: Bash v: 4.4.23 inxi: 3.3.04 The BIOS doesn't have any setting labeled S1 or S3, but the ACPI setting it does have that Google says equates to S3 is enabled. To generate the following, I first booted to multi-user, logged in as root, then issued systemctl start systemd-suspend. The response was no different that I could tell than by selecting sleep or hibernate from Plasma's Power/Session menu. # dmesg https://paste.opensuse.org/99478212 # journalctl -b https://paste.opensuse.org/10906426 My search fu is fubar again. I was sure there was recent discussion about this subject either on a mailing list or on the forums, but I'm not finding it. Is there anything in the two logs to explain why an attempt to suspend or hibernate results either in: 1-several seconds of black screen without a poweroff, then all coming back as if resume had been intentionally triggered, or 2-several seconds of black screen without a poweroff, then all coming back as if screenlocker had been triggered, or 3-reboot Does anyone know of some bug that needs a workaround, or a fix or config change required? Is this supposed to be controllable via YaST? The only place I see power control settings are in Plasma's systemsettings, where screen energy saving and suspend session are enabled, but the other three checkboxes (including button events) not. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 02/07/2021 06.46, Felix Miata wrote:
This PC is my brother's, originally installed 24 months ago by myself with 15.1. He claims sleep/hibernate used to work before the upgrade to 15.2, and now 15.3. He wants hibernate/sleep to work again. So far, I haven't found the secret to success.
...
To generate the following, I first booted to multi-user, logged in as root, then issued systemctl start systemd-suspend. The response was no different that I could tell than by selecting sleep or hibernate from Plasma's Power/Session menu.
The command is "systemctl hibernate". I have no idea if the one you use is equivalent or not.
Contains no information on "hibernate".
# journalctl -b https://paste.opensuse.org/10906426
Contains no hibernation attempt. The only thing I see is that the kernel checks to see if there is an hibernation image stored, and fails, there is no such image. Jul 01 23:11:23 rok68 systemd[1]: Starting Resume from hibernation using device /dev/disk/by-label/P02swapper... Jul 01 23:11:23 rok68 systemd-hibernate-resume[337]: Could not resume from '/dev/disk/by-label/P02swapper' (8:2). Jul 01 23:11:23 rok68 kernel: PM: Image not found (code -22) Jul 01 23:11:23 rok68 systemd[1]: systemd-hibernate-resume@dev-disk-by\x2dlabel-P02swapper.service: Succeeded. Jul 01 23:11:23 rok68 systemd[1]: Finished Resume from hibernation using device /dev/disk/by-label/P02swapper. Jul 01 23:11:23 rok68 systemd[1]: Reached target Local File Systems (Pre).
My search fu is fubar again. I was sure there was recent discussion about this subject either on a mailing list or on the forums, but I'm not finding it.
Is there anything in the two logs to explain why an attempt to suspend or hibernate results either in:
1-several seconds of black screen without a poweroff, then all coming back as if resume had been intentionally triggered, or 2-several seconds of black screen without a poweroff, then all coming back as if screenlocker had been triggered, or 3-reboot
There is no hint that such a thing ever happened. Start the machine in level 3, then login as root and issue "systemctl hibernate". If it fails, extract the logs just at that instant. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E. R. composed on 2021-07-02 10:12 (UTC+0200):
Start the machine in level 3, then login as root and issue "systemctl hibernate".
If it fails, extract the logs just at that instant.
The command triggered a full reboot after blanking the screen. https://paste.opensuse.org/36730585 https://paste.opensuse.org/37512829 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 02/07/2021 20.22, Felix Miata wrote:
Carlos E. R. composed on 2021-07-02 10:12 (UTC+0200):
Start the machine in level 3, then login as root and issue "systemctl hibernate".
If it fails, extract the logs just at that instant.
The command triggered a full reboot after blanking the screen.
It would help if you say at what exact hour:minute:second you issued the command.
There is a warning about '/etc/init.d/xfs'. What is that? Ah, font server. Why has it not been migrated to systemd? Not related, anyway. It seems the hibernation command is given at "14:18:03". It seems to try hibernation, then stops and restores instantly at 14:18:49. No idea why.
It appears a successful hibernation followed by successful restore. I have no idea what is going on. Did you report in Bugzilla? I can tell you the same they told me once: Could you try hibernating directly via kernel interface: echo disk > /sys/power/state instead of systemd? If the problem is seen there, it's a bit easier to see what happening. The next step would be testing as described in Documentation/power/basic-pm-debugging.rst -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Carlos E.R. composed on 2021-07-02 23:39 (UTC+0200):
It appears a successful hibernation followed by successful restore.
I have no idea what is going on. Did you report in Bugzilla?
Not yet.
I can tell you the same they told me once:
That looks like in https://bugzilla.opensuse.org/show_bug.cgi?id=1182346
Could you try hibernating directly via kernel interface: echo disk > /sys/power/state instead of systemd? If the problem is seen there, it's a bit easier to see what happening.
It didn't trigger.
The next step would be testing as described in Documentation/power/basic-pm-debugging.rst
I struck out trying to locate that document. Then I asked on a forum: <https://forums.opensuse.org/showthread.php/556448-sleep-suspend-amp-hibernate-don-t-exactly> By creating /etc/systemd/sleep.conf containing only [Sleep] HibernateMode=shutdown I am able to manually suspend or hibernate, but none of the power saving functions controlled via systemsettings5 in Plasma have any effect. I find it seriously disappointing that I can't find anything about power saving options in YaST. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 04/07/2021 00.54, Felix Miata wrote:
Carlos E.R. composed on 2021-07-02 23:39 (UTC+0200):
It appears a successful hibernation followed by successful restore.
I have no idea what is going on. Did you report in Bugzilla?
Not yet.
I can tell you the same they told me once:
That looks like in https://bugzilla.opensuse.org/show_bug.cgi?id=1182346
Could you try hibernating directly via kernel interface: echo disk > /sys/power/state instead of systemd? If the problem is seen there, it's a bit easier to see what happening.
It didn't trigger.
mean it did not hibernate? Put that in the bugzilla.
The next step would be testing as described in Documentation/power/basic-pm-debugging.rst
I struck out trying to locate that document.
You need kernel sources installed. full path in my machine: /usr/src/linux-5.3.18-lp152.78/Documentation/power/basic-pm-debugging.rst I will attach and email it to you, off-list.
Then I asked on a forum: <https://forums.opensuse.org/showthread.php/556448-sleep-suspend-amp-hibernate-don-t-exactly>
By creating /etc/systemd/sleep.conf containing only
[Sleep] HibernateMode=shutdown
I am able to manually suspend or hibernate, but none of the power saving functions controlled via systemsettings5 in Plasma have any effect.
I never hibernate that way, in my case using XFCE. I always hibernate via command as root. Look, yesterday I closed the lid in my laptop. It went black, but did not suspend. I did not notice. When I came back to the room, the machine was alive, and a prompt was asking permission to hibernate, please give root password - because something or other was active. This bug has been active for many years. So, lesson: always suspend or hibernate as root, via command line.
I find it seriously disappointing that I can't find anything about power saving options in YaST.
They never were, AFAIR. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
It seems that the kernel doesn't find the image. You could create a new file called, e.g., "99-fix-resume.conf" in /etc/dracut.conf.d>, which should contain add_dracutmodules+="resume" followed by 'sudo dracut -fv', then reboot. Hope it helps. Regards, Frank
I took the SSD out of my brother's, put it in one of my own, and found hibernation working as he wants it. So I put it back in his, and it's working exactly the same as it did in mine. Weird. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 08/07/2021 20.11, Felix Miata wrote:
I took the SSD out of my brother's, put it in one of my own, and found hibernation working as he wants it. So I put it back in his, and it's working exactly the same as it did in mine. Weird.
So, your brother's machine is working correctly now with its own hard disk, and hibernating ok? Maybe BIOS was stuck on some funky mode, maybe hard disk connections were not working right. Who knows. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.1 x86_64 (Minas Tirith))
participants (4)
-
Carlos E. R. -
Carlos E.R. -
Felix Miata -
Frank Krüger