[oS-en] Machine doesn't hibernate.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, (same new laptop, Lenovo L14 Gen3, new Leap 15.4 install) I do "systemctl hibernate" as root, and machine recovers instantly. It just flickers the screen to black for an instant, then prompts for user password (XFCE). Tried also Gnome. Mar 29 20:47:06 Laicolasse dbus-daemon[1664]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=3705 comm="/usr/bin/wireplumber ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1662 comm="/usr/lib/bluetooth/bluetoothd ") Mar 29 20:47:06 Laicolasse dbus-daemon[1664]: [system] Rejected send message, 0 matched rules; type="error", sender=":1.80" (uid=1000 pid=3705 comm="/usr/bin/wireplumber ") interface="(unset)" member="(unset)" error name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0" destination=":1.2" (uid=0 pid=1662 comm="/usr/lib/bluetooth/bluetoothd ") Mar 29 20:47:06 Laicolasse systemd-sleep[4303]: INFO: Done. Mar 29 20:47:06 Laicolasse systemd[1]: systemd-hibernate.service: Deactivated successfully. Mar 29 20:47:06 Laicolasse systemd[1]: Finished Hibernate. Mar 29 20:47:06 Laicolasse systemd[1]: Reached target System Hibernation. Mar 29 20:47:06 Laicolasse systemd[1]: Stopped target Sleep. Mar 29 20:47:06 Laicolasse systemd-logind[1718]: Operation 'sleep' finished. Mar 29 20:47:06 Laicolasse systemd[1]: Stopped target System Hibernation. Mar 29 20:47:06 Laicolasse ModemManager[1799]: <info> [sleep-monitor] system is resuming Mar 29 20:47:06 Laicolasse NetworkManager[1806]: <info> [1680115626.2953] manager: sleep: wake requested (sleeping: yes enabled: yes) Mar 29 20:47:06 Laicolasse NetworkManager[1806]: <info> [1680115626.2954] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Mar 29 20:47:06 Laicolasse kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) Mar 29 20:47:06 Laicolasse kernel: Bluetooth: hci0: Device setup in 119038 usecs It says there "wake requested". By whom? I did not touch any key. Ideas? journal: <https://paste.opensuse.org/pastes/62e56c840f4a> Machine does suspend to ram, both using "systemctl suspend" or closing the lid. In BIOS config there is an option that says: Sleep State: Windows and Linux vs Linux S3 hibernation I left at default, the first option. Maybe I can try the second option. Trying [...] Power led flashes fast for some seconds, then stays on constantly. The red led on the back stays red. The screen stays black. I wait. I think nothing happens. Machine doesn't react to ping, nor keyboard. I have to press and hold the power button for 4 seconds, then press for power up and fresh full boot. Ideas? I don't have log for previous boot, journal was not persistent. Changing that :-( Behaviour for sleep has changed. Now to wake up from suspend to ram I have to press the power on button, the keyboard is ignored. Oh, at some moment the Caps Lock led became permanently "on" now. Maybe "init 1" did that? Or coming back from sleep? It seems I have to reboot to try to hibernate and have some log, but too many problems to keep using this "Linux S3" mode. Will revert after testing once more. Hibernating... Crashing Changing bios booting... <https://paste.opensuse.org/pastes/46f774d01960> last lines: Mar 29 21:30:21 Laicolasse systemd-sleep[5061]: Entering sleep state 'hibernate'... Mar 29 21:30:21 Laicolasse kernel: PM: hibernation: hibernation entry - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCSVlxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVyh8AnA4KLKy7iwOae0npsrXv 0WRYVZ0+AJ0cm9Vvs+wt9WTzL60EV+GjI1bWCQ== =Ym2v -----END PGP SIGNATURE-----
On 3/29/23 14:46, Carlos E. R. wrote:
ModemManager[1799]: <info> [sleep-monitor] system is resuming
Looks like this is the first indication that a wakeup has occured. The next line is Network Manager. Why we have ModemManager running has always been a curiosity, and I've seen reasoning, but I don't recall the details. Were it me, I'd kill it and try putting the laptop to sleep again and see if it stays that way. I doubt you have a modem anyway. (what I do recall is it is used by the likes of gphoto2, etc.. for some serial communications of USB. That is a vague recollection though) -- David C. Rankin, J.D.,P.E.
On 2023-03-30 03:15, David C. Rankin wrote:
On 3/29/23 14:46, Carlos E. R. wrote:
ModemManager[1799]: <info> [sleep-monitor] system is resuming
Looks like this is the first indication that a wakeup has occured. The next line is Network Manager. Why we have ModemManager running has always been a curiosity, and I've seen reasoning, but I don't recall the details.
I don't know if ModemManager is causing the wake up, or detecting the wake up.
Were it me, I'd kill it and try putting the laptop to sleep again and see if it stays that way. I doubt you have a modem anyway.
Let's see... Nope, didn't work.
(what I do recall is it is used by the likes of gphoto2, etc.. for some serial communications of USB. That is a vague recollection though)
Huh :-? Ah, maybe those usb things that had two behaviours, and something in the computer triggered a change of mode, then usb detected it as something different. Well, now it is NetworkManager who says waking up.
Mar 30 07:49:34 Laicolasse gdm-Xorg-:0[10939]: (II) AMDGPU(0): Modeline "1920x1080"x0.0 160.63 1920 1936 1952 2180 1080 1083 1097 1228 -hsync -vsync (73.7 kHz > Mar 30 07:49:34 Laicolasse systemd-sleep[18725]: INFO: Done. Mar 30 07:49:34 Laicolasse systemd[1]: systemd-hibernate.service: Deactivated successfully. Mar 30 07:49:34 Laicolasse systemd[1]: Finished Hibernate. Mar 30 07:49:34 Laicolasse systemd[1]: Reached target System Hibernation. Mar 30 07:49:34 Laicolasse systemd[1]: Stopped target Sleep. Mar 30 07:49:34 Laicolasse systemd[1]: Stopped target System Hibernation. Mar 30 07:49:34 Laicolasse systemd-logind[1725]: Operation 'sleep' finished. Mar 30 07:49:34 Laicolasse NetworkManager[1831]: <info> [1680155374.8546] manager: sleep: wake requested (sleeping: yes enabled: yes) Mar 30 07:49:34 Laicolasse NetworkManager[1831]: <info> [1680155374.8547] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-stat> Mar 30 07:49:34 Laicolasse kernel: Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) Mar 30 07:49:34 Laicolasse kernel: Bluetooth: hci0: Device setup in 121088 usecs Mar 30 07:49:34 Laicolasse kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
(this is with kernel 6.2.8-lp154.3 from Kernel:stable:Backports) (I notice that the ssh session, via wlan, now and then stops responding) Before, I suspected wake on line, so I tried disconnected the cable. At the moment, wlan was not working. Now I called hibernate from a ssh session using wlan. On other machines, the ssh would just stop responding and eventually die. Here... :-? But NetworkManager talks about etho, not wlan. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Wed, Mar 29, 2023 at 10:46 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Mar 29 20:47:06 Laicolasse kernel: Wakeup pending. Abort CPU freeze. Some device tried to wake up at the wrong moment. You could try low hanging fruits like disabling wakeup sources in /etc/acpi/wakep (https://wiki.archlinux.org/title/Power_management/Wakeup_triggers). But there are a lot of reports of similar symptoms on AMD systems, just google for this message. Debugging suspend issues is more art than science. This usually needs second system to capture (debug) console output to start with.
On 2023-03-30 08:46, Andrei Borzenkov wrote:
On Wed, Mar 29, 2023 at 10:46 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
Mar 29 20:47:06 Laicolasse kernel: Wakeup pending. Abort CPU freeze.
Ah, didn't see that one. Would be nice if the kernel reported which. With updated kernel from "Kernel:stable:Backports": Mar 30 10:13:22 Laicolasse kernel: ACPI: PM: Preparing to enter system sleep state S4 Mar 30 10:13:22 Laicolasse kernel: ACPI: EC: event blocked Mar 30 10:13:22 Laicolasse kernel: ACPI: EC: EC stopped Mar 30 10:13:22 Laicolasse kernel: ACPI: PM: Saving platform NVS memory Mar 30 10:13:22 Laicolasse kernel: Disabling non-boot CPUs ... Mar 30 10:13:22 Laicolasse kernel: Wakeup pending. Abort CPU freeze Mar 30 10:13:22 Laicolasse kernel: Non-boot CPUs are not disabled Mar 30 10:13:22 Laicolasse kernel: ACPI: EC: EC started Mar 30 10:13:22 Laicolasse kernel: ACPI: PM: Waking up from system sleep state S4 Mar 30 10:13:22 Laicolasse kernel: ACPI: EC: interrupt unblocked Mar 30 10:13:22 Laicolasse kernel: ACPI: EC: event unblocked Mar 30 10:13:22 Laicolasse kernel: pci 0000:00:00.2: can't derive routing for PCI INT A Mar 30 10:13:22 Laicolasse kernel: pci 0000:00:00.2: PCI INT A: no GSI
Some device tried to wake up at the wrong moment. You could try low hanging fruits like disabling wakeup sources in /etc/acpi/wakep
Ok. Oh :-( Laicolasse:~ # ls /etc/acpi/* ls: cannot access '/etc/acpi/*': No such file or directory Laicolasse:~ #
(https://wiki.archlinux.org/title/Power_management/Wakeup_triggers).
Ok, will read.
But there are a lot of reports of similar symptoms on AMD systems, just google for this message.
Ok.
Debugging suspend issues is more art than science. This usually needs second system to capture (debug) console output to start with.
Yes, I have done that, with a true RS232. Ethernet can do it, with some more limits. however, in this case I do have the log file, so maybe I don't need doing that? :-? Thanks for the pointers. Thinking aloud: Laicolasse:~ # cat /proc/acpi/wakeup Device S-state Status Sysfs node GPP4 S0 *enabled pci:0000:00:02.3 GPP7 S0 *disabled GP17 S0 *enabled pci:0000:00:08.1 LID S4 *enabled platform:PNP0C0D:00 SLPB S3 *enabled platform:PNP0C0E:00 Laicolasse:~ # Ok, LID I know what it is. What are the others? Laicolasse:~ # cat /sys/module/acpi/parameters/ec_no_wakeup N Laicolasse:~ # Laicolasse:~ # cat /sys/bus/usb/devices/usb?/power/wakeup disabled disabled disabled disabled disabled Laicolasse:~ # Hum. Must look in bios and disable wake on LAN. Laicolasse:~ # ls /sys/class/wakeup | wc -l 60 Laicolasse:~ # Laicolasse:~ # ls /sys/class/wakeup/*/device/physical_node/power/wakeup | wc -l 20 Laicolasse:~ # Laicolasse:~ # ls /sys/class/wakeup/*/device/power/wakeup | wc -l 15 Laicolasse:~ # Laicolasse:~ # ls /sys/class/wakeup/*/device/path | wc -l 48 Laicolasse:~ # Google: "Wakeup pending. Abort CPU freeze" "Lenovo" "L15" nothing found. "Wakeup pending. Abort CPU freeze" "Lenovo" There are some. [...] Nothing seems to be it. "Wakeup pending. Abort CPU freeze" Reading... -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 21:46, Carlos E. R. wrote:
Hi,
(same new laptop, Lenovo L14 Gen3, new Leap 15.4 install)
I do "systemctl hibernate" as root, and machine recovers instantly. It just flickers the screen to black for an instant, then prompts for user password (XFCE). Tried also Gnome.
...
It says there "wake requested". By whom? I did not touch any key.
Ideas?
journal: <https://paste.opensuse.org/pastes/62e56c840f4a>
Machine does suspend to ram, both using "systemctl suspend" or closing the lid.
In BIOS config there is an option that says:
Sleep State: Windows and Linux vs Linux S3 hibernation
I left at default, the first option. Maybe I can try the second option.
Trying [...]
Power led flashes fast for some seconds, then stays on constantly. The red led on the back stays red. The screen stays black. I wait. I think nothing happens.
Machine doesn't react to ping, nor keyboard. I have to press and hold the power button for 4 seconds, then press for power up and fresh full boot.
Ideas?
I don't have log for previous boot, journal was not persistent. Changing that :-(
Behaviour for sleep has changed. Now to wake up from suspend to ram I have to press the power on button, the keyboard is ignored.
Oh, at some moment the Caps Lock led became permanently "on" now. Maybe "init 1" did that? Or coming back from sleep?
It seems I have to reboot to try to hibernate and have some log, but too many problems to keep using this "Linux S3" mode. Will revert after testing once more.
Hibernating... Crashing Changing bios booting...
<https://paste.opensuse.org/pastes/46f774d01960>
last lines:
Mar 29 21:30:21 Laicolasse systemd-sleep[5061]: Entering sleep state 'hibernate'... Mar 29 21:30:21 Laicolasse kernel: PM: hibernation: hibernation entry
There is known issue, reported here: Bug 1207948 - Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic https://bugzilla.suse.com/show_bug.cgi?id=1207948 It is not exactly what I see, though, mine enters in panic at the end of hibernation, way before trying resume, which I can't try. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On Fri, Mar 31, 2023 at 10:57 AM Carlos E. R. <robin.listas@telefonica.net> wrote: ...
(same new laptop, Lenovo L14 Gen3, new Leap 15.4 install) ...
There is known issue, reported here:
Bug 1207948 - Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
How is a bug for T14s relevant for L14? You have already been told in another bug report that you have a different wireless chip.
On 2023-03-31 11:15, Andrei Borzenkov wrote:
On Fri, Mar 31, 2023 at 10:57 AM Carlos E. R. <robin.listas@telefonica.net> wrote: ...
(same new laptop, Lenovo L14 Gen3, new Leap 15.4 install) ...
There is known issue, reported here:
Bug 1207948 - Lenovo T14s Gen3 AMD resume from hibernation ends in kernel panic
How is a bug for T14s relevant for L14? You have already been told in another bug report that you have a different wireless chip.
That was later. The message about having a different chip appeared AFTER he told me I was affected by that bug. The same person told me I was affected, and less than an hour later, that I wasn't, that he got confused with a different chip. Please! Don't spank me that fast :-( -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 21:46, Carlos E. R. wrote:
Hi,
(same new laptop, Lenovo L14 Gen3, new Leap 15.4 install)
...
In BIOS config there is an option that says:
Sleep State: Windows and Linux vs Linux S3 hibernation
With kernel 6.2.8 with bios setting "Linux S3 hibernation" hibernation succeeds :-)) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-03-29 21:46, Carlos E. R. wrote:
Hi,
(same new laptop, Lenovo L14 Gen3, new Leap 15.4 install)
I do "systemctl hibernate" as root, and machine recovers instantly. It just flickers the screen to black for an instant, then prompts for user password (XFCE). Tried also Gnome.
...
In BIOS config there is an option that says:
Sleep State: Windows and Linux vs Linux S3 hibernation
I left at default, the first option. Maybe I can try the second option.
Trying [...]
Power led flashes fast for some seconds, then stays on constantly. The red led on the back stays red. The screen stays black. I wait. I think nothing happens.
Machine doesn't react to ping, nor keyboard. I have to press and hold the power button for 4 seconds, then press for power up and fresh full boot.
Ideas?
Bug 1210029 Can't hibernate laptop Lenovo L14 Gen 3 AMD Summary. Machine can hibernate if in UEFI config is set "Sleep State: Linux S3 hibernation", and uses the kernel from Leap 15.5. Initially it appeared that kernel 6.2.8 from "Kernel:stable:Backports" was needed. The issue was confusing because YaST thought that the swap space (25 Gigs) was too small having 32 gigs of ram, and did not insert the "resume=..." entry on the kernel load line. So the machine did hibernate fine, but could never recover but did a fresh boot instead all the time, when using the dedicated Beta (Leap 15.5) test install. Once the entry was written manually the machine booted fine. 15.4 also hibernates fine using the (patched) kernel from 15.5. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin