You are not logged in.

#1 2021-10-02 23:19:22

kalex
Member
Registered: 2021-10-02
Posts: 2

Hibernation... doesn't hibernate!

Hello,

New to the forum, I hope this is the correct place to post.

I've been using Arch for a while now (about a year). Hibernation has always worked correctly after initial setup. Then, without any change to the disk partitions, it stopped. When I try to hibernate, most of the times, it bringes me to the lock screen. I'm on a Lenovo Ideapad 320-15IKB, kernel 5.14.3-arch1-1.

I've tried to use

sudo systemctl hibernate

... same behaviour.

Here is a piece of the log from dmesg

Oct 03 01:05:23 arch kernel: PM: hibernation: hibernation entry
Oct 03 01:05:27 arch kernel: Filesystems sync: 0.174 seconds
Oct 03 01:05:27 arch kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Oct 03 01:05:27 arch kernel: OOM killer disabled.
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x00058000-0x00058fff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x56958000-0x56959fff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x58388000-0x58c87fff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x5f6a1000-0x5f71cfff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x6ee9e000-0x6fffdfff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Marking nosave pages: [mem 0x6ffff000-0xffffffff]
Oct 03 01:05:27 arch kernel: PM: hibernation: Basic memory bitmaps created
Oct 03 01:05:27 arch kernel: PM: hibernation: Preallocating image memory
Oct 03 01:05:27 arch kernel: PM: hibernation: Allocated 1608095 pages for snapshot
Oct 03 01:05:27 arch kernel: PM: hibernation: Allocated 6432380 kbytes in 1.59 seconds (4045.52 MB/s)
Oct 03 01:05:27 arch kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 03 01:05:27 arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 133 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: VI should always have 2 performance levels
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 148 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 145 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 146 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 13d ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 14f ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 151 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 135 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 190 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: 
                              last message was failed ret is 65535
Oct 03 01:05:27 arch kernel: amdgpu: 
                              failed to send message 84 ret is 65535 
