You are not logged in.

#1 2022-04-21 06:20:55

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Changes to /proc/acpi/wakeup dont have any effect

Hi. Ive got a problem with my wireless mouse and keyboard constantly waking up my computer from sleep.
Previously i was using Linux Mint and i just disabled wakeup by XHC0 in /proc/acpi/wakeup, fixing the problem - i was only able to wake the computer by pressing the button on the case, but no accidental wakeups overnight.
Now i have migrated to Arch Linux and tried doing the same, but any changes i make to /proc/acpi/wakeup dont have any effect. In fact, i have made a script which disables wakeup by *all* devices on the boot-time, but my computer is still getting woken up by a keypress or mouse movement:

[dinth@dinth-desktop ~]$ cat /proc/acpi/wakeup
Device	S-state	  Status   Sysfs node
GPP0	  S4	*disabled  pci:0000:00:01.1
GPP2	  S4	*disabled
GPP3	  S4	*disabled
GPP4	  S4	*disabled
GPP5	  S4	*disabled
GPP6	  S4	*disabled
GPP7	  S4	*disabled
GPP8	  S4	*disabled  pci:0000:00:03.1
GPP9	  S4	*disabled
GPPA	  S4	*disabled
GPPB	  S4	*disabled
GPPC	  S4	*disabled
GPPD	  S4	*disabled
GPPE	  S4	*disabled
GPPF	  S4	*disabled
GP10	  S4	*disabled
GP11	  S4	*disabled
GP12	  S4	*disabled  pci:0000:00:07.1
GP13	  S4	*disabled  pci:0000:00:08.1
XHC0	  S4	*disabled  pci:0000:0c:00.3
GP30	  S4	*disabled
GP31	  S4	*disabled
PS2K	  S3	*disabled
BXBR	  S4	*disabled  pci:0000:00:01.2

What should i do to make changes /proc/acpi/wakeup take effect?

Offline

#2 2022-04-21 11:44:30

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,399

Re: Changes to /proc/acpi/wakeup dont have any effect

It does look like everything is disabled. I assume it's a USB wireless? Any systemd unit that could trigger this?
Have you checked your BIOS if there's any switch there that could trigger wakeup?

What should i do to make changes /proc/acpi/wakeup take effect?

If you're getting the above output after reboot, then I would think the effects are effective and something else is triggering the wakeup which might not be even your mouse or keyboard.

Offline

#3 2022-04-21 11:53:15

dogknowsnx
Member
Registered: 2021-04-12
Posts: 334

Re: Changes to /proc/acpi/wakeup dont have any effect


Wayland.

"We are eternal, all this pain is an illusion" - Maynard James Keenan

Offline

#4 2022-04-21 14:19:37

seth
Member
Registered: 2012-09-03
Posts: 30,860

Re: Changes to /proc/acpi/wakeup dont have any effect

my computer is still getting woken up by a keypress or mouse movement

Is that positive knowledge? If you've left the system alone for a while but as soon as you touch your mose it wakes up and exactly then?
Or do you assume that from

accidental wakeups overnight

?
Do you get those "accidental wakeups" also when removing the wireless input? Can you wake the system with a wired mouse/keyboard?
Is the wireless input some proprietary usb dongle or via bluetooth?

Final question: how many parallel windows installations are there?

Online

#5 2022-04-21 16:11:50

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

d_fajardo wrote:

Have you checked your BIOS if there's any switch there that could trigger wakeup?

There's almost no power saving options in BIOS. This is one of those "high performance" mobos, with five screens of CPU fine tuning options, but power saving is limited to just 3 items or so.

If you're getting the above output after reboot, then I would think the effects are effective and something else is triggering the wakeup which might not be even your mouse or keyboard.

Yep, i have made those settings persistent with a systemd script. The problem is that disabling ACPI wakeup events simply doesnt work on my installation of Archlinux. What else could trigger a wakeup exactly when i press a key on the keyboard?

seth wrote:

Is that positive knowledge? If you've left the system alone for a while but as soon as you touch your mose it wakes up and exactly then?

Yes. Touch a mouse or press a key.

Is the wireless input some proprietary usb dongle or via bluetooth?

Both are wireless proprietary usb dongles (respectively Logitech Unify and Logitech Lightspeed dongles)

Do you get those "accidental wakeups" also when removing the wireless input?

TBH i havent tried that yet, but disabling ACPI wakeups just on XHC0 on Linux Mint was preventing both my mouse and keyboard from waking up the computer (and also no more accidental overnight wakeups)

Last edited by Dinth (2022-04-21 16:13:51)

Offline

#6 2022-04-21 18:39:15

seth
Member
Registered: 2012-09-03
Posts: 30,860

Re: Changes to /proc/acpi/wakeup dont have any effect

