Suspend/Hybernate doesn't work anymore after 20.1 upgrade [SOLVED]

Screen resolution, 3D Acceleration, nVidia, ATI
Forum rules
Before you post please read this
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Suspend/Hybernate doesn't work anymore after 20.1 upgrade [SOLVED]

Post by aidandorc »

Hi guys
I've just updated my mint 20 to 20.1 and if I close the notebook, when I reopen it the os is freezed. Suspension doesn't work anymore...
It's necessary a forced power off with the power on button....... :shock:
Before upgrade, with mint 20, everything was perfect!
Any idea is really appreciated.....


My stuff here:

Code: Select all

System:    Kernel: 5.8.0-36-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 4.8.5 
           wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: ASUSTeK product: X540LJ v: 1.0 serial: <filter> 
           Mobo: ASUSTeK model: X540LJ v: 1.0 serial: <filter> UEFI: American Megatrends 
           v: X540LJ.301 date: 11/01/2016 
CPU:       Topology: Dual Core model: Intel Core i3-4005U bits: 64 type: MT MCP arch: Haswell 
           rev: 1 L2 cache: 3072 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 13569 
           Speed: 929 MHz min/max: 800/1600 MHz Core speeds (MHz): 1: 933 2: 928 3: 933 4: 916 
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: ASUSTeK driver: i915 v: kernel 
           bus ID: 00:02.0 chip ID: 8086:0a16 
           Device-2: NVIDIA GK208BM [GeForce 920M] vendor: ASUSTeK driver: nvidia v: 460.32.03 
           bus ID: 04:00.0 chip ID: 10de:1299 
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia 
           unloaded: fbdev,nouveau,vesa resolution: 1366x768~60Hz
Last edited by aidandorc on Fri Jan 22, 2021 2:58 pm, edited 1 time in total.
User avatar
AZgl1500
Level 15
Level 15
Posts: 5796
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes sweeping down the plains
Contact:

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by AZgl1500 »

I took a different approach.

1) if the power adapter is connected, I set "lid closed" to NOTHING

2) if on Battery Power, "lid Closed" is set to POWER OFF.

can't tell you how times I just closed the lid and forget the laptop was still running, and zonked the battery flat.
Linux Mint 19.3 Cinnamon / ASUS FX705GM
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

ok...I understand your suggestion, but it's not correct.
Before upgrade...with mint 20 it worked perfectly.
So ..something happened with 20.1...
I don't want to change configurations.
nick78739
Level 1
Level 1
Posts: 4
Joined: Tue Mar 06, 2012 6:17 pm
Location: Austin, TX

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by nick78739 »

I am seeing the same issue - laptop shuts off instead of suspending when on AC power when I close the lid:

Code: Select all

System:    Kernel: 5.4.0-60-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.5 
           wm: muffin 4.8.0 dm: LightDM 1.30.0 Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Laptop System: Hewlett-Packard product: HP ENVY Notebook v: Type1ProductConfigId 
           serial: <filter> Chassis: type: 10 serial: <filter> 
           Mobo: Hewlett-Packard model: 80DD v: 64.02 serial: <filter> UEFI: Insyde v: F.02 date: 05/11/2015 
Battery:   ID-1: BAT1 charge: 49.6 Wh condition: 49.6/55.5 Wh (89%) volts: 12.8/11.4 model: COMPAL PABAS0241231 
           type: Li-ion serial: <filter> status: Full 
CPU:       Topology: Dual Core model: Intel Core i7-5500U bits: 64 type: MT MCP arch: Broadwell rev: 4 
           L2 cache: 4096 KiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19156 
           Speed: 1021 MHz min/max: 500/3000 MHz Core speeds (MHz): 1: 1216 2: 1143 3: 1179 4: 1003 
Graphics:  Device-1: Intel HD Graphics 5500 vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:1616 
           Device-2: NVIDIA GM107M [GeForce GTX 950M] vendor: Hewlett-Packard driver: nvidia v: 450.102.04 
           bus ID: 04:00.0 chip ID: 10de:139a 
           Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 3200x1800~60Hz 
           OpenGL: renderer: Mesa Intel HD Graphics 5500 (BDW GT2) v: 4.6 Mesa 20.2.6 direct render: Yes
User avatar
SMG
Level 11
Level 11
Posts: 3858
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by SMG »

aidandorc wrote:
Sun Jan 10, 2021 4:24 pm
Any idea is really appreciated.....
If you are pressing the button to kill the power, then you know approximately when this is happening. Check /var/log/syslog around that time to see what might be happening.

