[Solved] First suspend doesn't work but second yes.

Anarconda · 2024-11-20 20:25:59

Hi, I'd appreciate it if someone can be pointing me on how to solve the problem mentioned in the subject.

A more elaborated explanation would be: if I try to suspend by clicking in a menu option or in CLI sending a 'systemd.suspend' it doesn't work, the system immediately resumes. But if I let the system alone for ten minutes (that's the period configured in KDE) the first attempt to suspend doesn't work (resume immediately) but the second one (ten minutes later) works as expected.

The journal: http://0x0.st/XnWQ.txt

In the journal we can see:

a) 11:07:51 Gaia-A systemd-logind[917]: The system will suspend now! -> This is the first attempt to suspend after ten minutes doing nothing.

b) nov 20 11:08:04 Gaia-A kernel: ACPI: PM: Low-level resume complete -> System up again.

c) nov 20 11:18:03 Gaia-A systemd-logind[917]: The system will suspend now! -> Ten minutes after a new 'suspend'

d) nov 20 11:18:03 Gaia-A kernel: PM: suspend entry (deep) -> This time it works.
nov 20 12:45:48 Gaia-A kernel: Filesystems sync: 0.008 seconds -> The system resume when I wanted without any problem.

The computer has a mainboard Asus ROG STRIX X870E-E GAMING WIFI with the latest BIOS firmware, and I'm using a 6.12 from AUR because of the net card (Realtek 8126).

Any information you think is necessary, don't hesitate to ask.

Thanks in advance for your time and help.

Last edited by Anarconda (2024-11-21 23:16:58)

seth · 2024-11-20 21:43:35

nov 20 09:49:02 Gaia-A kernel:  nvme0n1: p1 p2 p3 p4 p5
nov 20 09:49:02 Gaia-A kernel: nvme nvme2: 16/0/0 default/read/poll queues
nov 20 09:49:02 Gaia-A kernel: nvme nvme1: 32/0/0 default/read/poll queues
nov 20 09:49:02 Gaia-A kernel:  nvme2n1: p1
nov 20 09:49:02 Gaia-A kernel:  nvme1n1: p1 p2

How many parallel windows installations are there?

Anarconda · 2024-11-20 21:46:13

@seth Just one in nvme0n1 (p1,p2,p3,p4) in nvme0n1p5 is Arch and for the others NVMe: one is another Arch Linux install and three are for storage.

Last edited by Anarconda (2024-11-20 21:48:43)

seth · 2024-11-20 21:47:58

Yeah, was a trick question…
See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons (this is meant seriously)

Anarconda · 2024-11-20 21:50:45

seth wrote:

See the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!)

Fast boot in BIOS is off. I'll take a look in windows to see if I can find any option for "Fast Boot".

Thank you.

seth · 2024-11-20 21:52:11

The feature is called "fast start" and is hibernation in disguise, please follow the link - it's explained there.
The BIOS setting is, as mentioned, irrelevant.

Anarconda · 2024-11-20 22:01:41

seth wrote:

The feature is called "fast start" and is hibernation in disguise, please follow the link - it's explained there.
The BIOS setting is, as mentioned, irrelevant.

Thanks again. Yes, I found it in Control Panel, Hibernation.

And, against my convictions, re-started twice. Unfortunately, when I clicked on "suspend" restarted immediately.

seth · 2024-11-21 16:35:38

Since the system didn't wake "immediately" but after 12 seconds, there's probably some spurious trigger.

lsusb
cat /proc/acpi/wakeup

You can also try to disable APTS, https://wiki.archlinux.org/title/Solid_ … leshooting
But there's no strong indication for that kind of problem in the log.

Anarconda · 2024-11-21 16:41:38

└──> ~ $  lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 152a:8750 Thesycon Systemsoftware & Consulting GmbH E70 Velvet
Bus 001 Device 003: ID 0489:e13a Foxconn / Hon Hai Wireless_Device
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 174c:2074 ASMedia Technology Inc. ASM1074 High-Speed hub
Bus 003 Device 003: ID 174c:2174 ASMedia Technology Inc. ASMT2307
Bus 003 Device 004: ID 0b05:1b9b ASUSTek Computer, Inc. USB Audio
Bus 003 Device 005: ID 0b05:1aa6 ASUSTek Computer, Inc. AURA LED Controller
Bus 003 Device 006: ID 1532:0243 Razer USA, Ltd Huntsman Tournament Edition
Bus 003 Device 007: ID 046d:c548 Logitech, Inc. Logi Bolt Receiver
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 002: ID 174c:3074 ASMedia Technology Inc. ASM1074 SuperSpeed hub
Bus 004 Device 003: ID 174c:3174 ASMedia Technology Inc. ASMT2307
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
└──> ~ $

