What could cause an Ubuntu computer to keep crashing after hibernation?

Linux support
1

I don’t seem to understand why my Ubuntu laptop would keep crashing after I resume it from hibernation. When I hibernate it and resume it after, it becomes unstable with graphic glitches, apps freezing and becoming non responsive and within a few minutes, the system would ultimately crash.

I am running Ubuntu 22.04 LTS with a fairly recent kernel (5.15.0-47). All software up to date with updates.

What could be the cause of this post hibernation crashes and what measures can solve it once and for all? Thanks in advance for your suggestions.

2

The computer needs to be powered off and powered on and not hibernate. This is because in hibernation it stills working on backend. Or even close session is better than hibernate. It is same for either Ubuntu or Windows system.

3

What are the specifications of your computer?

1 Like
4
  • Processor: Intel Core i7-9750H (6 Cores, 12 Threads, up to 4.5 GHz)
  • Memory: 16GB DDR4 RAM
  • Storage: 512GB NVMe SSD
  • Graphics: NVIDIA GeForce GTX 1650 with 4GB GDDR5
  • Display: 15.6-inch Full HD (1920x1080) IPS
  • Operating System: Ubuntu 22.04 LTS
6

Hey, sorry for the late response. Did you figure it out?

Otherwise, my hypothesis is it has to do with your Nvidia GPU - Nvidia unfortunately does not play nicely with Linux, so you might have to do some searching.

1 Like
7

When a computer is put to sleep, all active files and the current states of open applications are stored in the system’s memory. If you encounter issues upon waking the computer, such as slow performance or crashes, it may be attributed to various factors related to the system’s memory. These could include memory speed, insufficient memory capacity, or memory leakage, where the system fails to release memory that is no longer needed. To troubleshoot this, you can use specialized RAM testing tools to detect and diagnose any potential memory-related issues.

1 Like
8

@Don11

this is a big problem with the Ubuntu and i have faced it multiple times. If you want to overcome this then simply add a cron job in your profile and then it will not go to sleep. You can also use the free -m

[gauravsablok@fedora]~% free -m
               total        used        free      shared  buff/cache   available
Mem:            7779        6952         335        1903        2819         827
Swap:           7778        7000         778

to check the memory swapped. When the virtual memory is going to overcome the running memory the process will block. I have been maintaining cluster and installing and this is my go to routine. If you are using the mount disk then edit your

nano /etc/fstab

and put the disk in the unmount state and then after login you can mount it and in this way your disk will not be read while mounting.

Alles Gute,
Gaurav

1 Like