Or you can run the following. It will post the journal of the prior boot (the one which ended in a hang and you powered it off) in reverse order and send it to termbin.

Code: Select all

journalctl -rb -1 | nc termbin.com 9999
Let us know the url which this returns.

While you recently did the upgrade to LM20.1, you also updated your graphics driver around the same time. Sometimes graphic drivers have been known to cause issues when resuming from suspend, so there could be more than one issue contributing to this depending on the timing of exactly when it started.

You might also want to check to see if you have the latest BIOS/UEFI installed on your computer.
LM20.1 Cinnamon
User avatar
AZgl1500
Level 15
Level 15
Posts: 5796
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes sweeping down the plains
Contact:

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by AZgl1500 »

Why not just set Lid Closed to nothing and avoid all of those problems?

the BIOS will turn the screen power off while it is closed.
Linux Mint 19.3 Cinnamon / ASUS FX705GM
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

are you sure that BIOS does that?
my laptop remains active and powered-off.....
What have I to check on BIOS settings?
no good for me.....
User avatar
AZgl1500
Level 15
Level 15
Posts: 5796
Joined: Thu Dec 31, 2015 3:20 am
Location: Oklahoma where the wind comes sweeping down the plains
Contact:

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by AZgl1500 »

aidandorc wrote:
Wed Jan 13, 2021 4:32 am
are you sure that BIOS does that?
my laptop remains active and powered-off.....
What have I to check on BIOS settings?
no good for me.....
there is a switch on the hinge of laptops that when the lid is closed, it tells BIOS to turn off the power to the screen.
that has been the case on every laptop I have seen, Dell, ASUS, Acer, HP, Toshiba. and the CPU goes into 'idle mode'

when I have lifted the lid on all the laptops I have seen, there is a 2 or 3 second delay powered up the screen.... whatever I have been doing, is still there, waiting for me.... I make it a habit to issue the SuperKey+D command, or in Windows WinKey+D does the same thing.

I have all of my laptops configured in 'SETTINGS' to Power Off, if the lid is closed, AND it is on Battery Power....

I have forgotten several times too many, that I had closed the lid and the laptop was still up and running.
bad bad bad, especially in Windows.

So, in Linux, I configure Lid Closed to SHUTDOWN.

.
Linux Mint 19.3 Cinnamon / ASUS FX705GM
nick78739
Level 1
Level 1
Posts: 4
Joined: Tue Mar 06, 2012 6:17 pm
Location: Austin, TX

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by nick78739 »

BTW - I tried setting the lid close to do nothing - noticed this morning my CPU fan was running this morning and the system was locked up. :? BTW if I do a pm-suspend, that works so somehow the event mapping isn't working.
User avatar
SMG
Level 11
Level 11
Posts: 3858
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by SMG »

Hibernate is turned off by default in LM20.0. While I do not use hibernate, I have helped others troubleshoot getting it to work in LM20.0 so I know there are steps which need to be taken to make it active. Maybe if you walk through the steps you took to get it enabled the first time you will find what may have changed during the upgrade so you can get it working again.
LM20.1 Cinnamon
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

On my laptop hybernation was not turned off and it worked perfectly with 20.0.
To upgrade to 20.1 I've followed the guided path proposed by the os itself and it made the job.
That's all.
What are the steps you mentioned to re enable it?
Thx
Bye
User avatar
SMG
Level 11
Level 11
Posts: 3858
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by SMG »

aidandorc wrote:
Thu Jan 14, 2021 3:45 am
On my laptop hybernation was not turned off and it worked perfectly with 20.0.
Suspending the computer to put it to sleep (save current session in RAM) is different from hibernation (save current session to hard disk).

Rereading your initial post, it appears suspension (save to RAM) is not working like it was in LM20.0. That is turned on by default.

You have indicated pm-suspend does work. Does suspend work from the shutdown menu?

I already mentioned in an earlier post that checking the logs would probably be necessary to determine what is happening. You can either supply the url of the command I suggested earlier or you can check /var/log/syslog to see what messages appear before you press the power button to restart the computer.
LM20.1 Cinnamon
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

No it doesn't work neither from startmenu.
Yes ...you're right...I' ve to check syslog....I let you know asap!🙏
Bye
loaded_dog
Level 1
Level 1
Posts: 1
Joined: Sat Nov 02, 2019 11:32 pm

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by loaded_dog »

Yabba dabba doo!!!

Suspend used to work in 19.3...

stopped working in 20.0!

NOW, working in 20.1!!!!!

