Ubuntu 18.04 completely freezes after waking from suspend to memory
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I suspect I'm having the same problem on the same laptop (HP Probook 4540s with after market SSD) than the user posted here and I'm really battling to find the solution.
After suspending to memory and waking again, the laptop hangs completely withing 2 - 10s. When it hangs I'm not even able to open the console using ctrl alt F2. Only solution is to hold down the power button.
My kernel version is "Linux version 4.18.0-16-generic" and all app are updated as of 2019/03/20.
What I have tired so var:
rmmod hp_accel hp_wmi hp_wireless
Did this just before suspending in the hope that it might be one of the HP drivers as this seems to be specific to HP. No luck.
Had the failure, hard reboot and then have a look at journal, but there is nothing from after we went to sleep.
Ran the following command:
echo mem | sudo tee /sys/power/state; journalctl -f
This is handy as the sleep does not lock the device requiring login again, giving you some time to try an figure out whats happening. Problem is that journal does not spit anything out (once had a few lines pop out, not hanging for about 10s but nothing from journal from after suspend).
The above two tests points me to an issue in journal, but I've not been able to disable journal to test this.
Any think I can try and test? Problem is VERY reproducible.
Graphics card is a Intel® Sandybridge Mobile and I have been having this issue even from a fresh install.
EDIT
free -h
total used free shared buff/cache available
Mem: 3.7G 1.2G 1.3G 231M 1.3G 2.1G
Swap: 2.0G 0B 2.0G
sudo blkid
/dev/sda2: UUID="e29950d0-4e71-45fd-8081-ce907359e16c" TYPE="ext4" PARTUUID="e0cefbf7-4e11-437c-909e-a1a3acbfa1a8"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="5CAB-AE29" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="f51590a1-535e-4ce2-86cb-b2b61589962c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
cat /etc/fstab
UUID=e29950d0-4e71-45fd-8081-ce907359e16c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=5CAB-AE29 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
cat /etc/initramfs-tools/conf.d/resume
I have the dir but not the file...
grep -i resume /etc/default/grub
Returns nothing...
EDIT 2
Results from lsblk -a
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6405
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 34.6M 1 loop /snap/gtk-common-themes/818
loop3 7:3 0 14.8M 1 loop /snap/gnome-characters/206
loop4 7:4 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop5 7:5 0 271.7M 1 loop /snap/pycharm-community/117
loop6 7:6 0 14.5M 1 loop /snap/gnome-logs/45
loop7 7:7 0 2.3M 1 loop /snap/gnome-calculator/260
loop8 7:8 0 3.7M 1 loop /snap/gnome-system-monitor/57
loop9 7:9 0 4M 1 loop /snap/gnome-calculator/352
loop10 7:10 0 34.8M 1 loop /snap/gtk-common-themes/1122
loop11 7:11 0 13M 1 loop /snap/gnome-characters/139
loop12 7:12 0 91M 1 loop /snap/core/6350
loop13 7:13 0 53.7M 1 loop /snap/core18/782
loop14 7:14 0 3.7M 1 loop /snap/gnome-system-monitor/70
loop15 7:15 0 140.7M 1 loop /snap/gnome-3-26-1604/78
loop16 7:16 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop17 7:17 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop18 7:18 0 140.7M 1 loop /snap/gnome-3-26-1604/74
loop19 7:19 0 1008K 1 loop /snap/gnome-logs/57
loop20 7:20 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
EDIT 3
Removed all the snap apps that I could install with apt and now I only have the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6350
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 53.7M 1 loop /snap/core18/782
loop3 7:3 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop4 7:4 0 91M 1 loop /snap/core/6405
loop5 7:5 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop6 7:6 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop7 7:7 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
Also increased the swap file to 6GB
18.04 hp
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
|
show 9 more comments
I suspect I'm having the same problem on the same laptop (HP Probook 4540s with after market SSD) than the user posted here and I'm really battling to find the solution.
After suspending to memory and waking again, the laptop hangs completely withing 2 - 10s. When it hangs I'm not even able to open the console using ctrl alt F2. Only solution is to hold down the power button.
My kernel version is "Linux version 4.18.0-16-generic" and all app are updated as of 2019/03/20.
What I have tired so var:
rmmod hp_accel hp_wmi hp_wireless
Did this just before suspending in the hope that it might be one of the HP drivers as this seems to be specific to HP. No luck.
Had the failure, hard reboot and then have a look at journal, but there is nothing from after we went to sleep.
Ran the following command:
echo mem | sudo tee /sys/power/state; journalctl -f
This is handy as the sleep does not lock the device requiring login again, giving you some time to try an figure out whats happening. Problem is that journal does not spit anything out (once had a few lines pop out, not hanging for about 10s but nothing from journal from after suspend).
The above two tests points me to an issue in journal, but I've not been able to disable journal to test this.
Any think I can try and test? Problem is VERY reproducible.
Graphics card is a Intel® Sandybridge Mobile and I have been having this issue even from a fresh install.
EDIT
free -h
total used free shared buff/cache available
Mem: 3.7G 1.2G 1.3G 231M 1.3G 2.1G
Swap: 2.0G 0B 2.0G
sudo blkid
/dev/sda2: UUID="e29950d0-4e71-45fd-8081-ce907359e16c" TYPE="ext4" PARTUUID="e0cefbf7-4e11-437c-909e-a1a3acbfa1a8"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="5CAB-AE29" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="f51590a1-535e-4ce2-86cb-b2b61589962c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
cat /etc/fstab
UUID=e29950d0-4e71-45fd-8081-ce907359e16c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=5CAB-AE29 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
cat /etc/initramfs-tools/conf.d/resume
I have the dir but not the file...
grep -i resume /etc/default/grub
Returns nothing...
EDIT 2
Results from lsblk -a
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6405
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 34.6M 1 loop /snap/gtk-common-themes/818
loop3 7:3 0 14.8M 1 loop /snap/gnome-characters/206
loop4 7:4 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop5 7:5 0 271.7M 1 loop /snap/pycharm-community/117
loop6 7:6 0 14.5M 1 loop /snap/gnome-logs/45
loop7 7:7 0 2.3M 1 loop /snap/gnome-calculator/260
loop8 7:8 0 3.7M 1 loop /snap/gnome-system-monitor/57
loop9 7:9 0 4M 1 loop /snap/gnome-calculator/352
loop10 7:10 0 34.8M 1 loop /snap/gtk-common-themes/1122
loop11 7:11 0 13M 1 loop /snap/gnome-characters/139
loop12 7:12 0 91M 1 loop /snap/core/6350
loop13 7:13 0 53.7M 1 loop /snap/core18/782
loop14 7:14 0 3.7M 1 loop /snap/gnome-system-monitor/70
loop15 7:15 0 140.7M 1 loop /snap/gnome-3-26-1604/78
loop16 7:16 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop17 7:17 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop18 7:18 0 140.7M 1 loop /snap/gnome-3-26-1604/74
loop19 7:19 0 1008K 1 loop /snap/gnome-logs/57
loop20 7:20 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
EDIT 3
Removed all the snap apps that I could install with apt and now I only have the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6350
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 53.7M 1 loop /snap/core18/782
loop3 7:3 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop4 7:4 0 91M 1 loop /snap/core/6405
loop5 7:5 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop6 7:6 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop7 7:7 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
Also increased the swap file to 6GB
18.04 hp
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Edit your question (not into the comments please) to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resumeandgrep -i resume /etc/default/grub. Report back to @heynnema
– heynnema
Mar 23 at 14:35
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51
|
show 9 more comments
I suspect I'm having the same problem on the same laptop (HP Probook 4540s with after market SSD) than the user posted here and I'm really battling to find the solution.
After suspending to memory and waking again, the laptop hangs completely withing 2 - 10s. When it hangs I'm not even able to open the console using ctrl alt F2. Only solution is to hold down the power button.
My kernel version is "Linux version 4.18.0-16-generic" and all app are updated as of 2019/03/20.
What I have tired so var:
rmmod hp_accel hp_wmi hp_wireless
Did this just before suspending in the hope that it might be one of the HP drivers as this seems to be specific to HP. No luck.
Had the failure, hard reboot and then have a look at journal, but there is nothing from after we went to sleep.
Ran the following command:
echo mem | sudo tee /sys/power/state; journalctl -f
This is handy as the sleep does not lock the device requiring login again, giving you some time to try an figure out whats happening. Problem is that journal does not spit anything out (once had a few lines pop out, not hanging for about 10s but nothing from journal from after suspend).
The above two tests points me to an issue in journal, but I've not been able to disable journal to test this.
Any think I can try and test? Problem is VERY reproducible.
Graphics card is a Intel® Sandybridge Mobile and I have been having this issue even from a fresh install.
EDIT
free -h
total used free shared buff/cache available
Mem: 3.7G 1.2G 1.3G 231M 1.3G 2.1G
Swap: 2.0G 0B 2.0G
sudo blkid
/dev/sda2: UUID="e29950d0-4e71-45fd-8081-ce907359e16c" TYPE="ext4" PARTUUID="e0cefbf7-4e11-437c-909e-a1a3acbfa1a8"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="5CAB-AE29" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="f51590a1-535e-4ce2-86cb-b2b61589962c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
cat /etc/fstab
UUID=e29950d0-4e71-45fd-8081-ce907359e16c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=5CAB-AE29 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
cat /etc/initramfs-tools/conf.d/resume
I have the dir but not the file...
grep -i resume /etc/default/grub
Returns nothing...
EDIT 2
Results from lsblk -a
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6405
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 34.6M 1 loop /snap/gtk-common-themes/818
loop3 7:3 0 14.8M 1 loop /snap/gnome-characters/206
loop4 7:4 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop5 7:5 0 271.7M 1 loop /snap/pycharm-community/117
loop6 7:6 0 14.5M 1 loop /snap/gnome-logs/45
loop7 7:7 0 2.3M 1 loop /snap/gnome-calculator/260
loop8 7:8 0 3.7M 1 loop /snap/gnome-system-monitor/57
loop9 7:9 0 4M 1 loop /snap/gnome-calculator/352
loop10 7:10 0 34.8M 1 loop /snap/gtk-common-themes/1122
loop11 7:11 0 13M 1 loop /snap/gnome-characters/139
loop12 7:12 0 91M 1 loop /snap/core/6350
loop13 7:13 0 53.7M 1 loop /snap/core18/782
loop14 7:14 0 3.7M 1 loop /snap/gnome-system-monitor/70
loop15 7:15 0 140.7M 1 loop /snap/gnome-3-26-1604/78
loop16 7:16 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop17 7:17 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop18 7:18 0 140.7M 1 loop /snap/gnome-3-26-1604/74
loop19 7:19 0 1008K 1 loop /snap/gnome-logs/57
loop20 7:20 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
EDIT 3
Removed all the snap apps that I could install with apt and now I only have the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6350
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 53.7M 1 loop /snap/core18/782
loop3 7:3 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop4 7:4 0 91M 1 loop /snap/core/6405
loop5 7:5 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop6 7:6 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop7 7:7 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
Also increased the swap file to 6GB
18.04 hp
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
I suspect I'm having the same problem on the same laptop (HP Probook 4540s with after market SSD) than the user posted here and I'm really battling to find the solution.
After suspending to memory and waking again, the laptop hangs completely withing 2 - 10s. When it hangs I'm not even able to open the console using ctrl alt F2. Only solution is to hold down the power button.
My kernel version is "Linux version 4.18.0-16-generic" and all app are updated as of 2019/03/20.
What I have tired so var:
rmmod hp_accel hp_wmi hp_wireless
Did this just before suspending in the hope that it might be one of the HP drivers as this seems to be specific to HP. No luck.
Had the failure, hard reboot and then have a look at journal, but there is nothing from after we went to sleep.
Ran the following command:
echo mem | sudo tee /sys/power/state; journalctl -f
This is handy as the sleep does not lock the device requiring login again, giving you some time to try an figure out whats happening. Problem is that journal does not spit anything out (once had a few lines pop out, not hanging for about 10s but nothing from journal from after suspend).
The above two tests points me to an issue in journal, but I've not been able to disable journal to test this.
Any think I can try and test? Problem is VERY reproducible.
Graphics card is a Intel® Sandybridge Mobile and I have been having this issue even from a fresh install.
EDIT
free -h
total used free shared buff/cache available
Mem: 3.7G 1.2G 1.3G 231M 1.3G 2.1G
Swap: 2.0G 0B 2.0G
sudo blkid
/dev/sda2: UUID="e29950d0-4e71-45fd-8081-ce907359e16c" TYPE="ext4" PARTUUID="e0cefbf7-4e11-437c-909e-a1a3acbfa1a8"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/sda1: UUID="5CAB-AE29" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="f51590a1-535e-4ce2-86cb-b2b61589962c"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
cat /etc/fstab
UUID=e29950d0-4e71-45fd-8081-ce907359e16c / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=5CAB-AE29 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
cat /etc/initramfs-tools/conf.d/resume
I have the dir but not the file...
grep -i resume /etc/default/grub
Returns nothing...
EDIT 2
Results from lsblk -a
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6405
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 34.6M 1 loop /snap/gtk-common-themes/818
loop3 7:3 0 14.8M 1 loop /snap/gnome-characters/206
loop4 7:4 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop5 7:5 0 271.7M 1 loop /snap/pycharm-community/117
loop6 7:6 0 14.5M 1 loop /snap/gnome-logs/45
loop7 7:7 0 2.3M 1 loop /snap/gnome-calculator/260
loop8 7:8 0 3.7M 1 loop /snap/gnome-system-monitor/57
loop9 7:9 0 4M 1 loop /snap/gnome-calculator/352
loop10 7:10 0 34.8M 1 loop /snap/gtk-common-themes/1122
loop11 7:11 0 13M 1 loop /snap/gnome-characters/139
loop12 7:12 0 91M 1 loop /snap/core/6350
loop13 7:13 0 53.7M 1 loop /snap/core18/782
loop14 7:14 0 3.7M 1 loop /snap/gnome-system-monitor/70
loop15 7:15 0 140.7M 1 loop /snap/gnome-3-26-1604/78
loop16 7:16 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop17 7:17 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop18 7:18 0 140.7M 1 loop /snap/gnome-3-26-1604/74
loop19 7:19 0 1008K 1 loop /snap/gnome-logs/57
loop20 7:20 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
EDIT 3
Removed all the snap apps that I could install with apt and now I only have the following:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 91M 1 loop /snap/core/6350
loop1 7:1 0 91.1M 1 loop /snap/core/6531
loop2 7:2 0 53.7M 1 loop /snap/core18/782
loop3 7:3 0 35.3M 1 loop /snap/gtk-common-themes/1198
loop4 7:4 0 91M 1 loop /snap/core/6405
loop5 7:5 0 143.5M 1 loop /snap/gnome-3-28-1804/23
loop6 7:6 0 140.7M 1 loop /snap/gnome-3-26-1604/82
loop7 7:7 0 0 loop
sda 8:0 0 465.8G 0 disk
├─sda1 8:1 0 512M 0 part /boot/efi
└─sda2 8:2 0 465.3G 0 part /
Also increased the swap file to 6GB
18.04 hp
18.04 hp
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
edited Mar 27 at 14:46
Christo Labuschagne
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
asked Mar 23 at 11:50
Christo LabuschagneChristo Labuschagne
11
11
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Edit your question (not into the comments please) to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resumeandgrep -i resume /etc/default/grub. Report back to @heynnema
– heynnema
Mar 23 at 14:35
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51
|
show 9 more comments
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Edit your question (not into the comments please) to include the output offree -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resumeandgrep -i resume /etc/default/grub. Report back to @heynnema
– heynnema
Mar 23 at 14:35
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Edit your question (not into the comments please) to include the output of
free -h and sudo blkid and cat /etc/fstab and cat /etc/initramfs-tools/conf.d/resume and grep -i resume /etc/default/grub. Report back to @heynnema– heynnema
Mar 23 at 14:35
Edit your question (not into the comments please) to include the output of
free -h and sudo blkid and cat /etc/fstab and cat /etc/initramfs-tools/conf.d/resume and grep -i resume /etc/default/grub. Report back to @heynnema– heynnema
Mar 23 at 14:35
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51
|
show 9 more comments
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128041%2fubuntu-18-04-completely-freezes-after-waking-from-suspend-to-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1128041%2fubuntu-18-04-completely-freezes-after-waking-from-suspend-to-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Did you check your RAM (e.g. using MemTest)? I've experienced similar issues with bad RAM modules. Is your firmware up to date?
– danzel
Mar 23 at 12:18
Edit your question (not into the comments please) to include the output of
free -handsudo blkidandcat /etc/fstabandcat /etc/initramfs-tools/conf.d/resumeandgrep -i resume /etc/default/grub. Report back to @heynnema– heynnema
Mar 23 at 14:35
@heynnema, I've added the info you requested.
– Christo Labuschagne
Mar 25 at 5:27
@danzel. If you are referring to bios firmware, then yes, updated a few weeks ago (before installing ubuntu 18.04) and I ran its mem test this morning with a pass. Do you have another mem test that you prefer I run?
– Christo Labuschagne
Mar 25 at 6:07
@ChristoLabuschagne How do you "suspend to memory"? Has this always been a problem, or something new that just started?
– heynnema
Mar 25 at 6:51