Mint refuses to suspend properly

[yuuki47]

Hi,

The time I spent in my computer is divided each day on several different periods. As such, everytime I no longer use it, I want it to suspend itself after 15 minutes. I set it up to do that in the control panel, but that didn't quite work. It only suspends partially (hard drives spin down, monitors shut off, etc) but the fans are still spinning. And worse, it refuses to wake-up half the time no matter what I do. It just freezes completely unresponsive.

I don't really know how to approach a solution here, does anyone have any idea?

Specs:

Code: Select all

MB: ASUS Prime B350-Plus
CPU: Ryzen 5 2400g
GPU: ASUS GT 730 (Running proprietary nvidia driver version 470) 
RAM: HyperX DDR4 8GB @ 2666MHZ
PSU: Corsair RM550x
SSD: Corsair MP510

And a record in my journal when it goes to sleep:

Code: Select all

May 11 17:39:10 mintpc systemd-sleep[3394]: Suspending system...
May 11 20:17:02 mintpc kernel: ACPI: Preparing to enter system sleep state S3
May 11 20:17:02 mintpc kernel: ACPI: Waking up from system sleep state S3
May 11 20:17:02 mintpc systemd-sleep[3394]: System resumed.
May 11 20:17:05 mintpc systemd-sleep[3540]: /dev/sdb:
May 11 20:17:05 mintpc systemd-sleep[3540]:  setting Advanced Power Management level to 0xfe (254)
May 11 20:17:05 mintpc systemd-sleep[3540]:  APM_level        = off
May 11 20:17:05 mintpc systemd-logind[906]: Operation 'sleep' finished.
May 11 20:17:05 mintpc NetworkManager[865]: <info>  [1652296625.4383] manager: sleep: wake requested (sleeping: yes  enabled: yes)
May 11 20:17:05 mintpc ModemManager[957]: <info>  [sleep-monitor] system is resuming
May 11 20:32:03 mintpc ModemManager[957]: <info>  [sleep-monitor] system is about to suspend
May 11 20:32:03 mintpc NetworkManager[865]: <info>  [1652297523.4011] manager: sleep: sleep requested (sleeping: no  enabled: yes)
May 11 20:32:03 mintpc NetworkManager[865]: <info>  [1652297523.4012] device (enp4s0): state change: unavailable -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 11 20:32:03 mintpc NetworkManager[865]: <info>  [1652297523.4102] device (p2p-dev-wlx8416f917cf0d): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')
May 11 20:32:03 mintpc NetworkManager[865]: <info>  [1652297523.4111] device (wlx8416f917cf0d): state change: activated -> deactivating (reason 'sleeping', sys-iface-state: 'managed')
May 11 20:32:04 mintpc NetworkManager[865]: <info>  [1652297524.0737] device (wlx8416f917cf0d): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
May 11 20:32:04 mintpc NetworkManager[865]: <info>  [1652297524.1354] device (wlx8416f917cf0d): state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 'managed')

[SMG]

Specs:

Code: Select all

MB: ASUS Prime B350-Plus
CPU: Ryzen 5 2400g
GPU: ASUS GT 730 (Running proprietary nvidia driver version 470) 
RAM: HyperX DDR4 8GB @ 2666MHZ
PSU: Corsair RM550x
SSD: Corsair MP510

Please give us information about your install by entering this command in a terminal:

Code: Select all

inxi -Fxxxrz

Click </> from the mini toolbar above the textbox where you type your reply and then place your cursor between the code tags and paste the results of the command between the code tags [code]Results[/code]. This will let us know how Mint sees your hardware.

[Aleigo]