1. do you use solaar?
2. Just a hunch: try to disable usb-autosuspend, https://wiki.archlinux.org/title/Power_ … utosuspend (try broadly w/ "usbcore.autosuspend=-1", you can narrow that down to the device if it works - also nb. that userspace tools like TLP will alter that value at runtime and you must configure the behavior there/as well)

Online

#7 2022-04-22 05:44:18

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

seth wrote:

1. do you use solaar?

Not at the moment, i forgot to install it after migration to Arch. Will do that now.

2. Just a hunch: try to disable usb-autosuspend

Also i will try this

Offline

#8 2022-04-22 19:18:11

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

Unfortunately no luck, i have disabled autosuspend and installed Solaar - doesnt make any difference

Offline

#9 2022-04-23 06:03:14

seth
Member
Registered: 2012-09-03
Posts: 30,860

Re: Changes to /proc/acpi/wakeup dont have any effect

Did you create and assign yourself to the solaar group and make sure the udev rule as been applied, https://wiki.archlinux.org/title/Logite … stallation

Though, frankly, this is about the ACPI and I don't see how the usb could still trigger a wakeup.

lspci; lsusb -tv

Online

#10 2022-04-23 07:23:14

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

So what may be the reason why ACPI settings are not affecting the system? I could understand on an older installation after a couple of years of tinkering with a system such things can happen, but this is a brand new installation. And the kernel is talking with the system via ACPI because it does show for example a list of interfaces.

Offline

#11 2022-04-23 16:41:05

seth
Member
Registered: 2012-09-03
Posts: 30,860

Re: Changes to /proc/acpi/wakeup dont have any effect

Kernel bug where the acpi wakeup devices are simply not communicated to the BIOS.
I don't think this is very likely, but you could test the lts kernel.
Afaics you also haven't responded to the question whether there's a parallel windows installation.
Finally, please post the requested lspci/lsusb output so we can see whether the relevant hub is at all affected by the entry in the DSDT.

Online

#12 2022-04-23 17:58:23

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

seth wrote:

Kernel bug where the acpi wakeup devices are simply not communicated to the BIOS.
I don't think this is very likely, but you could test the lts kernel.
Afaics you also haven't responded to the question whether there's a parallel windows installation.
Finally, please post the requested lspci/lsusb output so we can see whether the relevant hub is at all affected by the entry in the DSDT.

Sorry i missed that. I've got one parallel Windows installation on a separate drive. But im not sure if it will affect anything in my circumstances because i havent booted up Windows since i installed Arch.

Regarding the lsusb output here it is:

[dinth-desktop default]# lspci; lsusb -tv
00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex
00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU
00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge
00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge
00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)
00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3
00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4
00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5
00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6
00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7
01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983
02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream
03:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
03:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge
04:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 01)
07:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
08:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
09:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)
0a:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] (rev a1)
0a:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1)
0b:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function
0c:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP
0c:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP
0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
0c:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
    |__ Port 2: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 05dc:ba08 Lexar Media, Inc. 
        |__ Port 1: Dev 4, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            ID 05dc:ba06 Lexar Media, Inc. 
        |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/3p, 5000M
            ID 05dc:ba0b Lexar Media, Inc. 
            |__ Port 3: Dev 11, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
                ID 05dc:ba0d Lexar Media, Inc. 
            |__ Port 1: Dev 8, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
                ID 05dc:ba0d Lexar Media, Inc. 
            |__ Port 2: Dev 10, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
                ID 05dc:ba0d Lexar Media, Inc. 
        |__ Port 3: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            ID 05dc:ba06 Lexar Media, Inc. 
        |__ Port 4: Dev 9, If 0, Class=Mass Storage, Driver=usb-storage, 5000M
            ID 05dc:ba02 Lexar Media, Inc. Workflow CFR1
    |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
        ID 05e3:0612 Genesys Logic, Inc. Hub
        |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M
            ID 05e3:0612 Genesys Logic, Inc. Hub
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 30, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 0424:2524 Microchip Technology, Inc. (formerly SMSC) USB MultiSwitch Hub
        |__ Port 4: Dev 31, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 056d:0002 EIZO Corp. HID Monitor Controls
    |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05dc:ba08 Lexar Media, Inc. 
        |__ Port 2: Dev 6, If 0, Class=Hub, Driver=hub/3p, 480M
            ID 05dc:ba0c Lexar Media, Inc. 
    |__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0610 Genesys Logic, Inc. Hub
        |__ Port 1: Dev 7, If 0, Class=Hub, Driver=hub/4p, 480M
            ID 05e3:0610 Genesys Logic, Inc. Hub
            |__ Port 2: Dev 8, If 0, Class=Human Interface Device, Driver=usbhid, 12M
                ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
            |__ Port 2: Dev 8, If 1, Class=Human Interface Device, Driver=usbhid, 12M
                ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
            |__ Port 2: Dev 8, If 2, Class=Chip/SmartCard, Driver=, 12M
                ID 1050:0407 Yubico.com Yubikey 4/5 OTP+U2F+CCID
            |__ Port 4: Dev 9, If 0, Class=Video, Driver=uvcvideo, 480M
                ID 046d:082d Logitech, Inc. HD Pro Webcam C920
            |__ Port 4: Dev 9, If 1, Class=Video, Driver=uvcvideo, 480M
                ID 046d:082d Logitech, Inc. HD Pro Webcam C920
            |__ Port 4: Dev 9, If 2, Class=Audio, Driver=snd-usb-audio, 480M
                ID 046d:082d Logitech, Inc. HD Pro Webcam C920
            |__ Port 4: Dev 9, If 3, Class=Audio, Driver=snd-usb-audio, 480M
                ID 046d:082d Logitech, Inc. HD Pro Webcam C920
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 3: Dev 7, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c53d Logitech, Inc. G631 Keyboard
    |__ Port 3: Dev 7, If 1, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c53d Logitech, Inc. G631 Keyboard
    |__ Port 3: Dev 7, If 2, Class=Human Interface Device, Driver=usbhid, 12M
        ID 046d:c53d Logitech, Inc. G631 Keyboard
    |__ Port 5: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
    |__ Port 5: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
        ID 8087:0029 Intel Corp. AX200 Bluetooth
    |__ Port 6: Dev 4, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0608 Genesys Logic, Inc. Hub
        |__ Port 1: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 12M
            ID 28de:1142 Valve Software Wireless Steam Controller
        |__ Port 1: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 12M
            ID 28de:1142 Valve Software Wireless Steam Controller
        |__ Port 1: Dev 5, If 2, Class=Human Interface Device, Driver=usbhid, 12M
            ID 28de:1142 Valve Software Wireless Steam Controller
        |__ Port 1: Dev 5, If 3, Class=Human Interface Device, Driver=usbhid, 12M
            ID 28de:1142 Valve Software Wireless Steam Controller
        |__ Port 1: Dev 5, If 4, Class=Human Interface Device, Driver=usbhid, 12M
            ID 28de:1142 Valve Software Wireless Steam Controller
        |__ Port 2: Dev 11, If 2, Class=Printer, Driver=usblp, 480M
            ID 413c:564a Dell Computer Corp. C1765 series Multifunction Color LaserPrinter, Scanner & Copier
        |__ Port 2: Dev 11, If 0, Class=Vendor Specific Class, Driver=, 480M
            ID 413c:564a Dell Computer Corp. C1765 series Multifunction Color LaserPrinter, Scanner & Copier
        |__ Port 2: Dev 11, If 1, Class=Printer, Driver=usblp, 480M
            ID 413c:564a Dell Computer Corp. C1765 series Multifunction Color LaserPrinter, Scanner & Copier
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
    ID 1d6b:0003 Linux Foundation 3.0 root hub
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
    ID 1d6b:0002 Linux Foundation 2.0 root hub
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
        ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller
    |__ Port 6: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M
        ID 05e3:0608 Genesys Logic, Inc. Hub
        |__ Port 3: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
            ID 10d5:5000 Uni Class Technology Co., Ltd 
        |__ Port 3: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
            ID 10d5:5000 Uni Class Technology Co., Ltd 

Offline

#13 2022-05-17 08:49:45

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

I still havent found a courage to try to downgrade the kernel, but i have been able to replicate the same behaviour with a completely fresh install of Archlinux

Offline

#14 2022-05-21 08:48:53

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

I have downgraded the kernel to LTS (5.15.7), but still have the same problem sad

Offline

#15 2022-05-23 20:16:16

seth
Member
Registered: 2012-09-03
Posts: 30,860

Re: Changes to /proc/acpi/wakeup dont have any effect

XHC0	  S4	*disabled  pci:0000:0c:00.3

is only

0c:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

There're also

07:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller
07:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

Leavign aside the apparenly external hub and the there attached steam controller and printer… can you plug the input devices into a different USB slot (one that's marked as usb3) and not get this problem?

Online

#16 2022-05-25 06:09:39

Dinth
Member
From: London
Registered: 2009-03-02
Posts: 238

Re: Changes to /proc/acpi/wakeup dont have any effect

Hi. Yes, i do have an external hub with bits and pieces like Yubikey and a webcam connected + i do have a KVM switch to which normally my keyboard and mouse are connected. Disabling XHC0 on Ubuntu was preventing the KVM connected keyboard and mouse from waking up the computer, so i wouldnt want to blame the KVM here.
Anyhow following your advice, i tried disabling XHC0 and connecting my keyboard to various ports on the motherboard (ones on the backplate, once on the USB3 headers) and it still wakes up the computer every single time.

Offline

Board footer

Powered by FluxBB