Cannot wake up from hibernate

It’s the same issue as this one.

Seemed like the latest update had fixed the issue, but it’s back. But now it doesn’t happen always. Sometimes hibernate does work, sometimes it doesn’t.

As described in the linked post, nothing shows up in journalctl. Let me know if I can look anywhere else and post some details.

inxi -Fazy

System:
  Kernel: 5.14.10-1-MANJARO x86_64 bits: 64 compiler: gcc v: 11.1.0
  parameters: BOOT_IMAGE=/boot/vmlinuz-5.14-x86_64
  root=UUID=fe64fafd-1c2a-4b55-846f-c264196ff166 rw nomce "acpi_osi=Windows
  2018" quiet resume=UUID=4517ac81-4ac6-42a0-8e7a-a5870b5f98df
  Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 wm: kwin_x11 vt: 1 dm: SDDM
  Distro: Manjaro Linux base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP Pavilion Laptop 14-bf1xx
  v: Type1ProductConfigId serial: <filter> Chassis: type: 10 serial: <filter>
  Mobo: HP model: 83CE v: 59.38 serial: <filter> UEFI: Insyde v: F.31
  date: 10/30/2017
Battery:
  ID-1: BAT1 charge: 18.6 Wh (44.0%) condition: 42.3/42.3 Wh (100.0%)
  volts: 12.5 min: 11.6 model: Hewlett-Packard PABAS0241231 type: Li-ion
  serial: <filter> status: Charging
CPU:
  Info: Quad Core model: Intel Core i7-8550U bits: 64 type: MT MCP
  arch: Kaby Lake note: check family: 6 model-id: 8E (142) stepping: A (10)
  microcode: EA cache: L2: 8 MiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 32012
  Speed: 800 MHz min/max: 400/1800 MHz Core speeds (MHz): 1: 800 2: 800 3: 800
  4: 800 5: 799 6: 800 7: 800 8: 800
  Vulnerabilities: Type: itlb_multihit status: KVM: VMX unsupported
  Type: l1tf mitigation: PTE Inversion
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: spec_store_bypass
  mitigation: Speculative Store Bypass disabled via prctl and seccomp
  Type: spectre_v1
  mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Full generic retpoline, IBPB: conditional,
  IBRS_FW, STIBP: conditional, RSB filling
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915
  v: kernel bus-ID: 00:02.0 chip-ID: 8086:5917 class-ID: 0300
  Device-2: NVIDIA GM108M [GeForce 940MX] vendor: Hewlett-Packard
  driver: nvidia v: 470.63.01 alternate: nouveau,nvidia_drm bus-ID: 01:00.0
  chip-ID: 10de:134d class-ID: 0302
  Device-3: Chicony HP Wide Vision HD Camera type: USB driver: uvcvideo
  bus-ID: 1-5:4 chip-ID: 04f2:b5d6 class-ID: 0e02
  Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver:
  loaded: modesetting,nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 115 s-size: 424x238mm (16.7x9.4")
  s-diag: 486mm (19.1")
  Monitor-1: eDP-1 res: 1920x1080 hz: 60 dpi: 158 size: 309x173mm (12.2x6.8")
  diag: 354mm (13.9")
  OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 21.2.3
  direct render: Yes
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Hewlett-Packard
  driver: snd_hda_intel v: kernel alternate: snd_soc_skl bus-ID: 00:1f.3
  chip-ID: 8086:9d71 class-ID: 0403
  Sound Server-1: ALSA v: k5.14.10-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.19 running: no
  Sound Server-3: PulseAudio v: 15.0 running: no
  Sound Server-4: PipeWire v: 0.3.38 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: Hewlett-Packard driver: r8168 v: 8.049.02-NAPI modules: r8169
  port: 3000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: down mac: <filter>
  Device-2: Intel Wireless 7265 driver: iwlwifi v: kernel bus-ID: 03:00.0
  chip-ID: 8086:095a class-ID: 0280
  IF: wlo1 state: up mac: <filter>
  IF-ID-1: br-ab1ab553cc42 state: up speed: 10000 Mbps duplex: unknown
  mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
  IF-ID-3: veth98d2cba state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-4: vethaf15093 state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-5: vethb5dde2a state: up speed: 10000 Mbps duplex: full mac: <filter>
  IF-ID-6: wgpia0 state: unknown speed: N/A duplex: N/A mac: N/A
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8
  bus-ID: 1-4:3 chip-ID: 8087:0a2a class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.03 TiB used: 680.72 GiB (64.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/sda maj-min: 8:0 vendor: Seagate model: ST1000LM035-1RK172
  size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  type: HDD rpm: 5400 serial: <filter> rev: RSM7 scheme: GPT
  ID-2: /dev/sdb maj-min: 8:16 vendor: SanDisk model: SD8SN8U-128G-1006
  size: 119.24 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
  type: SSD serial: <filter> rev: 0006 scheme: GPT
Partition:
  ID-1: / raw-size: 50 GiB size: 48.72 GiB (97.43%) used: 29.31 GiB (60.2%)
  fs: ext4 dev: /dev/sdb5 maj-min: 8:21
  ID-2: /boot/efi raw-size: 277 MiB size: 276.4 MiB (99.80%)
  used: 280 KiB (0.1%) fs: vfat dev: /dev/sdb1 maj-min: 8:17
  ID-3: /home raw-size: 56.97 GiB size: 55.83 GiB (97.99%)
  used: 34.75 GiB (62.3%) fs: ext4 dev: /dev/sdb2 maj-min: 8:18
Swap:
  Kernel: swappiness: 1 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: partition size: 12 GiB used: 0 KiB (0.0%) priority: -2
  dev: /dev/sdb3 maj-min: 8:19
Sensors:
  System Temperatures: cpu: 33.0 C mobo: 29.8 C
  Fan Speeds (RPM): N/A
Info:
  Processes: 298 Uptime: 8m wakeups: 1 Memory: 7.69 GiB used: 4.43 GiB (57.6%)
  Init: systemd v: 249 tool: systemctl Compilers: gcc: 11.1.0 clang: 12.0.1
  Packages: 1982 pacman: 1978 lib: 436 flatpak: 4 Shell: fish v: 3.3.1
  running-in: yakuake inxi: 3.3.07

@Sushisource reported the same issue in the last thread. So tagging you here in case you’re still facing this.

That’s not really a viable option for me tbh.

This is some log from the latest failure.

journalctl --boot -1 --dmesg | tail -50

Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:29:58 sintan-pc kernel: wlo1: send auth to c0:c9:e3:00:b5:51 (try 1/3)
Oct 25 01:29:58 sintan-pc kernel: wlo1: authenticated
Oct 25 01:29:58 sintan-pc kernel: wlo1: associate with c0:c9:e3:00:b5:51 (try 1/3)
Oct 25 01:29:58 sintan-pc kernel: wlo1: RX AssocResp from c0:c9:e3:00:b5:51 (capab=0x11 status=0 aid=2)
Oct 25 01:29:58 sintan-pc kernel: wlo1: associated
Oct 25 01:29:58 sintan-pc kernel: wlo1: Connection to AP c0:c9:e3:00:b5:51 lost
Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:29:58 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:29:59 sintan-pc kernel: wlo1: authenticate with c0:c9:e3:00:b5:51
Oct 25 01:29:59 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:29:59 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:29:59 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:29:59 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:29:59 sintan-pc kernel: wlo1: send auth to c0:c9:e3:00:b5:51 (try 1/3)
Oct 25 01:29:59 sintan-pc kernel: wlo1: authenticated
Oct 25 01:29:59 sintan-pc kernel: wlo1: associate with c0:c9:e3:00:b5:51 (try 1/3)
Oct 25 01:29:59 sintan-pc kernel: wlo1: RX AssocResp from c0:c9:e3:00:b5:51 (capab=0x11 status=0 aid=2)
Oct 25 01:29:59 sintan-pc kernel: wlo1: associated
Oct 25 01:30:02 sintan-pc kernel: audit: type=1130 audit(1635143402.840:2496): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 01:30:13 sintan-pc kernel: audit: type=1131 audit(1635143413.527:2497): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 01:30:37 sintan-pc kernel: audit: type=1130 audit(1635143437.957:2498): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Oct 25 01:30:37 sintan-pc kernel: wlo1: deauthenticating from c0:c9:e3:00:b5:51 by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: AER: Corrected error received: 0000:00:1c.5
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:   device [8086:9d15] error status/mask=00000001/00002000
Oct 25 01:30:38 sintan-pc kernel: pcieport 0000:00:1c.5:    [ 0] RxErr                  (First)
Oct 25 01:30:39 sintan-pc kernel: PM: hibernation: hibernation entry
Oct 25 01:30:39 sintan-pc kernel: ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Oct 25 01:30:39 sintan-pc kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
Oct 25 01:30:40 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Oct 25 01:30:40 sintan-pc kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Oct 25 01:30:40 sintan-pc kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Oct 25 01:30:40 sintan-pc kernel: ata1.00: configured for UDMA/100
Oct 25 01:30:40 sintan-pc kernel: sd 0:0:0:0: [sda] Starting disk

Adding nomsi to GRUB_CMDLINE_LINUX line in /etc/default/grub seems to have helped. Will close if the issue doesn’t return in a few days.

Edit : Still happening. Trying with noaer now.

Edit 2 : Still happening.

Edit 3 : What has been working for me for the last few days is editing /etc/default/grub so that these two lines are like this :

GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi='Windows 2015' quiet resume=UUID=4517ac81-4ac6-42a0-8e7a-a5870b5f98df pci=nomsi"
GRUB_CMDLINE_LINUX="pci=noaer"

Will close if I don’t run into further problems.

1 Like

Thanks for @ ing me, because adding those PCI parameters seems to have helped for me too. At least, I was literally never able to resume from suspend/hibernate and I did just manage to successfully resume from hibernate just now so thanks for the tip.

Any idea why those params matter / work? I don’t have any PCI errors in my logs like you do so I’m kinda surprised this helped at all. Only concerning things I see are these:

Nov 13 11:44:11 monolith-linux kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80
Nov 13 11:44:11 monolith-linux kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x201] vs fed40080 f80

Some nvidia nonsense

Nov 13 11:44:11 monolith-linux kernel: nvidia: loading out-of-tree module taints kernel.
Nov 13 11:44:11 monolith-linux kernel: nvidia: module license 'NVIDIA' taints kernel.
Nov 13 11:44:11 monolith-linux kernel: Disabling lock debugging due to kernel taint
Nov 13 11:44:11 monolith-linux kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Nov 13 11:44:11 monolith-linux kernel: nvidia-gpu 0000:01:00.3: pci_alloc_irq_vectors err -22
Nov 13 11:44:11 monolith-linux kernel: nvidia-gpu: probe of 0000:01:00.3 failed with error -22
Nov 13 11:44:11 monolith-linux kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 235
Nov 13 11:44:11 monolith-linux kernel:
Nov 13 11:44:11 monolith-linux kernel: nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem
Nov 13 11:44:11 monolith-linux systemd-modules-load[242]: Inserted module 'nvidia'
Nov 13 11:44:11 monolith-linux kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module  470.63.01  Tue Aug  3 20:44:16 UTC 2021

And some lines like this:

Nov 13 11:46:37 monolith-linux upowerd[1288]: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb5/5-2
Nov 13 11:46:37 monolith-linux upowerd[1288]: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb5/5-2/5-2.3
Nov 13 11:46:37 monolith-linux upowerd[1288]: treating change event as add on /sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0/usb5/5-2/5-2.3

Which is maybe the pci related part

I’m not sure really. I found it in the arch forums, where someone was having a similar issue (but not the same as they couldn’t even suspend). And this seems not to be a permanent/proper fix as wakeup still fails sometimes.