Is this an "undocumented feature" that cannot be explained by mere mortals (and kernel developers)???
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

it's not my case.
suspend worked perfectly on 20.0 and stopped working on 20.1.........
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

Hi @smg ....I've checked /var/log/syslog......this is what happens when suspend command is invoked...

n 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2287] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2289] device (enp2s0f2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2648] device (p2p-dev-wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2655] device (50:8F:4C:07:D5:7B): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2664] manager: NetworkManager state is now ASLEEP
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.2678] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home dbus-daemon[702]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=704 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 19 09:04:02 davide-home systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 19 09:04:02 davide-home dbus-daemon[702]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 19 09:04:02 davide-home systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 19 09:04:02 davide-home kernel: [ 447.657712] wlp3s0: deauthenticating from c4:f0:81:3f:43:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=c4:f0:81:3f:43:a0 reason=3 locally_generated=1
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 19 09:04:02 davide-home NetworkManager[704]: <warn> [1611043442.3479] sup-iface[0x564527a80120,wlp3s0]: connection disconnected (reason -3)
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.3522] device (wlp3s0): supplicant interface state: completed -> disconnected
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.3526] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home avahi-daemon[699]: Withdrawing address record for fe80::f17c:1ae7:dd1a:8894 on wlp3s0.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::f17c:1ae7:dd1a:8894.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.3750] dhcp4 (wlp3s0): canceled DHCP transaction
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.3751] dhcp4 (wlp3s0): state changed bound -> done
Jan 19 09:04:02 davide-home avahi-daemon[699]: Withdrawing address record for 192.168.43.213 on wlp3s0.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.43.213.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Jan 19 09:04:02 davide-home NetworkManager[704]: <info> [1611043442.3863] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jan 19 09:04:02 davide-home wpa_supplicant[753]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jan 19 09:04:02 davide-home systemd[1]: Reached target Sleep.
Jan 19 09:04:02 davide-home systemd[1]: Starting Suspend...
Jan 19 09:04:02 davide-home kernel: [ 447.899228] PM: suspend entry (deep)
Jan 19 09:04:02 davide-home systemd-sleep[2981]: Suspending system...
User avatar
SMG
Level 11
Level 11
Posts: 3858
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by SMG »

aidandorc wrote:
Tue Jan 19, 2021 4:17 am
Hi @smg ....I've checked /var/log/syslog......this is what happens when suspend command is invoked...

Code: Select all

n 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2287] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2289] device (enp2s0f2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2648] device (p2p-dev-wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2655] device (50:8F:4C:07:D5:7B): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2664] manager: NetworkManager state is now ASLEEP
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.2678] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home dbus-daemon[702]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=704 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 19 09:04:02 davide-home systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 19 09:04:02 davide-home dbus-daemon[702]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 19 09:04:02 davide-home systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 19 09:04:02 davide-home kernel: [  447.657712] wlp3s0: deauthenticating from c4:f0:81:3f:43:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=c4:f0:81:3f:43:a0 reason=3 locally_generated=1
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 19 09:04:02 davide-home NetworkManager[704]: <warn>  [1611043442.3479] sup-iface[0x564527a80120,wlp3s0]: connection disconnected (reason -3)
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.3522] device (wlp3s0): supplicant interface state: completed -> disconnected
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.3526] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home avahi-daemon[699]: Withdrawing address record for fe80::f17c:1ae7:dd1a:8894 on wlp3s0.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::f17c:1ae7:dd1a:8894.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.3750] dhcp4 (wlp3s0): canceled DHCP transaction
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.3751] dhcp4 (wlp3s0): state changed bound -> done
Jan 19 09:04:02 davide-home avahi-daemon[699]: Withdrawing address record for 192.168.43.213 on wlp3s0.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.43.213.
Jan 19 09:04:02 davide-home avahi-daemon[699]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Jan 19 09:04:02 davide-home NetworkManager[704]: <info>  [1611043442.3863] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 19 09:04:02 davide-home wpa_supplicant[753]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jan 19 09:04:02 davide-home wpa_supplicant[753]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jan 19 09:04:02 davide-home systemd[1]: Reached target Sleep.
Jan 19 09:04:02 davide-home systemd[1]: Starting Suspend...
Jan 19 09:04:02 davide-home kernel: [  447.899228] PM: suspend entry (deep)
Jan 19 09:04:02 davide-home systemd-sleep[2981]: Suspending system...
This is when you use pm-suspend (which you indicated does work)?
Is there something different in the log when you try suspending from the menu? That might give a clue as to what is happening.
LM20.1 Cinnamon
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

