-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) <=== ? (Leap 15.4) - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY9euHRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfV+QYAn2BNz8gdjl3RlP3Jxk/F SGdEcBZeAKCKbIbcbQC24bT1DQgYqig/jLEuog== =vWby -----END PGP SIGNATURE-----
On Mon, Jan 30, 2023 at 2:46 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) <===
Something inside the kernel returns EBUSY. If you feel like chasing it down: https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html
On 2023-01-30 13:05, Andrei Borzenkov wrote:
On Mon, Jan 30, 2023 at 2:46 PM Carlos E. R. <> wrote:
Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) <===
Something inside the kernel returns EBUSY. If you feel like chasing it down: https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html
It worked days ago, it failed after a recent kernel update. I opened a bugzilla (1207763). Any idea why it would say "ebusy"? What is busy, why... I have not changed hardware. Only told yast to update... My intention is to revert to a kernel of two updates ago, at least. I may try some of the methods in that document. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <dc2a58d2-afe0-2976-a930-b769b331eef5@Telcontar.valinor> El 2023-01-30 a las 13:16 +0100, Carlos E.R. escribió:
On 2023-01-30 13:05, Andrei Borzenkov wrote:
On Mon, Jan 30, 2023 at 2:46 PM Carlos E. R. <> wrote:
Jan 30 11:30:35 Telcontar kernel: OOM killer enabled. Jan 30 11:30:35 Telcontar kernel: Restarting tasks ... done. Jan 30 11:30:35 Telcontar kernel: PM: hibernation: resume failed (-16) <===
Something inside the kernel returns EBUSY. If you feel like chasing it down: https://www.kernel.org/doc/html/latest/power/basic-pm-debugging.html
I may try some of the methods in that document.
+++··················· Debugging hibernation and suspend 2007 Rafael J. Wysocki <rjw@sisk.pl>, GPL 1. Testing hibernation (aka suspend to disk or STD) To check if hibernation works, you can try to hibernate in the �reboot� mode: # echo reboot > /sys/power/disk # echo disk > /sys/power/state ···················++- This part worked. Telcontar:~ # systemctl start gpm.service Telcontar:~ # echo reboot > /sys/power/disk Telcontar:~ # echo disk > /sys/power/state Telcontar:~ # I am on runlevel 5, but I am not logged in graphical mode, but in tty1. +++··················· and the system should create a hibernation image, reboot, resume and get back to the command prompt where you have started the transition. If that happens, hibernation is most likely to work correctly. Still, you need to repeat the test at least a couple of times in a row for confidence. [This is necessary, because some problems only show up on a second attempt at suspending and resuming the system.] Moreover, hibernating in the �reboot� and �shutdown� modes causes the PM core to skip some platform-related callbacks which on ACPI systems might be necessary to make hibernation work. Thus, if your machine fails to hibernate or resume in the �reboot� mode, you should try the �platform� mode: # echo platform > /sys/power/disk # echo disk > /sys/power/state which is the default and recommended mode of hibernation. ···················++- Telcontar:~ # echo platform > /sys/power/disk Telcontar:~ # echo disk > /sys/power/state Telcontar:~ # Interestingly, it did not reboot, it powered off at the end. I pressed the button, and it recovered just fine. +++··················· Unfortunately, the �platform� mode of hibernation does not work on some systems with broken BIOSes. In such cases the �shutdown� mode of hibernation might work: # echo shutdown > /sys/power/disk # echo disk > /sys/power/state (it is similar to the �reboot� mode, but it requires you to press the power button to make the system resume). If neither �platform� nor �shutdown� hibernation mode works, you will need to identify what goes wrong. ···················++- The third method also works. Telcontar:~ # echo shutdown > /sys/power/disk Telcontar:~ # echo disk > /sys/power/state Telcontar:~ # I will now login in graphical mode and try again. It worked. It took a looong time, with no messages, but it worked. Telcontar:~ # echo reboot > /sys/power/disk Telcontar:~ # echo disk > /sys/power/state Telcontar:~ # Telcontar:~ # echo platform > /sys/power/disk Telcontar:~ # echo disk > /sys/power/state Telcontar:~ # Both methods work. The command I use to hibernate normally is "systemctl hibernate" in an xfce-term as root. - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCY9fK+Bwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVHBAAniYlDbDwDIshx7pey42s qArsrgayAJ9H/iTVS6fmUM5vFTR2xMw6ib6PPw== =8pHt -----END PGP SIGNATURE-----
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E.R.