[Solved] Linux Mint 20.2 does not recover from opening lid after suspending

[jamespedid]

Hello, I'm having an issue in Linux Mint 20.2 that I did not have in 19.3

When I close the laptop lid, the OS goes into a sleep or suspend mode. Then later I open the lid, and I'm greeted with a single blank underscore in the corner of the screen. When I hit buttons, I see the following graphics-card related error

Code: Select all

[8875.947033] nvidia-modeset: GPU0: Error: Display engine push buffer channel allocation failed: 0x65 (Call times out [NV_ERR_TIMEOUT])
[8875.947311] nvidia-modeset: GPU0 Error: Failed to allocate display engine core DMA push buffer
[8879.947028] nvidia-modeset: GPU0: Error: Display engine push buffer channel allocation failed: 0x65 (Call times out [NV_ERR_TIMEOUT])
[8879.947216] nvidia-modeset: GPU0 Error: Failed to allocate display engine core DMA push buffer

What should I look at first? Should I try downgrading the graphics card driver to an earlier version?

Code: Select all

System:
  Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
  Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 dm: LightDM 1.30.0
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal
Machine:
  Type: Laptop System: Notebook product: N85_87HP6 v: N/A serial: <filter>
  Chassis: type: 10 serial: <filter>
  Mobo: Notebook model: N85_87HP6 serial: <filter>
  UEFI [Legacy]: American Megatrends v: 1.05.02RLS1 date: 07/05/2017
Battery:
  ID-1: BAT0 charge: 49.8 Wh condition: 49.8/59.9 Wh (83%) volts: 12.8/11.1
  model: Notebook BAT type: Li-ion serial: <filter> status: Full
CPU:
  Topology: Quad Core model: Intel Core i7-7700HQ bits: 64 type: MT MCP
  arch: Kaby Lake rev: 9 L2 cache: 6144 KiB
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  bogomips: 44798
  Speed: 1000 MHz min/max: 800/3800 MHz Core speeds (MHz): 1: 1000 2: 1000
  3: 1000 4: 1001 5: 1002 6: 1005 7: 1000 8: 1045
Graphics:
  Device-1: Intel HD Graphics 630 vendor: CLEVO/KAPOK driver: i915 v: kernel
  bus ID: 00:02.0 chip ID: 8086:591b
  Device-2: NVIDIA GP106M [GeForce GTX 1060 Mobile] vendor: CLEVO/KAPOK
  driver: nvidia v: 460.80 bus ID: 01:00.0 chip ID: 10de:1c20
  Display: x11 server: X.Org 1.20.9 driver: modesetting,nvidia
  unloaded: fbdev,nouveau,vesa resolution: 1920x1080~60Hz
  OpenGL: renderer: GeForce GTX 1060/PCIe/SSE2 v: 4.6.0 NVIDIA 460.80
  direct render: Yes
Audio:
  Device-1: Intel CM238 HD Audio vendor: CLEVO/KAPOK driver: snd_hda_intel
  v: kernel bus ID: 00:1f.3 chip ID: 8086:a171
  Device-2: NVIDIA GP106 High Definition Audio driver: snd_hda_intel
  v: kernel bus ID: 01:00.1 chip ID: 10de:10f1
  Sound Server: ALSA v: k5.4.0-77-generic
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
  vendor: CLEVO/KAPOK driver: r8169 v: kernel port: d000 bus ID: 03:00.1
  chip ID: 10ec:8168
  IF: enp3s0f1 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel port: d000
  bus ID: 04:00.0 chip ID: 8086:24fd
  IF: wlp4s0 state: up mac: <filter>
  IF-ID-1: br-9c0ec184c63c state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 39.17 GiB (8.2%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS512G1X0C-00ENX0
  size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> rev: B35500WD
  scheme: MBR
Partition:
  ID-1: / size: 467.96 GiB used: 39.17 GiB (8.4%) fs: ext4
  dev: /dev/nvme0n1p5
Sensors:
  System Temperatures: cpu: 54.0 C mobo: N/A gpu: nvidia temp: 55 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/docker.list
  1: deb [arch=amd64 signed-by=/usr/share/keyrings/docker-archive-keyring.gpg] https://download.docker.com/linux/ubuntu focal stable
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
  1: deb http://packages.linuxmint.com 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
Info:
  Processes: 268 Uptime: 8h 42m Memory: 15.52 GiB used: 1.84 GiB (11.9%)
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

EDIT: Added inxi information

[SMG]

What should I look at first?

I suggest looking at Section 5 of READ: How To Get Help!. It explains the data we need to be able to help you. Please provide that system data.

[jamespedid]

What should I look at first?

I suggest looking at Section 5 of READ: How To Get Help!. It explains the data we need to be able to help you. Please provide that system data.

Added information

[SMG]

Do you recall if you were using the same driver version in LM19.3?

I helped someone in this thread <SOLVED> Mint doesn't recover from sleep with a dual-graphics laptop who ended up switching to the Nvidia-450 (from the Nvidia-460) which resolved the issue. However, the Nvidia-450 is no longer available in Driver Manager. Maybe some of the troubleshooting done in that thread will give you ideas of things to check. I can pass along instructions to install the Nvidia-450 file from the Nvidia website if you decide to go that route.

However, Nvidia just released the Nvidia-470 driver yesterday. There is usually a little lag between when Nvidia releases a driver and when it becomes available through Driver Manager. There is repackaging and such done to make sure it works with the other packages in Ubuntu/Mint as well as with Driver Manager and that takes time. (In the past, I seem to recall a lag of ~1-3 weeks before a newer driver became available in Driver Manager.)

Here are the Nvidia-470 Release highlights. It is an unusually loooooooong list. I do not know if the updated driver might correct the issue your system is experiencing, but perhaps waiting to try it will be an option you want to consider.

[jamespedid]

I downgraded to the NVIDIA-390 driver and functionality was restored.

I tried the NVIDIA-470 driver first and it still had the issue.