this is the log when the lid is closed....

Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.5818] manager: sleep: sleep requested (sleeping: no enabled: yes)
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.5820] device (enp2s0f2): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6004] device (p2p-dev-wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6009] device (50:8F:4C:07:D5:7B): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6016] manager: NetworkManager state is now ASLEEP
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6020] device (wlp3s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home dbus-daemon[761]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.10' (uid=0 pid=762 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
Jan 20 15:55:24 davide-home systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 20 15:55:24 davide-home dbus-daemon[761]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 20 15:55:24 davide-home systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 20 15:55:24 davide-home kernel: [ 460.346796] wlp3s0: deauthenticating from c4:f0:81:3f:43:a0 by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 20 15:55:24 davide-home wpa_supplicant[795]: wlp3s0: CTRL-EVENT-DISCONNECTED bssid=c4:f0:81:3f:43:a0 reason=3 locally_generated=1
Jan 20 15:55:24 davide-home wpa_supplicant[795]: wlp3s0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Jan 20 15:55:24 davide-home NetworkManager[762]: <warn> [1611154524.6452] sup-iface[0x55c0ce94d920,wlp3s0]: connection disconnected (reason -3)
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6464] device (wlp3s0): supplicant interface state: completed -> disconnected
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6468] device (wlp3s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home avahi-daemon[757]: Withdrawing address record for fe80::f17c:1ae7:dd1a:8894 on wlp3s0.
Jan 20 15:55:24 davide-home avahi-daemon[757]: Leaving mDNS multicast group on interface wlp3s0.IPv6 with address fe80::f17c:1ae7:dd1a:8894.
Jan 20 15:55:24 davide-home avahi-daemon[757]: Interface wlp3s0.IPv6 no longer relevant for mDNS.
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6789] dhcp4 (wlp3s0): canceled DHCP transaction
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6790] dhcp4 (wlp3s0): state changed bound -> done
Jan 20 15:55:24 davide-home avahi-daemon[757]: Withdrawing address record for 192.168.43.213 on wlp3s0.
Jan 20 15:55:24 davide-home avahi-daemon[757]: Leaving mDNS multicast group on interface wlp3s0.IPv4 with address 192.168.43.213.
Jan 20 15:55:24 davide-home avahi-daemon[757]: Interface wlp3s0.IPv4 no longer relevant for mDNS.
Jan 20 15:55:24 davide-home NetworkManager[762]: <info> [1611154524.6881] device (wlp3s0): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
Jan 20 15:55:24 davide-home wpa_supplicant[795]: wlp3s0: CTRL-EVENT-SCAN-FAILED ret=-100
Jan 20 15:55:24 davide-home wpa_supplicant[795]: nl80211: deinit ifname=wlp3s0 disabled_11b_rates=0
Jan 20 15:55:24 davide-home systemd[1]: Reached target Sleep.
Jan 20 15:55:24 davide-home systemd[1]: Starting Suspend...
Jan 20 15:55:24 davide-home systemd-sleep[3064]: Suspending system...
Jan 20 15:55:24 davide-home kernel: [ 460.616526] PM: suspend entry (deep)
User avatar
SMG
Level 11
Level 11
Posts: 3858
Joined: Sun Jul 26, 2020 6:15 pm
Location: USA

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by SMG »

The only difference I see between the two are the last two lines. They are reversed in the second case and the kernel timing seems to be slightly longer in the second case.

Code: Select all

 using PM suspend
Jan 19 09:04:02 davide-home kernel: [ 447.899228] PM: suspend entry (deep)
Jan 19 09:04:02 davide-home systemd-sleep[2981]: Suspending system...

 when the lid is closed
Jan 20 15:55:24 davide-home systemd-sleep[3064]: Suspending system...
Jan 20 15:55:24 davide-home kernel: [ 460.616526] PM: suspend entry (deep)
Did you change the kernel version right around when you upgraded to LM20.1? Maybe a kernel update rather than the LM20 upgrade might be a factor in this.
LM20.1 Cinnamon
aidandorc
Level 1
Level 1
Posts: 15
Joined: Sun Jan 10, 2021 10:53 am

Re: Suspend/Hybernate doesn't work anymore after 20.1 upgrade

Post by aidandorc »

Hi
yes...the kernel was upgraded with 20.1 and also during last days (maybe yesterday..) with the update managament process proposed by the os itself sometimes on a daily basis.....
Post Reply

Return to “Graphics Cards & Monitors”