[opensuse-support] After upgrade to 15.0, restore from hibernation crashes the machine.
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop. Log: <10.6> 2019-01-10 20:20:01 Telcontar cron 27759 - - pam_unix(crond:session): session opened for user cer by (uid=0) <10.6> 2019-01-10 20:20:02 Telcontar CRON 27759 - - pam_unix(crond:session): session closed for user cer <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Reached target Sleep. <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Starting Hibernate... <0.7> 2019-01-10 20:23:50 Telcontar kernel - - - [117583.419978] PM: Hibernation mode set to 'platform' <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: Running prepare-grub .. <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - 2019-01-10 20:23:50+01:00 - Hibernating the system now... <3.4> 2019-01-10 20:23:50 Telcontar systemd-sh - - - Hibernating the system now... <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - service: no such service upsd.service <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - running kernel is grub menu entry openSUSE Leap 15.0 (vmlinuz-4.12.14-lp150.12.28-default) <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - preparing boot-loader: selecting entry openSUSE Leap 15.0, kernel /boot/4.12.14-lp150.12.28-default <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - running /usr/sbin/grub2-once "openSUSE Leap 15.0" <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - time needed for sync: 5.2 seconds, time needed for grub: 0.2 seconds. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - INFO: Done. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - Suspending system... <0.6> 2019-01-10 20:23:57 Telcontar kernel - - - [117590.115929] PM: Syncing filesystems ... 2019-01-11 11:07:16+01:00 - Booting the system now ================================================================================ Linux Telcontar 4.12.14-lp150.12.28-default #1 SMP Mon Dec 3 16:46:15 UTC 2018 (b91289f) x86_64 x86_64 x86_64 GNU/Linux <3.6> 2019-01-11 11:07:18 Telcontar systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) Hibernation has worked in this machine reliably for about a decade - till 15.0 :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Freitag, 11. Januar 2019, 11:50:46 CET schrieb Carlos E. R.:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Does S2RAM work? What is the video-hardware? Cheers Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 11/01/2019 15.02, Axel Braun wrote:
Am Freitag, 11. Januar 2019, 11:50:46 CET schrieb Carlos E. R.:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Does S2RAM work? What is the video-hardware?
There is no "s2... anything. "systemctl suspend" works, yes, but this is not a laptop, it is a desktop computer. Video hardware is nvidia. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Am Freitag, 11. Januar 2019, 15:19:16 CET schrieb Carlos E. R.:
On 11/01/2019 15.02, Axel Braun wrote:
Am Freitag, 11. Januar 2019, 11:50:46 CET schrieb Carlos E. R.:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Does S2RAM work? What is the video-hardware?
There is no "s2... anything.
old name for systemctl suspend....
"systemctl suspend" works, yes, but this is not a laptop, it is a desktop computer.
Video hardware is nvidia.
thats maybe the issue, initialization of HW (or the driver) after the return from hibernation. In the old power management one could configure hooks to shut down the video driver and fire it up after hibernation. I guess this can be done with systemd as well. Just found this: https://bbs.archlinux.org/viewtopic.php?id=208891 HTH Axel -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 11/01/2019 17.43, Axel Braun wrote:
Am Freitag, 11. Januar 2019, 15:19:16 CET schrieb Carlos E. R.:
On 11/01/2019 15.02, Axel Braun wrote:
Am Freitag, 11. Januar 2019, 11:50:46 CET schrieb Carlos E. R.:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Does S2RAM work? What is the video-hardware?
There is no "s2... anything.
old name for systemctl suspend....
with pm-utils.
"systemctl suspend" works, yes, but this is not a laptop, it is a desktop computer.
Video hardware is nvidia.
thats maybe the issue, initialization of HW (or the driver) after the return from hibernation. In the old power management one could configure hooks to shut down the video driver and fire it up after hibernation. I guess this can be done with systemd as well.
With pm-utils there were tricks, now, no. And this machine with the same hardware was hibernating fine a week ago with 42.3... If it were the video restore, I would hope the machine to be accessible via ssh, but no.
Just found this: https://bbs.archlinux.org/viewtopic.php?id=208891
They do this: Can you change your boot hooks to this order, then mkinit again. "HOOKS="base udev plymouth autodetect modconf block resume filesystems keyboard fsck"" No idea what "HOOKS" is. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
11.01.2019 13:50, Carlos E. R. пишет:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Log:
<10.6> 2019-01-10 20:20:01 Telcontar cron 27759 - - pam_unix(crond:session): session opened for user cer by (uid=0) <10.6> 2019-01-10 20:20:02 Telcontar CRON 27759 - - pam_unix(crond:session): session closed for user cer <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Reached target Sleep. <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Starting Hibernate... <0.7> 2019-01-10 20:23:50 Telcontar kernel - - - [117583.419978] PM: Hibernation mode set to 'platform'
Try setting mode to "shutdown". See "man systemd-sleep.conf" HibernateMode=shutdown You can see possible modes in /sys/power/disk
<3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: Running prepare-grub .. <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - 2019-01-10 20:23:50+01:00 - Hibernating the system now... <3.4> 2019-01-10 20:23:50 Telcontar systemd-sh - - - Hibernating the system now... <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - service: no such service upsd.service <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - running kernel is grub menu entry openSUSE Leap 15.0 (vmlinuz-4.12.14-lp150.12.28-default) <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - preparing boot-loader: selecting entry openSUSE Leap 15.0, kernel /boot/4.12.14-lp150.12.28-default <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - running /usr/sbin/grub2-once "openSUSE Leap 15.0" <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - time needed for sync: 5.2 seconds, time needed for grub: 0.2 seconds. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - INFO: Done. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - Suspending system... <0.6> 2019-01-10 20:23:57 Telcontar kernel - - - [117590.115929] PM: Syncing filesystems ... 2019-01-11 11:07:16+01:00 - Booting the system now ================================================================================ Linux Telcontar 4.12.14-lp150.12.28-default #1 SMP Mon Dec 3 16:46:15 UTC 2018 (b91289f) x86_64 x86_64 x86_64 GNU/Linux <3.6> 2019-01-11 11:07:18 Telcontar systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid)
Hibernation has worked in this machine reliably for about a decade - till 15.0 :-(
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop.
Log:
<10.6> 2019-01-10 20:20:01 Telcontar cron 27759 - - pam_unix(crond:session): session opened for user cer by (uid=0) <10.6> 2019-01-10 20:20:02 Telcontar CRON 27759 - - pam_unix(crond:session): session closed for user cer <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Reached target Sleep. <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Starting Hibernate... <0.7> 2019-01-10 20:23:50 Telcontar kernel - - - [117583.419978] PM: Hibernation mode set to 'platform'
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file. cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~> Will test change. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-) Do you know the difference between "platform" and "shutdown"? Or a document? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
12.01.2019 12:49, Carlos E. R. пишет:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
Do you know the difference between "platform" and "shutdown"?
"platform" is using ACPI (at least on x86) to enter and resume from S4 state while "shutdown" simply switches off the system. "shutdown" ensures that devices are properly initialized on resume (they go via normal power on sequence) while "platform" relies on ACPI to perform transition and so is more fragile.
Or a document?
Kernel documentation has some information.
On 12/01/2019 13.04, Andrei Borzenkov wrote:
12.01.2019 12:49, Carlos E. R. пишет:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
Do you know the difference between "platform" and "shutdown"?
"platform" is using ACPI (at least on x86) to enter and resume from S4 state while "shutdown" simply switches off the system. "shutdown" ensures that devices are properly initialized on resume (they go via normal power on sequence) while "platform" relies on ACPI to perform transition and so is more fragile.
Ah, that explains it, thanks.
Or a document?
Kernel documentation has some information.
I think the above suffices :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 12/01/2019 10.49, Carlos E. R. wrote:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
And this afternoon it crashed again :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
12.01.2019 23:29, Carlos E. R. пишет:
On 12/01/2019 10.49, Carlos E. R. wrote:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
And this afternoon it crashed again :-(
Well, at this point you have choice between trying to debug it yourself or simply submitting bug report. Some debugging hints are here: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu... Testing current kernel from Kernel:stable or Kernel:HEAD is of course always recommended before making bug report (that it what you will be asked most likely anyway).
On 13/01/2019 08.14, Andrei Borzenkov wrote:
12.01.2019 23:29, Carlos E. R. пишет:
On 12/01/2019 10.49, Carlos E. R. wrote:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
And this afternoon it crashed again :-(
Well, at this point you have choice between trying to debug it yourself or simply submitting bug report. Some debugging hints are here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu...
Testing current kernel from Kernel:stable or Kernel:HEAD is of course always recommended before making bug report (that it what you will be asked most likely anyway).
I'll try new kernel first, yes. Well, before I'll try to hibernate more times and see. Maybe hibernate in text mode. Yes, once I tried to debug hibernate. I inserted lines in the kernel code to output text and find out the crash point. Not something that makes me enthusiastic. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday, 2019-01-13 at 13:25 +0100, Carlos E. R. wrote:
On 13/01/2019 08.14, Andrei Borzenkov wrote:
12.01.2019 23:29, Carlos E. R. пишет:
On 12/01/2019 10.49, Carlos E. R. wrote:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
For the record, the exact syntax is: cer@Telcontar:~> cat /etc/systemd/sleep.conf [Sleep] HibernateMode=shutdown cer@Telcontar:~> Case sensitive.
And this afternoon it crashed again :-(
Well, at this point you have choice between trying to debug it yourself or simply submitting bug report. Some debugging hints are here:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Docu...
Testing current kernel from Kernel:stable or Kernel:HEAD is of course always recommended before making bug report (that it what you will be asked most likely anyway).
I'll try new kernel first, yes. Well, before I'll try to hibernate more times and see. Maybe hibernate in text mode.
Yes, once I tried to debug hibernate. I inserted lines in the kernel code to output text and find out the crash point. Not something that makes me enthusiastic.
Finally, I managed to try the kernel used on Leap 15.1 (because I think it will be the easiest, re NVidia or vmware), and it appears to work. I have hibernated 7 times so far, sucesfully. cer@Telcontar:~> uname -a Linux Telcontar 4.12.14-lp151.23-default #1 SMP Fri Mar 22 18:22:30 UTC 2019 (b40158b) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHIEARECADIWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXKe8KRQccm9iaW4ubGlz dGFzQGdteC5lcwAKCRC1MxgcbY1H1aaQAJ9JZfQqCZV17ocKQOOQJr4bxZPSJQCd F4gmqv1WF2nVc25J5HGY2l4LTgY= =zEWZ -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2019-01-12 at 21:29 +0100, Carlos E. R. wrote:
On 12/01/2019 10.49, Carlos E. R. wrote:
On 11/01/2019 19.45, Carlos E. R. wrote:
On 11/01/2019 19.24, Andrei Borzenkov wrote:
11.01.2019 13:50, Carlos E. R. пишет:
Try setting mode to "shutdown". See "man systemd-sleep.conf"
HibernateMode=shutdown
You can see possible modes in /sys/power/disk
Apparently, I have no "sleep.conf" file.
cer@Telcontar:~> cat /sys/power/disk [platform] shutdown reboot suspend test_resume cer@Telcontar:~>
Will test change.
It worked - thank you :-)
And this afternoon it crashed again :-(
I found out that it did not work because this incantation is case sensitive :-/ It has to be exactly this, or it produces errors in syslog (see thread "How can I hibernate in shutdown mode?" dated 2019-03-01): Telcontar:~ # cat /etc/systemd/sleep.conf [Sleep] HibernateMode=shutdown Telcontar:~ # - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHIEARECADIWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXID+tRQccm9iaW4ubGlz dGFzQGdteC5lcwAKCRC1MxgcbY1H1TwWAKCVF/ijuQGx8GJ/IwsfYcL7hwYK9gCe JRVD+os4XnhEk/ULrr3PFdjqD+E= =cD5I -----END PGP SIGNATURE-----
participants (4)
-
Andrei Borzenkov -
Axel Braun -
Carlos E. R. -
Carlos E. R.