Mailinglist Archive: opensuse-factory (807 mails)

< Previous Next >
[opensuse-factory] how to debug hibernation issue
  • From: "Axel Braun" <Axel.Braun@xxxxxx>
  • Date: Sun, 12 Feb 2017 19:42:38 +0100
  • Message-id: <trinity-83fec14e-180c-45c4-bebb-b38eaffacd2a-1486924958695@3capp-gmx-bs77>
Hi,

I made an upgrade on my Asus eeePC from 13.1 to Tumbleweed in a single run
(first update zypper, then run zypper dup).
That worked perfectly, no issues so far, except that hibernation does not work
(suspend does!).

System boots into the hibernation file, screen gets black, and after some
seconds it reboots

journalctl issues:
Feb 12 19:20:33 eeePC systemd[1]: Found device ASUS-JM_S41_SSD 2.
Feb 12 19:20:33 eeePC systemd[1]: Found device ASUS-JM_S41_SSD 1.
Feb 12 19:20:33 eeePC systemd[1]: Starting Resume from hibernation using device
/dev/sda1...
Feb 12 19:20:33 eeePC systemd[1]: Reached target Initrd Root Device.
Feb 12 19:20:33 eeePC systemd-hibernate-resume[287]: Could not resume from
'/dev/sda1' (8:1).
Feb 12 19:20:33 eeePC kernel: PM: Starting manual resume from disk
Feb 12 19:20:33 eeePC kernel: PM: Hibernation image partition 8:1 present
Feb 12 19:20:33 eeePC kernel: PM: Looking for hibernation image.
Feb 12 19:20:33 eeePC kernel: PM: Image not found (code -22)
Feb 12 19:20:33 eeePC kernel: PM: Hibernation image not present or could not be
loaded.
Feb 12 19:20:33 eeePC systemd[1]: Started Resume from hibernation using device
/dev/sda1.
Feb 12 19:20:33 eeePC systemd[1]: Reached target Local File Systems (Pre).
Feb 12 19:20:33 eeePC systemd[1]: Reached target Local File Systems.
Feb 12 19:20:33 eeePC systemd[1]: Reached target System Initialization.
Feb 12 19:20:33 eeePC systemd[1]: Reached target Basic System.
Feb 12 19:20:33 eeePC systemd[1]: Starting File System Check on
/dev/disk/by-uuid/efb6a106-11a1-4537-baac-2d2

Obviously the image file was not written properly?
Any idea what I could try?

Thanks
Axel
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx

< Previous Next >