You are not logged in.

Pages: 1

#1 2023-12-07 23:51:06

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Computer hibernates and immediately turns itself back on

Hello, I am trying to set up hibernation on my computer, but it immediately turns itself back on after hibernating. I followed the arch wiki step by step, and tripled checked to confirm I didn't miss any steps. Here are some information:

My swap file size is 30 GB (double RAM usage), located at 

/swapfile

. In /etc/tmpfiles.d/hibernation_image_size.conf, 

#    Path                   Mode UID  GID  Age Argument
w    /sys/power/image_size  -    -    -    -   31457280

/etc/mkinitcpio.conf,

HOOKS=(base udev autodetect modconf keyboard keymap consolefont block filesystems resume fsck)

cat /proc/cmdline,

BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=c9fda7dc-4e50-40b5-93b1-1e462edfc116 rw nvidia-drm.modeset=1 loglevel=3 quiet splash resume=UUID=c9fda7dc-4e50-40b5-93b1-1e462edfc116 resume_offset=6393856

To double check that the UUID of resume and the offset is correct:
sudo findmnt -no UUID -T /swapfile

c9fda7dc-4e50-40b5-93b1-1e462edfc116

sudo filefrag -v /swapfile

Filesystem type is: ef53
File size of /swapfile is 32212254720 (7864320 blocks of 4096 bytes)
 ext:     logical_offset:        physical_offset: length:   expected: flags:
   0:        0..    4095:    6393856..   6397951:   4096:

fstab:

/swapfile none swap defaults 0 0

Journalctl of previous hibernation attempt:
journalctl -u systemd-hibernate.service

Dec 08 07:34:35 Fustigate-Arch systemd[1]: Starting Hibernate...
Dec 08 07:34:35 Fustigate-Arch systemd-sleep[3786]: Entering sleep state 'hibernate'...
Dec 08 07:34:49 Fustigate-Arch systemd-sleep[3786]: System returned from sleep state.
Dec 08 07:34:49 Fustigate-Arch systemd[1]: systemd-hibernate.service: Deactivated successfully.
Dec 08 07:34:49 Fustigate-Arch systemd[1]: Finished Hibernate.
Dec 08 07:34:49 Fustigate-Arch systemd[1]: systemd-hibernate.service: Consumed 6.696s CPU time.

Sometimes:

Dec 07 21:14:33 Fustigate-Arch systemd[1]: Starting Hibernate...
Dec 07 21:14:33 Fustigate-Arch systemd-sleep[6961]: Entering sleep state 'hibernate'...
Dec 07 21:14:41 Fustigate-Arch systemd-sleep[6961]: Failed to put system to sleep. System resumed again: Device or resource busy
Dec 07 21:14:41 Fustigate-Arch systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Dec 07 21:14:41 Fustigate-Arch systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Dec 07 21:14:41 Fustigate-Arch systemd[1]: Failed to start Hibernate.
Dec 07 21:14:41 Fustigate-Arch systemd[1]: systemd-hibernate.service: Consumed 6.763s CPU time.

journalctl -S 'Dec 08 07:34:35' -U 'Dec 08 07:34:49'
https://pastebin.com/sHwsLa8y

Suspending my computer also immediately wakes up.

Offline

#2 2023-12-08 08:39:22

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

Suspending my computer also immediately wakes up.

Please post your complete system journal for a boot covering that: 

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Also 

cat /proc/acpi/wakeup

https://wiki.archlinux.org/title/Power_ … om_suspend

And ceterum censeo: Is there a parallel windows installation?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2023-12-08 10:00:23

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

Here they are:


sudo journalctl -b | curl -F 'file=@-' 0x0.st

http://0x0.st/H3cn.txt

cat /proc/acpi/wakeup

http://0x0.st/H3c5.txt

There is a parallel windows installation. I am dual booting Arch Linux.
By the way, if useful, my kernel is 6.6.4-arch1-1.


EDIT:
I tried disabling everything in /proc/acpi/wakeup, and tried again, but it still didn't work; it continued to instantaneously wake up.

Last edited by Fustigate (2023-12-08 12:12:30)

Offline

#4 2023-12-08 12:38:38

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

There is a parallel windows installation.

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

You've dhcpcd and NM enabled, pick one, disable the other (since you're using wifi, you probably want to keep NM)

Since you're nvme acts up

Dec 08 09:47:15 Fustigate-Arch kernel: pcieport 10000:e0:1b.4: can't derive routing for PCI INT A
Dec 08 09:47:15 Fustigate-Arch kernel: nvme 10000:e1:00.0: PCI INT A: no GSI
Dec 08 09:47:15 Fustigate-Arch kernel: pcieport 10000:e0:1d.4: can't derive routing for PCI INT A
Dec 08 09:47:15 Fustigate-Arch kernel: nvme 10000:e2:00.0: PCI INT A: no GSI