Newer Asus AMD motherboards need kernel 5.14+ for suspend to work properly. You can try installing one yourself (didn't work with my ASUS UM425) or wait for the LM 21 next month release.

[SMG]

Newer Asus AMD motherboards need kernel 5.14+ for suspend to work properly.

Do you have a reference for that? I've not heard of that.

There are quite a few people with AMD graphics on their laptops which have problems with suspend, but that is related to the graphics driver. The person in this topic is using Nvidia graphics on a desktop.

There is the 5.14-oem kernel available for use with Linux Mint 20 versions, so if 5.14 works, then there is not a need to wait for LM21.

[Aleigo]

Do you have a reference for that? I've not heard of that.
There is the 5.14-oem kernel available for use with Linux Mint 20 versions, so if 5.14 works, then there is not a need to wait for LM21.

It's AMD S2idle Support For Linux e.g. here https://www.phoronix.com/scan.php?page= ... Linux-5.11

If 5.14oem works fine, then I totally agree that waiting for LM11 is not worth it. In my case oem kernels in LM didn't work (but Ubuntu 22.04 with 5.15 works just fine), so LM21 can be an option

[SMG]

It's AMD S2idle Support For Linux e.g. here https://www.phoronix.com/scan.php?page= ... Linux-5.11

That link indicates the patch is in the 5.11 kernel.

I found several other links which reference fixes in the 5.15 kernel, but those seem to be for Ryzen 5000 series. (OP has a 2000 series.)
AMD Has An Important Suspend/Resume Fix With Linux 5.15
One-Line Linux Patch Fixes AMD s2idle Failures For Some Ryzen Laptops?
AMD Prepares Linux Fix For Some Laptops Not Resuming From s2idle Suspend

If the fixes are in the 5.15 then that would explain why the 5.14-oem did not work for you, but Ubuntu 22.04 did.

[Aleigo]

It's AMD S2idle Support For Linux e.g. here https://www.phoronix.com/scan.php?page= ... Linux-5.11

That link indicates the patch is in the 5.11 kernel.

I found several other links which reference fixes in the 5.15 kernel, but those seem to be for Ryzen 5000 series. (OP has a 2000 series.)
AMD Has An Important Suspend/Resume Fix With Linux 5.15
One-Line Linux Patch Fixes AMD s2idle Failures For Some Ryzen Laptops?
AMD Prepares Linux Fix For Some Laptops Not Resuming From s2idle Suspend

If the fixes are in the 5.15 then that would explain why the 5.14-oem did not work for you, but Ubuntu 22.04 did.

Your last link is from Jan 2022 and the s2idle problem is still there, at least with some systems. Om my um425 kernel 5.14 works fine on other distros like Ubuntu and Arch, but 5.14oem in LM never solved the suspend failure.

My point in short was that suspend issues on amd should be in general approached by getting a fresher kernel.

[SMG]

Om my um425 kernel 5.14 works fine on other distros like Ubuntu and Arch, but 5.14oem in LM never solved the suspend failure.

My point in short was that suspend issues on amd should be in general approached by getting a fresher kernel.

Your hardware is much newer than OP's. For those with laptops with a Ryzen 4000 series like what you have, a "fresher" kernel is often recommended. We see those issues all the time.

In this case, OP is using a desktop with a Ryzen 2000 series which is quite a bit older than your hardware. We do not know what kernel they are using which is one reason I asked for the system information.

[yuuki47]

Please give us information about your install by entering this command in a terminal:

Code: Select all

inxi -Fxxxrz

Okay, here you go:

Code: Select all

System:
  Kernel: 5.4.0-110-generic x86_64 bits: 64 compiler: gcc v: 9.4.0 
  Desktop: Cinnamon 5.0.7 wm: muffin 5.0.2 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x 
  serial: <filter> UEFI: American Megatrends v: 6042 date: 04/28/2022 
CPU:
  Topology: Triple Core model: AMD Ryzen 5 2400G with Radeon Vega Graphics 
  bits: 64 type: MT MCP arch: Zen L2 cache: 1536 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 43200 
  Speed: 1599 MHz min/max: 1600/3600 MHz boost: enabled Core speeds (MHz): 
  1: 1600 2: 1600 3: 1599 4: 1600 5: 1600 6: 1600 
Graphics:
  Device-1: NVIDIA GK208B [GeForce GT 730] vendor: ASUSTeK driver: nvidia 
  v: 470.103.01 bus ID: 01:00.0 chip ID: 10de:1287 
  Display: x11 server: X.Org 1.20.13 driver: nvidia 
  unloaded: fbdev,modesetting,nouveau,vesa 
  resolution: 1440x900~60Hz, 1920x1080~60Hz 
  OpenGL: renderer: NVIDIA GeForce GT 730/PCIe/SSE2 
  v: 4.6.0 NVIDIA 470.103.01 direct render: Yes 
Audio:
  Device-1: NVIDIA GK208 HDMI/DP Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 01:00.1 chip ID: 10de:0e0f 
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 09:00.6 chip ID: 1022:15e3 
  Sound Server: ALSA v: k5.4.0-110-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: ASUSTeK driver: r8169 v: kernel port: e000 bus ID: 04:00.0 
  chip ID: 10ec:8168 
  IF: enp4s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
  IF-ID-1: virbr0 state: down mac: <filter> 
  IF-ID-2: virbr0-nic state: down mac: <filter> 
Drives:
  Local Storage: total: 3.17 TiB used: 1.14 TiB (36.1%) 
  ID-1: /dev/nvme0n1 vendor: Corsair model: Force MP510 size: 447.13 GiB 
  speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: ECFM12.2 scheme: GPT 
  ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0 
  size: 931.51 GiB speed: 6.0 Gb/s rotation: 7200 rpm serial: <filter> 
  rev: 1A01 scheme: GPT 
  ID-3: /dev/sdb vendor: Hitachi model: HDS5C3020BLE630 size: 1.82 TiB 
  speed: 6.0 Gb/s rotation: 5700 rpm serial: <filter> rev: AAB0 scheme: GPT 
Partition:
  ID-1: / size: 438.62 GiB used: 215.52 GiB (49.1%) fs: ext4 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 35.0 C mobo: N/A gpu: nvidia temp: 42 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb https://www.mirrorservice.org/sites/packages.linuxmint.com/packages uma main upstream import backport
  2: deb http://archive.ubuntu.com/ubuntu focal main restricted universe multiverse
  3: deb http://archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
  4: deb http://archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
  Active apt repos in: /etc/apt/sources.list.d/teamviewer.list 
  1: deb https://linux.teamviewer.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 354 Uptime: 55m Memory: 7.68 GiB used: 2.33 GiB (30.3%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 
 

I think you are right about the kernel, I'm using the 5.4 kernel because it's LTS and I'm used to it. However, if I have to install 5.15, I have no problem with that. But how is NTFS support on 5.15? I'm wondering because I know 5.15 brings the new Microsoft NTFS driver on the scene if memory serves.

[SMG]

I think you are right about the kernel, I'm using the 5.4 kernel because it's LTS and I'm used to it. However, if I have to install 5.15, I have no problem with that. But how is NTFS support on 5.15? I'm wondering because I know 5.15 brings the new Microsoft NTFS driver on the scene if memory serves.

There is thread on this forum about the unknown fate of the NTFS support. Apparently, the person/entity which provided the info for the 5.15 driver has disappeared so the fate of its support is unknown.

It is possible there may be more than one issue at play on your system. One may relate to getting into suspend and the other getting out of suspend. (Or maybe it is just one issue.)

You have an Nvidia 700 series GPU. I have lost count of how many people have posted to the forum with the problem resuming from suspend with those and have been able to successfully use a fix someone found and posted on the forum. The workaround mentioned in this post has worked for many people. If you need detailed instructions for editing the file then see this post and the subsequent ones in that topic.

I suggest trying that first. If that does not clear out all the issues, there is a 5.13 kernel available in Update Manager if you want to try a newer kernel.

[yuuki47]

I think you are right about the kernel, I'm using the 5.4 kernel because it's LTS and I'm used to it. However, if I have to install 5.15, I have no problem with that. But how is NTFS support on 5.15? I'm wondering because I know 5.15 brings the new Microsoft NTFS driver on the scene if memory serves.

There is thread on this forum about the unknown fate of the NTFS support. Apparently, the person/entity which provided the info for the 5.15 driver has disappeared so the fate of its support is unknown.

It is possible there may be more than one issue at play on your system. One may relate to getting into suspend and the other getting out of suspend. (Or maybe it is just one issue.)

You have an Nvidia 700 series GPU. I have lost count of how many people have posted to the forum with the problem resuming from suspend with those and have been able to successfully use a fix someone found and posted on the forum. The workaround mentioned in this post has worked for many people. If you need detailed instructions for editing the file then see this post and the subsequent ones in that topic.

I suggest trying that first. If that does not clear out all the issues, there is a 5.13 kernel available in Update Manager if you want to try a newer kernel.

I tried installing 5.14 oem. Didn't work. Then, I reset BIOS defaults, which worked. The system now suspends properly Everytime. Well, except when LibreOffice is open. If I leave it open, the system doesn't go to suspend and freezes with monitors off.

[SMG]

I tried installing 5.14 oem.

Why? I specifically suggested using the 5.13 kernel.

The OEM kernels are special kernels which is why they are not available in Update Manager and should not be used unless all others do not work. I do not know of anyone with a Ryzen 2000 series who needs the 5.14-oem kernel. The 4000 and 5000 series often do, but not a 2000 series.

Then, I reset BIOS defaults, which worked. The system now suspends properly Everytime. Well, except when LibreOffice is open. If I leave it open, the system doesn't go to suspend and freezes with monitors off.

It sounds like you are running into a memory issue. Perhaps increasing the size of the swap file will help. Or you can try the 5.13 kernel.

Instructions for upgrading to the 5.13 kernel:

• Open Update Manager.
• Select View > Linux Kernels and click Continue.
• Make sure 5.13 is selected on the left panel and then click the top-most option on the right panel. An "Install" button will appear.
• Install the kernel and then reboot for it to become active.

[yuuki47]

It sounds like you are running into a memory issue. Perhaps increasing the size of the swap file will help. Or you can try the 5.13 kernel.

Yes, sorry, you are right. I tried with 5.13 and suspend was still working fine, so indeed, no need for 5.14. But the same issue persists on 5.13, it won't go to suspend if LibreOffice is open. I increased the swapfile to 6G but that did nothing. Seems like the LibreOffice app makes the kernel freeze when it goes to suspend.

[SMG]

But the same issue persists on 5.13, it won't go to suspend if LibreOffice is open. I increased the swapfile to 6G but that did nothing. Seems like the LibreOffice app makes the kernel freeze when it goes to suspend.

I am not familiar with a "kernel freeze". I do know LibreOffice can be quite resource intensive. Have you checked to see if there might be any bug reports on LibreOffice which sound similar to what you are experiencing? I seem to recall reading on this forum that quite a few people are using versions newer than what come in the repo, but I do not recall off the top of my head what specific reasons they had for doing so.

The only other idea I have would be to check the logs to see if anything is being recorded which might indicate the problem. Usually, the commands to put the computer into suspend do show up in dmesg and journalctl. I think they are also in syslog, but can not recall for sure because it has been a while since I've checked syslog. If you need/want help checking those logs, let us know.