Oct 03 01:05:27 arch kernel: amdgpu: Failed to force to switch arbf0!
Oct 03 01:05:27 arch kernel: amdgpu: [disable_dpm_tasks] Failed to disable DPM!
Oct 03 01:05:27 arch kernel: [drm:amdgpu_device_ip_suspend_phase2 [amdgpu]] *ERROR* suspend of IP block <powerplay> failed -22
Oct 03 01:05:27 arch kernel: amdgpu 0000:01:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_1.3.0 test failed (-110)
Oct 03 01:05:27 arch kernel: [drm:gfx_v8_0_hw_fini [amdgpu]] *ERROR* KCQ disable failed
Oct 03 01:05:27 arch kernel: amdgpu: cp is busy, skip halt cp
Oct 03 01:05:27 arch kernel: amdgpu: rlc is busy, skip halt rlc
Oct 03 01:05:27 arch kernel: amdgpu 0000:01:00.0: amdgpu: PCI CONFIG reset
Oct 03 01:05:27 arch kernel: PM: pci_pm_freeze(): amdgpu_pmops_freeze+0x0/0x40 [amdgpu] returns -22
Oct 03 01:05:27 arch kernel: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xb0 returns -22
Oct 03 01:05:27 arch kernel: amdgpu 0000:01:00.0: PM: failed to freeze async: error -22
Oct 03 01:05:27 arch kernel: usb usb1: root hub lost power or was reset
Oct 03 01:05:27 arch kernel: usb usb2: root hub lost power or was reset
Oct 03 01:05:27 arch kernel: sd 0:0:0:0: [sda] Starting disk
Oct 03 01:05:27 arch kernel: iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
Oct 03 01:05:27 arch kernel: iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
Oct 03 01:05:27 arch kernel: iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
Oct 03 01:05:27 arch kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 03 01:05:27 arch kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 03 01:05:27 arch kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Oct 03 01:05:27 arch kernel: ata1.00: supports DRM functions and may not be fully accessible
Oct 03 01:05:27 arch kernel: ata1.00: configured for UDMA/133
Oct 03 01:05:27 arch kernel: ata1.00: Enabling discard_zeroes_data
Oct 03 01:05:27 arch kernel: ata2.00: configured for UDMA/33
Oct 03 01:05:27 arch kernel: usb 1-3: reset full-speed USB device number 12 using xhci_hcd
Oct 03 01:05:27 arch kernel: usb 1-8: reset high-speed USB device number 4 using xhci_hcd
Oct 03 01:05:27 arch kernel: usb 1-7: reset full-speed USB device number 3 using xhci_hcd
Oct 03 01:05:27 arch kernel: PM: hibernation: Basic memory bitmaps freed
Oct 03 01:05:27 arch kernel: OOM killer enabled.
Oct 03 01:05:27 arch kernel: Restarting tasks ... 
Oct 03 01:05:27 arch kernel: mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915])
Oct 03 01:05:27 arch kernel: done.
Oct 03 01:05:27 arch kernel: Bluetooth: hci0: read Intel version: 370810011003110e32
Oct 03 01:05:27 arch kernel: Bluetooth: hci0: Intel device is already patched. patch num: 32
Oct 03 01:05:27 arch kernel: audit: type=1130 audit(1633215927.658:375): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-rfkill comm="systemd" exe="/usr/>
Oct 03 01:05:27 arch kernel: PM: hibernation: hibernation exit
Oct 03 01:05:27 arch kernel: audit: type=1130 audit(1633215927.738:376): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hibernate comm="systemd" exe="/u>
Oct 03 01:05:27 arch kernel: Generic FE-GE Realtek PHY r8169-0-200:00: attached PHY driver (mii_bus:phy_addr=r8169-0-200:00, irq=MAC)
Oct 03 01:05:27 arch kernel: r8169 0000:02:00.0 enp2s0: Link is Down
Oct 03 01:05:31 arch kernel: audit: type=1100 audit(1633215931.588:377): pid=283300 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permi>
Oct 03 01:05:31 arch kernel: audit: type=1101 audit(1633215931.588:378): pid=283300 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit ac>
Oct 03 01:05:31 arch kernel: audit: type=1103 audit(1633215931.588:379): pid=283300 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=pam_permit acct=>
Oct 03 01:05:31 arch kernel: wlp3s0: authenticate with 46:64:b8:94:dd:92
Oct 03 01:05:31 arch kernel: wlp3s0: send auth to 46:64:b8:94:dd:92 (try 1/3)
Oct 03 01:05:31 arch kernel: wlp3s0: authenticated
Oct 03 01:05:31 arch kernel: wlp3s0: associate with 46:64:b8:94:dd:92 (try 1/3)
Oct 03 01:05:31 arch kernel: wlp3s0: RX AssocResp from 46:64:b8:94:dd:92 (capab=0x1431 status=0 aid=8)
Oct 03 01:05:31 arch kernel: wlp3s0: associated
Oct 03 01:05:31 arch kernel: audit: type=1130 audit(1633215931.622:380): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@975 comm="systemd" exe=>
Oct 03 01:05:31 arch kernel: audit: type=1101 audit(1633215931.632:381): pid=283310 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pa>
Oct 03 01:05:31 arch kernel: audit: type=1103 audit(1633215931.632:382): pid=283310 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred grantors=? acct="sddm" ex>
Oct 03 01:05:31 arch kernel: audit: type=1006 audit(1633215931.635:383): pid=283310 uid=0 old-auid=4294967295 auid=975 tty=(none) old-ses=4294967295 ses=4 res=1
Oct 03 01:05:31 arch kernel: audit: type=1300 audit(1633215931.635:383): arch=c000003e syscall=1 success=yes exit=3 a0=9 a1=7fff1e228e80 a2=3 a3=3cf items=0 ppid=1 pi>
Oct 03 01:05:31 arch kernel: audit: type=1327 audit(1633215931.635:383): proctitle="(systemd)"
Oct 03 01:05:31 arch kernel: wlp3s0: Limiting TX power to 17 (20 - 3) dBm as advertised by 46:64:b8:94:dd:92
Oct 03 01:05:31 arch kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Oct 03 01:05:31 arch kernel: audit: type=1105 audit(1633215931.635:384): pid=283310 uid=0 auid=975 ses=4 msg='op=PAM:session_open grantors=pam_loginuid,pam_loginuid,p>
Oct 03 01:05:31 arch kernel: userif-2: sent link down event.
Oct 03 01:05:31 arch kernel: userif-2: sent link up event.
Oct 03 01:05:36 arch kernel: userif-2: sent link down event.
Oct 03 01:05:36 arch kernel: userif-2: sent link up event.
Oct 03 01:05:37 arch kernel: userif-2: sent link down event.
Oct 03 01:05:37 arch kernel: userif-2: sent link up event.
Oct 03 01:05:39 arch kernel: userif-2: sent link down event.
Oct 03 01:05:39 arch kernel: userif-2: sent link up event.
Oct 03 01:05:43 arch kernel: kauditd_printk_skb: 12 callbacks suppressed
Oct 03 01:05:43 arch kernel: audit: type=1131 audit(1633215943.075:393): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd">
Oct 03 01:05:44 arch kernel: audit: type=1100 audit(1633215944.595:394): pid=283441 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_shell>
Oct 03 01:05:44 arch kernel: audit: type=1101 audit(1633215944.598:395): pid=283441 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_access,pa>
Oct 03 01:05:54 arch kernel: audit: type=1131 audit(1633215954.928:396): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user@975 comm="systemd" exe="/usr/lib/sy>
Oct 03 01:05:54 arch kernel: audit: type=1131 audit(1633215954.958:397): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=user-runtime-dir@975 comm="systemd" exe=>
Oct 03 01:06:20 arch kernel: audit: type=1101 audit(1633215980.858:398): pid=283606 uid=1000 auid=1000 ses=2 msg='op=PAM:accounting grantors=pam_unix,pam_permit,pam_t>
Oct 03 01:06:20 arch kernel: audit: type=1110 audit(1633215980.862:399): pid=283606 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_>
Oct 03 01:06:20 arch kernel: audit: type=1105 audit(1633215980.865:400): pid=283606 uid=1000 auid=1000 ses=2 msg='op=PAM:session_open grantors=pam_limits,pam_unix,pam>
Oct 03 01:06:20 arch kernel: audit: type=1106 audit(1633215980.898:401): pid=283606 uid=1000 auid=1000 ses=2 msg='op=PAM:session_close grantors=pam_limits,pam_unix,pa>
Oct 03 01:06:20 arch kernel: audit: type=1104 audit(1633215980.898:402): pid=283606 uid=1000 auid=1000 ses=2 msg='op=PAM:setcred grantors=pam_faillock,pam_permit,pam_>