see https://wiki.archlinux.org/title/Solid_ … leshooting and disable APST and try "iommu=soft"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2023-12-08 14:41:13

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

Hi seth, I did everything above, but it's still not working. After doing it, bluetooth won't start (bluetooth works after rebooting, but as soon as I enter password in plasma and login, it stops working)...

Dec 08 22:39:00 Fustigate-Arch bluetoothd[824]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 22:39:00 Fustigate-Arch bluetoothd[824]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 22:39:00 Fustigate-Arch bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down

Could you help me fix bluetooth? I give up on fixing hibernation... I just want to revert to my previous state. Thank you

Last edited by Fustigate (2023-12-08 14:48:06)

Offline

#6 2023-12-08 14:47:51

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

Post the complete journal, the symptoms mean that either the BT didn't power up or powered down for some reason, but the userspace error can't possibly hint at "why".
Undo the iommu=soft and since radio is a frequent victim of the fast-start/hibernation condition: you did fully reboot both OS after the change?
(It's "voodoo" because it's not ecactly clear why, but it is frequently required to "unconfuse" the firmware)

Also check "rfkill"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2023-12-08 14:51:14

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

rfkill returns

ID TYPE      DEVICE      SOFT      HARD
 1 wlan      phy0   unblocked unblocked
 3 bluetooth hci0   unblocked unblocked

I'll update on a new reply after I reboot after undoing iommu=soft, and try rebooting windows and linux twice again.

Offline

#8 2023-12-08 15:05:47

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

Update:
bluetooth working after 

sudo systemctl start bluetooth-mesh.service

, but 

sudo systemctl status bluetooth.service

still retuns the same error.

zsh ➜ sudo systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Fri 2023-12-08 23:06:34 CST; 25s ago
       Docs: man:bluetoothd(8)
   Main PID: 6889 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38028)
     Memory: 1.1M (peak: 1.7M)
        CPU: 42ms
     CGroup: /system.slice/bluetooth.service
             └─6889 /usr/lib/bluetooth/bluetoothd

Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc_xq_453
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc_xq_453
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc_xq_512
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc_xq_512
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSink/sbc_xq_552
Dec 08 23:06:34 Fustigate-Arch bluetoothd[6889]: Endpoint registered: sender=:1.74 path=/MediaEndpoint/A2DPSource/sbc_xq_552
Dec 08 23:06:35 Fustigate-Arch bluetoothd[6889]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 23:06:35 Fustigate-Arch bluetoothd[6889]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters

~ 
zsh ➜ sudo systemctl status bluetooth-mesh.service
● bluetooth-mesh.service - Bluetooth mesh service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth-mesh.service; enabled; preset: disabled)
     Active: active (running) since Fri 2023-12-08 22:59:58 CST; 7min ago
   Main PID: 4725 (bluetooth-meshd)
      Tasks: 1 (limit: 38028)
     Memory: 668.0K (peak: 1.2M)
        CPU: 17ms
     CGroup: /system.slice/bluetooth-mesh.service
             └─4725 /usr/lib/bluetooth/bluetooth-meshd

Dec 08 22:59:58 Fustigate-Arch systemd[1]: Started Bluetooth mesh service.
Dec 08 22:59:58 Fustigate-Arch bluetooth-meshd[4725]: index 0 up:1 pwr: 0 mesh: 1
Dec 08 22:59:58 Fustigate-Arch bluetooth-meshd[4725]: Controller hci 0 not in use
Dec 08 22:59:58 Fustigate-Arch bluetooth-meshd[4725]: mesh_ready_callback
Dec 08 22:59:58 Fustigate-Arch bluetooth-meshd[4725]: Added Network Interface on /org/bluez/mesh
Dec 08 23:04:25 Fustigate-Arch bluetooth-meshd[4725]: Failed to read info for hci index 0: Invalid Index (0x11)
Dec 08 23:04:25 Fustigate-Arch bluetooth-meshd[4725]: Hci dev 0 removal detected
Dec 08 23:04:25 Fustigate-Arch bluetooth-meshd[4725]: index 0 up:0 pwr: 0 mesh: 0
Dec 08 23:04:25 Fustigate-Arch bluetooth-meshd[4725]: index 0 up:1 pwr: 0 mesh: 1
Dec 08 23:04:25 Fustigate-Arch bluetooth-meshd[4725]: Controller hci 0 not in use



cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=c9fda7dc-4e50-40b5-93b1-1e462edfc116 rw nvidia-drm.modeset=1 loglevel=3 quiet splash resume=UUID=c9fda7dc-4e50-40b5-93b1-1e462edfc116 resume_offset=6393856 nvme_core.default_ps_max_latency_us=0

Hibernation and suspend still doesn't work.

Journal logs:
http://0x0.st/H3A5.txt

As you can see, these two lines still persist, but is it causing the error?

