Freeze for some seconds after wake up from suspend

nomat · 2016-01-24 17:08:24

Hello everyone, i have recently installed the latest version of Arch Linux on my laptop (Packard Bell Easy Note TS11SB), everything works fine except one thing. When i try to wake up from suspend, everything appears but are in freeze for some seconds (about 15-20 sec) and after return to normal. Earlier i had another distro and hadn't collide with this problem..
Can someone help me with this problem? thanks in advance

Last edited by nomat (2016-01-24 17:10:09)

ewaller · 2016-01-24 17:36:14

You might check your log journal for clues, but I bet you are waiting for a wireless network to reestablish itself.
Also, please define suspend. In my mind that implies you are saving state to disk and doing a complete power off; as opposed to sleep where state remains in memory and the processor does little else besides refresh memory.

nomat · 2016-01-24 18:04:11

So, suspend suppose that i write something like systemctl suspend in terminal and my laptop is not doing complete power off because i see enlightening with orange. Checking log journal i have found :

ian 24 19:49:25 mrXbl kernel: PM: resume of devices complete after 44008.428 msecs
ian 24 19:49:25 mrXbl kernel: PM: Finishing wakeup.
ian 24 19:49:25 mrXbl kernel: Restarting tasks ... done.
ian 24 19:49:25 mrXbl systemd[1]: Time has been changed
ian 24 19:49:25 mrXbl systemd[415]: Time has been changed
ian 24 19:49:25 mrXbl systemd-sleep[1973]: System resumed.
ian 24 19:49:25 mrXbl systemd[1]: Started Suspend.
ian 24 19:49:25 mrXbl systemd[1]: sleep.target: Unit not needed anymore. Stopping.
ian 24 19:49:25 mrXbl systemd[1]: Stopped target Sleep.
ian 24 19:49:25 mrXbl systemd[1]: Reached target Suspend.
ian 24 19:49:25 mrXbl systemd-logind[293]: Operation 'sleep' finished.
ian 24 19:49:25 mrXbl systemd[1]: suspend.target: Unit is bound to inactive unit systemd-suspend.service. Stopping, too.
ian 24 19:49:25 mrXbl systemd[1]: Stopped target Suspend.
ian 24 19:49:25 mrXbl NetworkManager[292]: <info>  wake requested (sleeping: yes  enabled: yes)
ian 24 19:49:25 mrXbl NetworkManager[292]: <info>  waking up...
ian 24 19:49:25 mrXbl NetworkManager[292]: <info>  (enp2s0f0): device state change: unavailable -> unmanaged (reason 'sleeping') [20 10 37]
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
ian 24 19:49:26 mrXbl kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  (enp2s0f0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
ian 24 19:49:26 mrXbl kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
ian 24 19:49:26 mrXbl kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0f0: link is not ready
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  NetworkManager state is now DISCONNECTED
ian 24 19:49:26 mrXbl kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0f0: link is not ready
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  (wlp3s0) supports 4 scan SSIDs
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: starting -> ready
ian 24 19:49:26 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
ian 24 19:49:26 mrXbl kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: ready -> inactive
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Auto-activating connection 'Patrinjel'.
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): Activation: starting connection 'Patrinjel' (4ad91670-9aff-4adc-bac2-79d664cc5688)
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  NetworkManager state is now CONNECTING
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): Activation: (wifi) access point 'Patrinjel' has security, but secrets are required.
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: config -> need-auth (reason 'none') [50 60 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): Activation: (wifi) connection 'Patrinjel' has security, and secrets exist.  No new secrets needed.
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: added 'ssid' value 'Patrinjel'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: added 'scan_ssid' value '1'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: added 'auth_alg' value 'OPEN'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: added 'psk' value '<omitted>'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Config: set interface ap_scan to 1
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: SME: Trying to authenticate with e8:94:f6:62:59:2a (SSID='Patrinjel' freq=2462 MHz)
ian 24 19:49:27 mrXbl kernel: wlp3s0: authenticate with e8:94:f6:62:59:2a
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: inactive -> authenticating
ian 24 19:49:27 mrXbl kernel: wlp3s0: send auth to e8:94:f6:62:59:2a (try 1/3)
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: Trying to associate with e8:94:f6:62:59:2a (SSID='Patrinjel' freq=2462 MHz)
ian 24 19:49:27 mrXbl kernel: wlp3s0: authenticated
ian 24 19:49:27 mrXbl kernel: wlp3s0: associate with e8:94:f6:62:59:2a (try 1/3)
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: authenticating -> associating
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: Associated with e8:94:f6:62:59:2a
ian 24 19:49:27 mrXbl kernel: wlp3s0: RX AssocResp from e8:94:f6:62:59:2a (capab=0x431 status=0 aid=1)
ian 24 19:49:27 mrXbl kernel: wlp3s0: associated
ian 24 19:49:27 mrXbl kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: associating -> 4-way handshake
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: WPA: Key negotiation completed with e8:94:f6:62:59:2a [PTK=CCMP GTK=CCMP]
ian 24 19:49:27 mrXbl wpa_supplicant[357]: wlp3s0: CTRL-EVENT-CONNECTED - Connection to e8:94:f6:62:59:2a completed [id=0 id_str=]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): supplicant interface state: 4-way handshake -> completed
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'Patrinjel'.
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  dhclient started with pid 2020
ian 24 19:49:27 mrXbl dhclient[2020]: DHCPREQUEST on wlp3s0 to 255.255.255.255 port 67
ian 24 19:49:27 mrXbl dhclient[2020]: DHCPACK from 192.168.0.1
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    address 192.168.0.101
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    plen 24 (255.255.255.0)
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    gateway 192.168.0.1
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    server identifier 192.168.0.1
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    lease time 7200
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>    nameserver '192.168.0.1'
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): DHCPv4 state changed unknown -> bound
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
ian 24 19:49:27 mrXbl NetworkManager[292]: <info>  NetworkManager state is now CONNECTED_LOCAL
ian 24 19:49:27 mrXbl dhclient[2020]: bound to 192.168.0.101 -- renewal in 3241 seconds.
ian 24 19:49:28 mrXbl NetworkManager[292]: <info>  NetworkManager state is now CONNECTED_GLOBAL
ian 24 19:49:28 mrXbl NetworkManager[292]: <info>  Policy set 'Patrinjel' (wlp3s0) as default for IPv4 routing and DNS.
ian 24 19:49:28 mrXbl NetworkManager[292]: <info>  Writing DNS information to /usr/bin/resolvconf
ian 24 19:49:28 mrXbl NetworkManager[292]: <info>  (wlp3s0): Activation: successful, device activated.
ian 24 19:49:28 mrXbl dbus[294]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
ian 24 19:49:28 mrXbl systemd[1]: Starting Network Manager Script Dispatcher Service...
ian 24 19:49:28 mrXbl dbus[294]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
ian 24 19:49:28 mrXbl systemd[1]: Started Network Manager Script Dispatcher Service.

EDIT: I've read some documentation, about suspend so i'm interesting how can i check if suspend to ram works?

Last edited by nomat (2016-01-25 05:18:25)

Arch Linux

#1 2016-01-24 17:08:24

Freeze for some seconds after wake up from suspend

#2 2016-01-24 17:36:14

Re: Freeze for some seconds after wake up from suspend

#3 2016-01-24 18:04:11

Re: Freeze for some seconds after wake up from suspend

Board footer