You are not logged in.

Pages: 1

#1 2016-10-19 01:19:23

Psykukumber
Member
From: Ukraine
Registered: 2016-10-19
Posts: 4
Website

Power manager settings ignored, system just suspend (emachines e355)

Hi all.

In last ~1.5 month i noticed that my power management settings is broken.

Earlier i set configuration like "close lid on battery -> suspend" and "close lid on AC power -> lock screen". But when i close laptop lid for now system goes to suspend, no matters, on AC or battery it still goes to suspend.

Firstly, i thought this is a problem in xfce4-power-manager but in lxqt and mate problem exists too.

Also i tried to edit logind.conf and set HandleLidSwitch=ignore. Then when i close lid, system not go to suspend when on battery.

Maybe anyone know how to fix this issue?

Offline

#2 2016-10-24 13:08:22

Drehstromlampe
Member
From: GER
Registered: 2015-07-18
Posts: 45

Re: Power manager settings ignored, system just suspend (emachines e355)

Sounds to me like xfce4-power-manager acpi-handling doesn't get applied.
What does the kernel-log tell?

Offline

#3 2016-10-24 17:57:27

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Power manager settings ignored, system just suspend (emachines e355)

Psykukumber wrote:

Also i tried to edit logind.conf and set HandleLidSwitch=ignore. Then when i close lid, system not go to suspend when on battery.

I think you have to set this as well:

LidSwitchIgnoreInhibited=no

However, I'm not feeling well at the moment and the man page is giving me a bad case of boolean overload so I may be wrong...
hmm

Can we also see the output of:

systemd-inhibit

Are you infected with Wetiko?

Offline

#4 2016-10-27 15:34:21

Psykukumber
Member
From: Ukraine
Registered: 2016-10-19
Posts: 4
Website

Re: Power manager settings ignored, system just suspend (emachines e355)

Drehstromlampe wrote:

Sounds to me like xfce4-power-manager acpi-handling doesn't get applied.
What does the kernel-log tell?

Something like this

