Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Unexpected wakeups

If none of the specific sub-forums seem right for your thread, ask here.
Post Reply
Message
Author
troffasky
Posts: 37
Joined: 2017-11-05 11:00
Has thanked: 1 time
Been thanked: 1 time

Unexpected wakeups

#1 Post by troffasky »

Debian SID on a generic desktop.
Installed a bunch of updates at the weekend, since then, my desktop is waking itself up unexpectedly. Yesterday I suspended it around 2220, and it woke up at 0200. Today I suspended it at 0933 and it woke up at 1648. The journalctl entries aren't timestamped in chronological order, but I assume they're written in chronological order. I am not exactly clear where suspend ends and resume begins in here, either.
What might be causing this?

Code: Select all

Sep 14 09:33:30 binky systemd-logind[1360]: Removed session 333.
Sep 14 16:48:16 binky kernel: (NULL device *): firmware: direct-loading firmware regulatory.db
Sep 14 16:48:24 binky kernel: (NULL device *): firmware: direct-loading firmware regulatory.db.p7s
Sep 14 16:48:24 binky kernel: Freezing user space processes ... (elapsed 0.002 seconds) done.
Sep 14 16:48:24 binky kernel: OOM killer disabled.
Sep 14 16:48:24 binky kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Sep 14 16:48:24 binky kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Sep 14 16:48:24 binky kernel: r8169 0000:04:00.0 eth0: Link is Down
Sep 14 16:48:24 binky kernel: serial 00:07: disabled
Sep 14 16:48:24 binky kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache
Sep 14 16:48:24 binky kernel: sd 1:0:0:0: [sda] Stopping disk
Sep 14 16:48:24 binky kernel: ACPI: Preparing to enter system sleep state S3
Sep 14 16:48:24 binky kernel: PM: Saving platform NVS memory
Sep 14 16:48:24 binky kernel: Disabling non-boot CPUs ...
Sep 14 16:48:24 binky kernel: smpboot: CPU 1 is now offline
Sep 14 16:48:24 binky kernel: smpboot: CPU 2 is now offline
Sep 14 16:48:24 binky kernel: smpboot: CPU 3 is now offline
Sep 14 16:48:24 binky kernel: ACPI: Low-level resume complete
Sep 14 16:48:24 binky kernel: PM: Restoring platform NVS memory
Sep 14 16:48:24 binky kernel: LVT offset 0 assigned for vector 0x400
Sep 14 16:48:24 binky kernel: Enabling non-boot CPUs ...
Sep 14 16:48:24 binky kernel: x86: Booting SMP configuration:
Sep 14 16:48:24 binky kernel: smpboot: Booting Node 0 Processor 1 APIC 0x11
Sep 14 16:48:24 binky kernel: microcode: CPU1: patch_level=0x06003106
Sep 14 16:48:24 binky kernel: ACPI: \_PR_.P001: Found 2 idle states
Sep 14 16:48:24 binky kernel: CPU1 is up
Sep 14 16:48:24 binky kernel: smpboot: Booting Node 0 Processor 2 APIC 0x12
Sep 14 16:48:24 binky kernel: microcode: CPU2: patch_level=0x06003106
Sep 14 16:48:24 binky kernel: ACPI: \_PR_.P002: Found 2 idle states
Sep 14 16:48:24 binky kernel: CPU2 is up
Sep 14 16:48:24 binky kernel: smpboot: Booting Node 0 Processor 3 APIC 0x13
Sep 14 16:48:24 binky kernel: microcode: CPU3: patch_level=0x06003106
Sep 14 16:48:24 binky kernel: ACPI: \_PR_.P003: Found 2 idle states
Sep 14 16:48:24 binky kernel: CPU3 is up
Sep 14 16:48:24 binky kernel: ACPI: Waking up from system sleep state S3
Sep 14 16:48:24 binky kernel: serial 00:07: activated
Sep 14 16:48:24 binky kernel: sd 1:0:0:0: [sda] Starting disk
Sep 14 16:48:24 binky kernel: r8169 0000:04:00.0 eth0: Link is Down
Sep 14 16:48:24 binky kernel: ata4: SATA link down (SStatus 0 SControl 300)
Sep 14 16:48:24 binky kernel: ata5: SATA link down (SStatus 0 SControl 300)
Sep 14 16:48:24 binky kernel: ata6: SATA link down (SStatus 0 SControl 300)
Sep 14 16:48:24 binky kernel: ata1: SATA link down (SStatus 0 SControl 300)
Sep 14 16:48:24 binky kernel: usb 5-2: reset full-speed USB device number 5 using ohci-pci
Sep 14 16:48:24 binky kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Sep 14 16:48:24 binky kernel: ata3.00: configured for UDMA/100
Sep 14 16:48:24 binky kernel: OOM killer enabled.
Sep 14 16:48:24 binky kernel: Restarting tasks ... done.
Sep 14 16:48:24 binky kernel: PM: suspend exit
Sep 14 16:48:24 binky kernel: r8169 0000:04:00.0 eth0: Link is Up - 1Gbps/Full - flow control off
Sep 14 16:48:24 binky kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Sep 14 16:48:24 binky kernel: ata2.00: configured for UDMA/100
Sep 14 16:48:16 binky systemd[1]: Started Run anacron jobs.
Sep 14 16:48:16 binky dhclient[1620]: PRC: Renewing lease on eth0.
Sep 14 16:48:16 binky systemd[1]: Condition check resulted in Snapshot ZFS filesystems being skipped.
Sep 14 16:48:16 binky dhclient[1620]: PRC: Rebinding lease on eth0.
Sep 14 16:48:16 binky systemd[1]: Condition check resulted in Prune ZFS snapshots being skipped.
Sep 14 16:48:16 binky dhclient[1620]: XMT: Rebind on eth0, interval 10060ms.
Sep 14 16:48:16 binky systemd-sleep[247582]: System resumed.
Sep 14 16:48:16 binky anacron[247644]: Anacron 2.3 started on 2021-09-14
Sep 14 16:48:16 binky systemd[1]: anacron.service: Succeeded.
Sep 14 16:48:16 binky anacron[247644]: Normal exit (0 jobs run)
Sep 14 16:48:16 binky systemd[1]: Condition check resulted in fan speed regulator being skipped.
Sep 14 16:48:16 binky acpid[1348]: client 1776[0:0] has disconnected
Sep 14 16:48:16 binky systemd[1]: systemd-suspend.service: Succeeded.
Sep 14 16:48:16 binky acpid[1348]: client connected from 1776[0:0]
Sep 14 16:48:16 binky systemd[1]: Finished Suspend.
Sep 14 16:48:16 binky acpid[1348]: 1 client rule loaded
Sep 14 16:48:16 binky systemd[1]: Stopped target Sleep.
Sep 14 16:48:16 binky systemd[1]: Reached target Suspend.
Sep 14 16:48:16 binky systemd[1]: Stopped target Suspend.
Sep 14 16:48:16 binky systemd-logind[1360]: Operation 'sleep' finished.
Sep 14 16:48:16 binky NetworkManager[1354]: <info>  [1631634496.6547] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Sep 14 16:48:18 binky NetworkManager[1354]: <info>  [1631634498.7944] device (eth0): carrier: link connected
Sep 14 16:48:24 binky kernel: NFS: __nfs4_reclaim_open_state: Lock reclaim failed!
Sep 14 16:48:24 binky kernel: NFS: __nfs4_reclaim_open_state: Lock reclaim failed!
Sep 14 16:48:26 binky dhclient[1620]: XMT: Rebind on eth0, interval 19960ms.
Sep 14 16:48:26 binky dhclient[1620]: RCV: Reply message on eth0 from fe80::94de:51ff:fe93:bf87.
Sep 14 16:48:35 binky sshd[247689]: Accepted publickey for alex from 192.168.1.78 port 57196 ssh2: RSA SHA256:6fCSx5DOtqbKGJBRThI571cZeEdP6S+EpjbJ0Th8M4U
Sep 14 16:48:35 binky sshd[247689]: pam_unix(sshd:session): session opened for user alex(uid=1000) by (uid=0)