Partitions:

❯ sudo fdisk -l
[sudo] password for kalex: 
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 860 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 5C507042-7081-4AB6-A87B-E88FD77FDE84

Device          Start        End   Sectors   Size Type
/dev/sda1        2048     530431    528384   258M EFI System
/dev/sda2      532480     565247     32768    16M Microsoft reserved
/dev/sda3      567296  537438208 536870913   256G Microsoft basic data
/dev/sda4   537440256  570994687  33554432    16G Linux swap
/dev/sda5   570994688 1107863551 536868864   256G Linux filesystem
/dev/sda6  1107863552 1951463423 843599872 402.3G Linux filesystem
/dev/sda11 1951471616 1953519615   2048000  1000M Windows recovery environment
❯ cat /proc/swaps
Filename                                Type            Size            Used            Priority
/dev/sda4                               partition       16777212        3840            -2
❯ cat /etc/fstab
# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda11
UUID=bb2350a8-ded2-492a-b291-988767199359       /               ext4            rw,relatime     0 1

# /dev/sda10
UUID=dd9cdab5-9731-4278-b97e-cc9c831c99e0       none            swap            defaults        0 0

# /dev/sda12
UUID=2f12acac-25fb-4a29-af99-20727499736c       /home           ext4            defaults        0 2

Feel free to ask for other pieces of information (I'm sure I forgot something), but the configuration files, partitions, etc. can be assumed to be correct (as sometimes it actually hibernates as it should).

Thanks in advance!

Last edited by kalex (2021-10-02 23:21:56)

Offline

#2 2021-10-04 12:54:28

_dodger_
Member
Registered: 2019-11-12
Posts: 5

Re: Hibernation... doesn't hibernate!

Unfortunately, I can't help you with your issue - at least not directly.
That said: I have the same issue (or at least very similar) and it all started with the 5.14 kernel. 5.13 worked perfectly.
Maybe switching back to 5.13 is a temporary solution for you?

I came here to start a thread about this as well.

Offline

#3 2021-10-07 07:57:42

kalex
Member
Registered: 2021-10-02
Posts: 2

Re: Hibernation... doesn't hibernate!

I downgraded to kernel 5.13.13-arch1-1, it seems to be working now.

I think this issue should get more attention as it looks like a problem with the kernel (at least for someone).

Offline

Board footer

Powered by FluxBB