psykukumber@pklaptop:[~]$ journalctl -f _TRANSPORT=kernel 
-- Logs begin at Mon 2016-01-04 10:45:02 EET. --
Oct 27 16:10:21 pklaptop kernel: ata1.00: configured for UDMA/133
Oct 27 16:10:21 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 16:10:21 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 16:10:34 pklaptop kernel: wlp2s0: authenticate with 04:8d:38:59:46:8b
Oct 27 16:10:34 pklaptop kernel: wlp2s0: send auth to 04:8d:38:59:46:8b (try 1/3)
Oct 27 16:10:34 pklaptop kernel: wlp2s0: authenticated
Oct 27 16:10:34 pklaptop kernel: wlp2s0: associate with 04:8d:38:59:46:8b (try 1/3)
Oct 27 16:10:34 pklaptop kernel: wlp2s0: RX AssocResp from 04:8d:38:59:46:8b (capab=0x411 status=0 aid=3)
Oct 27 16:10:34 pklaptop kernel: wlp2s0: associated
Oct 27 16:10:34 pklaptop kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
Oct 27 18:28:51 pklaptop kernel: wlp2s0: deauthenticating from 04:8d:38:59:46:8b by local choice (Reason: 3=DEAUTH_LEAVING)
Oct 27 18:28:52 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:04 pklaptop kernel: PM: Syncing filesystems ... done.
Oct 27 18:29:06 pklaptop kernel: PM: Preparing system for sleep (mem)
Oct 27 18:29:06 pklaptop kernel: Freezing user space processes ... (elapsed 0.143 seconds) done.
Oct 27 18:29:06 pklaptop kernel: Double checking all user space processes after OOM killer disable... (elapsed 0.000 seconds) 
Oct 27 18:29:06 pklaptop kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Oct 27 18:29:06 pklaptop kernel: PM: Suspending system (mem)
Oct 27 18:29:06 pklaptop kernel: Suspending console(s) (use no_console_suspend to debug)
Oct 27 18:29:06 pklaptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Oct 27 18:29:06 pklaptop kernel: sd 0:0:0:0: [sda] Stopping disk
Oct 27 18:29:06 pklaptop kernel: PM: suspend of devices complete after 803.990 msecs
Oct 27 18:29:06 pklaptop kernel: PM: late suspend of devices complete after 14.166 msecs
Oct 27 18:29:06 pklaptop kernel: uhci_hcd 0000:00:1d.2: System wakeup enabled by ACPI
Oct 27 18:29:06 pklaptop kernel: ehci-pci 0000:00:1d.7: System wakeup enabled by ACPI
Oct 27 18:29:06 pklaptop kernel: uhci_hcd 0000:00:1d.3: System wakeup enabled by ACPI
Oct 27 18:29:06 pklaptop kernel: uhci_hcd 0000:00:1d.0: System wakeup enabled by ACPI
Oct 27 18:29:06 pklaptop kernel: uhci_hcd 0000:00:1d.1: System wakeup enabled by ACPI
Oct 27 18:29:06 pklaptop kernel: PM: noirq suspend of devices complete after 16.893 msecs
Oct 27 18:29:07 pklaptop kernel: ACPI: Preparing to enter system sleep state S3
Oct 27 18:29:07 pklaptop kernel: ACPI : EC: EC stopped
Oct 27 18:29:07 pklaptop kernel: PM: Saving platform NVS memory
Oct 27 18:29:07 pklaptop kernel: Disabling non-boot CPUs ...
Oct 27 18:29:07 pklaptop kernel: smpboot: CPU 1 is now offline
Oct 27 18:29:07 pklaptop kernel: smpboot: CPU 2 is now offline
Oct 27 18:29:07 pklaptop kernel: smpboot: CPU 3 is now offline
Oct 27 18:29:07 pklaptop kernel: ACPI: Low-level resume complete
Oct 27 18:29:07 pklaptop kernel: ACPI : EC: EC started
Oct 27 18:29:07 pklaptop kernel: PM: Restoring platform NVS memory
Oct 27 18:29:07 pklaptop kernel: Enabling non-boot CPUs ...
Oct 27 18:29:07 pklaptop kernel: x86: Booting SMP configuration:
Oct 27 18:29:07 pklaptop kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Oct 27 18:29:07 pklaptop kernel: Initializing CPU#1
Oct 27 18:29:07 pklaptop kernel: Disabled fast string operations
Oct 27 18:29:07 pklaptop kernel: CPU1 is up
Oct 27 18:29:07 pklaptop kernel: smpboot: Booting Node 0 Processor 2 APIC 0x2
Oct 27 18:29:07 pklaptop kernel: Initializing CPU#2
Oct 27 18:29:07 pklaptop kernel: Disabled fast string operations
Oct 27 18:29:07 pklaptop kernel: CPU2 is up
Oct 27 18:29:07 pklaptop kernel: smpboot: Booting Node 0 Processor 3 APIC 0x3
Oct 27 18:29:07 pklaptop kernel: Initializing CPU#3
Oct 27 18:29:07 pklaptop kernel: Disabled fast string operations
Oct 27 18:29:07 pklaptop kernel: CPU3 is up
Oct 27 18:29:07 pklaptop kernel: ACPI: Waking up from system sleep state S3
Oct 27 18:29:07 pklaptop kernel: acpi LNXPOWER:00: Turning OFF
Oct 27 18:29:07 pklaptop kernel: uhci_hcd 0000:00:1d.0: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: uhci_hcd 0000:00:1d.1: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: uhci_hcd 0000:00:1d.2: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: uhci_hcd 0000:00:1d.3: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: ehci-pci 0000:00:1d.7: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: PM: noirq resume of devices complete after 15.485 msecs
Oct 27 18:29:07 pklaptop kernel: PM: early resume of devices complete after 0.843 msecs
Oct 27 18:29:07 pklaptop kernel: usb usb3: root hub lost power or was reset
Oct 27 18:29:07 pklaptop kernel: usb usb2: root hub lost power or was reset
Oct 27 18:29:07 pklaptop kernel: usb usb5: root hub lost power or was reset
Oct 27 18:29:07 pklaptop kernel: usb usb4: root hub lost power or was reset
Oct 27 18:29:07 pklaptop kernel: ath: phy0: ASPM enabled: 0x42
Oct 27 18:29:07 pklaptop kernel: sd 0:0:0:0: [sda] Starting disk
Oct 27 18:29:07 pklaptop kernel: rtc_cmos 00:01: System wakeup disabled by ACPI
Oct 27 18:29:07 pklaptop kernel: usb 1-4: reset high-speed USB device number 3 using ehci-pci
Oct 27 18:29:07 pklaptop kernel: ata2: SATA link down (SStatus 0 SControl 300)
Oct 27 18:29:07 pklaptop kernel: usb 2-1: reset full-speed USB device number 2 using uhci_hcd
Oct 27 18:29:07 pklaptop kernel: PM: resume of devices complete after 494.774 msecs
Oct 27 18:29:07 pklaptop kernel: usb 2-1:1.0: rebind failed: -517
Oct 27 18:29:08 pklaptop kernel: usb 2-1:1.1: rebind failed: -517
Oct 27 18:29:08 pklaptop kernel: PM: Finishing wakeup.
Oct 27 18:29:08 pklaptop kernel: Restarting tasks ... done.
Oct 27 18:29:08 pklaptop kernel: video LNXVIDEO:00: Restoring backlight state
Oct 27 18:29:08 pklaptop kernel: psmouse serio1: synaptics: queried max coordinates: x [..5612], y [..4618]
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:08 pklaptop kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Oct 27 18:29:08 pklaptop kernel: ata1.00: unexpected _GTF length (4)
Oct 27 18:29:08 pklaptop kernel: ata1.00: unexpected _GTF length (4)
Oct 27 18:29:08 pklaptop kernel: ata1.00: configured for UDMA/133
Oct 27 18:29:08 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:09 pklaptop kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Oct 27 18:29:12 pklaptop kernel: wlp2s0: authenticate with 04:8d:38:59:46:8b
Oct 27 18:29:12 pklaptop kernel: wlp2s0: send auth to 04:8d:38:59:46:8b (try 1/3)
Oct 27 18:29:12 pklaptop kernel: wlp2s0: authenticated
Oct 27 18:29:12 pklaptop kernel: wlp2s0: associate with 04:8d:38:59:46:8b (try 1/3)
Oct 27 18:29:12 pklaptop kernel: wlp2s0: RX AssocResp from 04:8d:38:59:46:8b (capab=0x411 status=0 aid=3)
Oct 27 18:29:12 pklaptop kernel: wlp2s0: associated
Oct 27 18:29:12 pklaptop kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready

Offline

#5 2016-10-27 15:50:36

Psykukumber
Member
From: Ukraine
Registered: 2016-10-19
Posts: 4
Website

Re: Power manager settings ignored, system just suspend (emachines e355)

Head_on_a_Stick wrote:

I think you have to set this as well:

LidSwitchIgnoreInhibited=no

Just tried this one, still not working.

Can we also see the output of:

systemd-inhibit

Looks like something really wrong:

psykukumber@pklaptop:[~]$ systemd-inhibit            
     Who: xfce4-power-manager (UID 1000/psykukumber, PID 764/xfce4-power-man)
    What: handle-power-key:handle-suspend-key:handle-hibernate-key
     Why: xfce4-power-manager handles these events
    Mode: block

     Who: NetworkManager (UID 0/root, PID 404/NetworkManager)
    What: sleep
     Why: NetworkManager needs to turn off networks
    Mode: delay

     Who: ModemManager (UID 0/root, PID 406/ModemManager)
    What: sleep
     Why: ModemManager needs to reset devices
    Mode: delay

3 inhibitors listed.

Offline

Pages: 1

Board footer

Powered by FluxBB