You are not logged in.

#1 2017-07-19 20:59:30

jufranz
Member
Registered: 2017-07-19
Posts: 2

[Solved] Why my computer is suspending?

Hey Folks,
I am having a hard time to figure out why my notebook is suspending. Its and old MacbookPro running with the lid closed: LXDE, Kodi, Plex, Home-Assistant and Mosquitto.
Kodi has no suspend option enabled, logind.conf has IdleAction set to ignore. When I am not playing media on kodi the computer suspends (at irregular intervals!). I have no idea where to still look for the config file that states that it should suspend...


Here is my dmesg containing the suspend/wake

[  642.623267] PM: Syncing filesystems ... done.
[  643.087290] PM: Preparing system for sleep (mem)
[  643.087539] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  643.088957] Freezing remaining freezable tasks ... (elapsed 6.964 seconds) done.
[  650.053247] PM: Suspending system (mem)
[  650.053269] Suspending console(s) (use no_console_suspend to debug)
[  650.054033] apple-gmux 00:04: System wakeup disabled by ACPI
[  650.054140] ACPI : EC: event blocked
[  650.057667] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[  650.057862] nouveau 0000:01:00.0: DRM: suspending console...
[  650.057866] nouveau 0000:01:00.0: DRM: suspending display...
[  650.059647] sd 0:0:0:0: [sda] Stopping disk
[  650.087667] nouveau 0000:01:00.0: DRM: evicting buffers...
[  650.743899] nouveau 0000:01:00.0: DRM: waiting for kernel channels to go idle...
[  650.743927] nouveau 0000:01:00.0: DRM: suspending fence...
[  650.744194] nouveau 0000:01:00.0: DRM: suspending object tree...
[  654.004311] PM: suspend of devices complete after 3950.799 msecs
[  654.020579] PM: late suspend of devices complete after 16.260 msecs
[  654.020933] ACPI : EC: interrupt blocked
[  654.021460] tg3 0000:02:00.0: System wakeup enabled by ACPI
[  654.021635] ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
[  654.021792] ehci-pci 0000:00:1a.7: System wakeup enabled by ACPI
[  654.053786] PM: noirq suspend of devices complete after 33.203 msecs
[  654.054210] ACPI: Preparing to enter system sleep state S3
[  654.055918] ACPI : EC: EC stopped
[  654.055919] PM: Saving platform NVS memory
[  654.055929] Disabling non-boot CPUs ...
[  654.081963] smpboot: CPU 1 is now offline
[  654.101779] smpboot: CPU 2 is now offline
[  654.128418] smpboot: CPU 3 is now offline
[  654.129630] ACPI: Low-level resume complete
[  654.129694] ACPI : EC: EC started
[  654.129694] PM: Restoring platform NVS memory
[  654.130028] Suspended for 52.179 seconds
[  654.130060] Enabling non-boot CPUs ...
[  654.130105] x86: Booting SMP configuration:
[  654.130105] smpboot: Booting Node 0 Processor 1 APIC 0x1
[  654.130388] Disabled fast string operations
[  654.132600]  cache: parent cpu1 should not be sleeping
[  654.132840] CPU1 is up
[  654.132874] smpboot: Booting Node 0 Processor 2 APIC 0x4
[  654.133373] Disabled fast string operations
[  654.142488]  cache: parent cpu2 should not be sleeping
[  654.170462] CPU2 is up
[  654.170491] smpboot: Booting Node 0 Processor 3 APIC 0x5
[  654.171078] Disabled fast string operations
[  654.182652]  cache: parent cpu3 should not be sleeping
[  654.220367] CPU3 is up
[  654.222644] ACPI: Waking up from system sleep state S3
[  654.652491] ACPI : EC: interrupt unblocked
[  654.671854] ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
[  654.671856] ehci-pci 0000:00:1a.7: System wakeup disabled by ACPI
[  654.691902] PM: noirq resume of devices complete after 40.084 msecs
[  654.691939] pciehp 0000:00:1c.2:pcie004: Slot(2): Link Up
[  654.691950] pciehp 0000:00:1c.1:pcie004: Slot(1-1): Link Up
[  654.691959] pciehp 0000:00:1c.0:pcie004: Slot(0): Link Up
[  654.693983] PM: early resume of devices complete after 2.059 msecs
[  654.694043] ACPI : EC: event unblocked
[  654.694096] ACPI : button: The lid device is not compliant to SW_LID.

And here is the journalctl:

Jul 19 17:43:04 franz-mbpro hass[421]: 2017-07-19 17:43:04 INFO (SyncWorker_19) [homeassistant.components.device_tracker.nmap_tracker] No MAC address found for 192.168.1.11
Jul 19 17:43:05 franz-mbpro hass[421]: 2017-07-19 17:43:04 INFO (SyncWorker_19) [homeassistant.components.device_tracker.nmap_tracker] nmap scan successful
Jul 19 17:43:15 franz-mbpro hass[421]: 2017-07-19 17:43:15 INFO (SyncWorker_15) [plexapi] GET redacted
Jul 19 17:43:15 franz-mbpro hass[421]: 2017-07-19 17:43:15 INFO (SyncWorker_15) [plexapi] GET redacted
Jul 19 17:43:18 franz-mbpro systemd-logind[320]: Suspending...
Jul 19 17:43:18 franz-mbpro systemd[1]: Reached target Sleep.
Jul 19 17:43:18 franz-mbpro systemd[1]: Starting Suspend...
Jul 19 17:43:18 franz-mbpro systemd-sleep[1705]: Suspending system...
Jul 19 17:44:23 franz-mbpro kernel: PM: Syncing filesystems ... done.
Jul 19 17:44:24 franz-mbpro kernel: PM: Preparing system for sleep (mem)
Jul 19 17:44:24 franz-mbpro kernel: Freezing user space processes ... (elapsed 0.001 seconds) done.
Jul 19 17:44:24 franz-mbpro kernel: Freezing remaining freezable tasks ... (elapsed 6.964 seconds) done.
Jul 19 17:44:24 franz-mbpro kernel: PM: Suspending system (mem)
Jul 19 17:44:24 franz-mbpro kernel: Suspending console(s) (use no_console_suspend to debug)

Does anyone have a suggestion on where to look?

Cheers!

Last edited by jufranz (2017-07-21 16:42:24)

Offline

#2 2017-07-20 05:44:22

seth
Member
Registered: 2012-09-03
Posts: 49,960

Re: [Solved] Why my computer is suspending?

acpid?
running out of battery?
xautolock?

Also there's a redacted GET from (likely?) Kodi and only 3 seconds later the system suspends? Highly suspicious.
In general, look at dmesg and journal for patterns, ie. at several sleep cycles - what's happening all the time (aside the sleep) and what's just noise?

Online

#3 2017-07-21 12:17:39

jufranz
Member
Registered: 2017-07-19
Posts: 2

Re: [Solved] Why my computer is suspending?

The computer is always connected to the power supply, no xautolock.
But I've figure it out smile

Apparently when I turned the TV the machine sensed it though the HDMI -> DP adapter which I thought it was impossible. Because of that systemd considered that the computer was not in docked mode anymore.
Solved by setting HandleLidSwitch to ignore on logind.conf

Cheers

Offline

Board footer

Powered by FluxBB