└──> ~ $  cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
GPP3      S4    *enabled   pci:0000:00:01.4
GP17      S4    *enabled   pci:0000:00:08.1
XHC0      S4    *enabled   pci:0000:7d:00.3
XHC1      S4    *enabled   pci:0000:7d:00.4
XHC2      S4    *enabled   pci:0000:7e:00.0
GPP0      S4    *enabled   pci:0000:00:01.1
SWUS      S4    *enabled   pci:0000:01:00.0
SWDS      S4    *enabled   pci:0000:02:00.0
GPP2      S4    *enabled   pci:0000:00:01.3
GPP7      S4    *enabled   pci:0000:00:02.1
UP00      S4    *enabled   pci:0000:07:00.0
DP00      S4    *enabled   pci:0000:08:00.0
NV00      S4    *disabled  pci:0000:09:00.0
DP08      S4    *disabled
EP00      S4    *disabled
DP10      S4    *disabled
WN00      S4    *disabled
DP18      S4    *disabled
LN00      S4    *disabled
DP20      S4    *disabled
NV00      S4    *disabled
DP28      S4    *disabled
EP00      S4    *disabled
DP30      S4    *disabled
EP00      S4    *disabled
DP38      S4    *disabled
EP00      S4    *disabled
DP40      S4    *enabled   pci:0000:08:08.0
UP00      S4    *enabled   pci:0000:0a:00.0
DP00      S4    *enabled   pci:0000:0b:00.0
NV00      S4    *disabled  pci:0000:0c:00.0
DP08      S4    *disabled
EP00      S4    *disabled
DP10      S4    *disabled
WN00      S4    *disabled
DP18      S4    *disabled
LN00      S4    *disabled
DP20      S4    *enabled   pci:0000:0b:04.0
NV00      S4    *disabled  pci:0000:0d:00.0
DP28      S4    *disabled
EP00      S4    *disabled
DP30      S4    *enabled   pci:0000:0b:06.0
EP00      S4    *disabled  pci:0000:0e:00.0
DP38      S4    *enabled   pci:0000:0b:07.0
EP00      S4    *disabled
DP40      S4    *enabled   pci:0000:0b:08.0
EP00      S4    *disabled
DP48      S4    *disabled
EP00      S4    *disabled
DP50      S4    *disabled
EP00      S4    *disabled
DP58      S4    *disabled
EP00      S4    *disabled
DP60      S4    *enabled   pci:0000:0b:0c.0
XH00      S4    *enabled   pci:0000:11:00.0
DP68      S4    *enabled   pci:0000:0b:0d.0
SA00      S4    *disabled  pci:0000:12:00.0
DP48      S4    *disabled
EP00      S4    *disabled
DP50      S4    *disabled
EP00      S4    *disabled
DP58      S4    *disabled
EP00      S4    *disabled
DP60      S4    *enabled   pci:0000:08:0c.0
XH00      S4    *enabled   pci:0000:13:00.0
DP68      S4    *enabled   pci:0000:08:0d.0
SA00      S4    *disabled  pci:0000:14:00.0
GPP8      S4    *enabled   pci:0000:00:02.2
U4UP      S4    *enabled   pci:0000:15:00.0
U4P0      S4    *enabled   pci:0000:16:00.0
UP0D      S4    *disabled
U4P1      S4    *enabled   pci:0000:16:01.0
UP1D      S4    *disabled
U4P2      S4    *enabled   pci:0000:16:02.0
UXHC      S4    *enabled   pci:0000:7b:00.0
U4P3      S4    *enabled   pci:0000:16:03.0
UHI0      S4    *enabled   pci:0000:7c:00.0
└──> ~ $

I took a look at this too, but what I don't understand is why it works the second time.

Thanks for your interest.

Anarconda · 2024-11-21 16:50:56

I forgot to mention two probably not relevant things:

1. It works the second time when the machine is suspended automatically, not by my actions (I mean if I select in the menu suspend twice or thrice it doesn't work).
2. I tried linuz-zen 6.12 from Extra/Testing with the sames results.

seth · 2024-11-21 22:16:18

'key - my money would be on the wireless input devices, because those will power down at some point and stop sending input until you touch them.

If that's not it, disable all wakeup devices by writing the 4-letter code into /proc/acpi/wakeup

awk '/enabled/ {print $1; exit}' /proc/acpi/wakeup | sudo tee /proc/acpi/wakeup

will flip the first enabled device.

Then see whether you can suspend the system (manually)
If yes, you'll have to bisect this until you found the culprit.
Currently you've

GPP3      S4    *enabled   pci:0000:00:01.4
GP17      S4    *enabled   pci:0000:00:08.1
XHC0      S4    *enabled   pci:0000:7d:00.3
XHC1      S4    *enabled   pci:0000:7d:00.4
XHC2      S4    *enabled   pci:0000:7e:00.0
GPP0      S4    *enabled   pci:0000:00:01.1
SWUS      S4    *enabled   pci:0000:01:00.0
SWDS      S4    *enabled   pci:0000:02:00.0
GPP2      S4    *enabled   pci:0000:00:01.3
GPP7      S4    *enabled   pci:0000:00:02.1
UP00      S4    *enabled   pci:0000:07:00.0
DP00      S4    *enabled   pci:0000:08:00.0
DP40      S4    *enabled   pci:0000:08:08.0
UP00      S4    *enabled   pci:0000:0a:00.0
DP00      S4    *enabled   pci:0000:0b:00.0
DP20      S4    *enabled   pci:0000:0b:04.0
DP30      S4    *enabled   pci:0000:0b:06.0
DP38      S4    *enabled   pci:0000:0b:07.0
DP40      S4    *enabled   pci:0000:0b:08.0
DP60      S4    *enabled   pci:0000:0b:0c.0
XH00      S4    *enabled   pci:0000:11:00.0
DP68      S4    *enabled   pci:0000:0b:0d.0
DP60      S4    *enabled   pci:0000:08:0c.0
XH00      S4    *enabled   pci:0000:13:00.0
DP68      S4    *enabled   pci:0000:08:0d.0
GPP8      S4    *enabled   pci:0000:00:02.2
U4UP      S4    *enabled   pci:0000:15:00.0
U4P0      S4    *enabled   pci:0000:16:00.0
U4P1      S4    *enabled   pci:0000:16:01.0
U4P2      S4    *enabled   pci:0000:16:02.0
UXHC      S4    *enabled   pci:0000:7b:00.0
U4P3      S4    *enabled   pci:0000:16:03.0
UHI0      S4    *enabled   pci:0000:7c:00.0

Anarconda · 2024-11-21 22:27:32

Ok. I'll try that and come back with the results.

Anyway, if I'm not mistaken, the wireless device is a MediaTek 7927 (both Wi-Fi and Bluetooth) and there isn't a Linux driver for that. Without a driver, can they do something here?

V1del · 2024-11-21 22:30:20

He's not referring to your wifi card, but the logitech receiver and the like.

Anarconda · 2024-11-21 22:44:56

V1del wrote:

He's not referring to your wifi card, but the logitech receiver and the like.

That makes sense for me. Thanks.

Anarconda · 2024-11-21 23:00:40

I'm back. The winner is the Logitech receiver (bolt) when disconnected suspend works as expected.

Edit:
The problem with bolt receiver seems to be known from some time and after remove it from the machine all is working as expected. I'm marking this thread as solved.

Thank you very much.

Last edited by Anarconda (2024-11-21 23:16:37)

Anarconda · 2024-11-22 00:54:32

I found this udev rule in reddit that inhibit the Logitech Bolt receiver to wakeup the system and it works:

ACTION=="add", SUBSYSTEM=="usb", DRIVERS=="usb", ATTRS{idVendor}=="046d", ATTRS{idProduct}=="c548", ATTR{power/wakeup}="disabled"

The problem is no device conected to this receiver will resume the system anymore. Not a big problem for me as only have a mouse.

Arch Linux

#1 2024-11-20 20:25:59

[Solved] First suspend doesn't work but second yes.

#2 2024-11-20 21:43:35

Re: [Solved] First suspend doesn't work but second yes.

#3 2024-11-20 21:46:13

Re: [Solved] First suspend doesn't work but second yes.

#4 2024-11-20 21:47:58

Re: [Solved] First suspend doesn't work but second yes.

#5 2024-11-20 21:50:45

Re: [Solved] First suspend doesn't work but second yes.

#6 2024-11-20 21:52:11

Re: [Solved] First suspend doesn't work but second yes.

#7 2024-11-20 22:01:41

Re: [Solved] First suspend doesn't work but second yes.

#8 2024-11-21 16:35:38

Re: [Solved] First suspend doesn't work but second yes.

#9 2024-11-21 16:41:38

Re: [Solved] First suspend doesn't work but second yes.

#10 2024-11-21 16:50:56

Re: [Solved] First suspend doesn't work but second yes.

#11 2024-11-21 22:16:18

Re: [Solved] First suspend doesn't work but second yes.

#12 2024-11-21 22:27:32

Re: [Solved] First suspend doesn't work but second yes.

#13 2024-11-21 22:30:20

Re: [Solved] First suspend doesn't work but second yes.

#14 2024-11-21 22:44:56

Re: [Solved] First suspend doesn't work but second yes.

#15 2024-11-21 23:00:40

Re: [Solved] First suspend doesn't work but second yes.

#16 2024-11-22 00:54:32

Re: [Solved] First suspend doesn't work but second yes.

Board footer