mm3100
Posts: 336
Joined: 2020-10-21 21:39
Has thanked: 8 times
Been thanked: 13 times

Re: Unexpected wakeups

#2 Post by mm3100 »

Can you check what devices can wake up your system?
cat /proc/acpi/wakeup

troffasky
Posts: 37
Joined: 2017-11-05 11:00
Has thanked: 1 time
Been thanked: 1 time

Re: Unexpected wakeups

#3 Post by troffasky »

Some of these I can guess ["PS/2 keyboard"?] but the rest are a mystery!

Code: Select all

$ cat /proc/acpi/wakeup 
Device  S-state   Status   Sysfs node
PB21      S4    *enabled   pci:0000:00:02.1
PB22      S4    *disabled
PB31      S4    *disabled
PB32      S4    *disabled
PB33      S4    *disabled
PB34      S4    *disabled
SBAZ      S4    *disabled  pci:0000:00:14.2
ECIR      S4    *disabled
PS2K      S4    *disabled
PS2M      S4    *disabled
UAR1      S4    *disabled  pnp:00:07
OHC1      S4    *enabled   pci:0000:00:12.0
EHC1      S4    *enabled   pci:0000:00:12.2
OHC2      S4    *enabled   pci:0000:00:13.0
EHC2      S4    *enabled   pci:0000:00:13.2
OHC3      S4    *disabled
EHC3      S4    *disabled
OHC4      S4    *disabled
XHC0      S4    *enabled   pci:0000:00:10.0
XHC1      S4    *disabled
PE21      S4    *disabled
PE22      S4    *enabled   pci:0000:00:15.2
RLAN      S4    *disabled  pci:0000:04:00.0
PE23      S4    *disabled
PE20      S4    *enabled   pci:0000:00:15.0
P0PC      S4    *disabled  pci:0000:00:14.4

mm3100
Posts: 336
Joined: 2020-10-21 21:39
Has thanked: 8 times
Been thanked: 13 times

Re: Unexpected wakeups

#4 Post by mm3100 »

You can check with lspci what are those devices. Just look at last 3 fields of
OHC1 S4 *enabled pci:0000:00:12.0
EHC1 S4 *enabled pci:0000:00:12.2
OHC2 S4 *enabled pci:0000:00:13.0
They will be names as such in lspci. So EHC1 will be described by 00:12.2.

troffasky
Posts: 37
Joined: 2017-11-05 11:00
Has thanked: 1 time
Been thanked: 1 time

Re: Unexpected wakeups

#5 Post by troffasky »

Code: Select all

00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Kaveri P2P Bridge for GFX PCIe Port [1:0]
00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 09)
00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11)
00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11)
00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0)
00:15.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 2)
I can live with only using the power button to wake it up, so for now, I have attempted to disable everything with

Code: Select all

$ for i in `grep enabled /proc/acpi/wakeup | awk '{ print $1 }'`
> do echo $i > /proc/acpi/wakeup
> done
and will see in the morning if it woke itself up again.

mm3100
Posts: 336
Joined: 2020-10-21 21:39
Has thanked: 8 times
Been thanked: 13 times

Re: Unexpected wakeups

#6 Post by mm3100 »

I had odd issues with my laptop were turning lights or anything in same room with laptop would turn it on. I followed it to usb devices, it seemed that small voltage changes on input would cause variation to usb device which would then be registered as wakeup request. I solved it by disabling all by power button. Had that issue on windows for years, so it was rather nice to have that 'fixed'. I hope it will solve it for you.

Only issue is that it will go back to default after restart, for that you will need to create script to disable them all on startup.

troffasky
Posts: 37
Joined: 2017-11-05 11:00
Has thanked: 1 time
Been thanked: 1 time

Re: Unexpected wakeups

#7 Post by troffasky »

It didn't wake up over night, for the first time since Sunday.

Post Reply