Dec 08 22:58:16 Fustigate-Arch kernel: nvme nvme1: pci function 10000:e2:00.0
Dec 08 22:58:16 Fustigate-Arch kernel: nvme nvme0: pci function 10000:e1:00.0

Last edited by Fustigate (2023-12-08 15:09:29)

Offline

#9 2023-12-08 15:40:09

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

Ftr, the same BT errors show up in your original journal

Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 07:57:32 Fustigate-Arch kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Dec 08 07:57:32 Fustigate-Arch kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:device_set_wake_support() Unable to set wake_support without RPA resolution
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 07:57:32 Fustigate-Arch bluetoothd[862]: src/device.c:set_wake_allowed_complete() Set device flags return status: Invalid Parameters
Dec 08 07:57:32 Fustigate-Arch kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
Dec 08 07:57:32 Fustigate-Arch kernel: Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)

What exactly is your metric for "bluetooth doesn't work"?

Dec 08 13:27:12 Fustigate-Arch plasmashell[1568]: kf.bluezqt: PendingCall Error: "br-connection-page-timeout"

doesn't show up in the new journal.

More things:
1. dhcpcd is still enabled
2. 

Dec 08 23:04:25 Fustigate-Arch kernel: Wakeup pending. Abort CPU freeze

there's still some wakeup scheduled.
3. The nvme and various other PCI errors showing up when prematurely waking might just be a symptom of the latter, not the cause

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#10 2023-12-09 08:17:38

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

For voodoo reasons, bluetooth works for now (with both bluetooth.service and bluetooth-mesh.service enabled and active)

I disabled dhcpcd.service and disabled everything in /proc/acpi/wakeup:

○ dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; disabled; preset: disabled)
     Active: inactive (dead)

Dec 09 16:02:53 Fustigate-Arch dhcpcd[910]: wlan0: adding route to 172.16.48.0/20
Dec 09 16:02:53 Fustigate-Arch dhcpcd[910]: wlan0: adding default route via 172.16.48.1
Dec 09 16:02:58 Fustigate-Arch dhcpcd[910]: wlan0: no IPv6 Routers available
Dec 09 16:08:04 Fustigate-Arch systemd[1]: Stopping DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces...
Dec 09 16:08:04 Fustigate-Arch dhcpcd[910]: received SIGTERM, stopping
Dec 09 16:08:04 Fustigate-Arch dhcpcd[910]: wlan0: removing interface
Dec 09 16:08:04 Fustigate-Arch dhcpcd[910]: enp108s0: removing interface
Dec 09 16:08:04 Fustigate-Arch dhcpcd[910]: dhcpcd exited
Dec 09 16:08:04 Fustigate-Arch systemd[1]: dhcpcd.service: Deactivated successfully.
Dec 09 16:08:04 Fustigate-Arch systemd[1]: Stopped DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces.

........... And it worked!!!




Thank you so much!

Will I have to disable every active device everytime I restart for hibernation? Or can I automate that process?





EDIT:
after coming back from hibernation, hibernation fails again... ......................

Last edited by Fustigate (2023-12-09 08:21:03)

Offline

#11 2023-12-09 08:25:55

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

Will I have to disable every active device everytime I restart for hibernation?

You first and foremost should figure which is the critical device - and whether after the voodoo dance and deactivating dhcpcd this is still necessary at all.

You can then test it using S3 (which is obviously the faster process) and bisect your way there.
(enable half the devices you want/need/have by default and see whether S3 still works; if yes, continue w/ half of the remaining devices etc. If things break, you know which bracket includes a troublesome device and can split that in halves to narrow in on it. Be aware that there might be two or more breaking devices in the same bracket at any time)

Once you figured which devices you get away with/need to deactivate you can automatically deactivate them w/ a systemd service on boot, for an example see https://wiki.archlinux.org/title/Power_ … therboards

Edit: the proc/acpi/wakeup settigns will most likely not survive S4

Last edited by seth (2023-12-09 08:26:40)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#12 2023-12-09 08:53:25

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

I have rebooted, and tried everything I did before, and it won't hibernate again. I believe the reason lies in the weird fact that now these two devices in wakeup can't be disabled regardless how many times I try to echo:

PXSX	 S4	*enabled   pci:0000:02:00.0
XHCI	 S3	*enabled   pci:0000:00:14.0

Offline

#13 2023-12-09 09:50:15

Fustigate
Member
Registered: 2023-11-01
Posts: 11

Re: Computer hibernates and immediately turns itself back on

It worked again... SO WEIRD! after some time PXSX and XHCI were able to be disabled again. I don't know how to reproduce.

Here is the new journal I got right after it worked:

https://0x0.st/H3QP.txt

Offline

#14 2023-12-09 16:27:48

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 76,048

Re: Computer hibernates and immediately turns itself back on

XHCI is USB for sure, PXSX probably as well.

lspci -knn
lsusb -tv

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB