Resume from suspend to RAM fails with nvidia-graphics-drivers-390

Bug #1777279 reported by Jaroslaw Ilgiewicz on 2018-06-16
36
This bug affects 8 people
Affects Status Importance Assigned to Milestone
nvidia-graphics-drivers-390 (Ubuntu)
Undecided
Unassigned

Bug Description

After suspending to RAM when resuming only black screen is visible with frozen mouse cursor. Can't switch to console and reset is required. When trying to suspend to RAM with pm-suspend command system doesn't suspend at all, you can find pm-suspend.log file attached. With default nouveau drivers system resumes fine however hangs forever on shutdown.
My specs:
AMD Ryzen 5 1600
Kingston Predator DDR4 8GB
Gigabyte GA-AB350N-Gaming WIFI
MSI GeForce GTX 1060 AERO ITX
SSD Crucial MX500 500GB

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-22-generic 4.15.0-22.24
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jaroslaw 1386 F.... pulseaudio
 /dev/snd/controlC1: jaroslaw 1386 F.... pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Sat Jun 16 21:38:21 2018
InstallationDate: Installed on 2018-05-16 (31 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=b5a92bcf-517e-4b97-ab26-84dbab8247c5 ro quiet splash resume=/dev/sda2 resume_offset=19075072 vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-22-generic N/A
 linux-backports-modules-4.15.0-22-generic N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/17/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23d
dmi.board.asset.tag: Default string
dmi.board.name: AB350N-Gaming WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350N-Gaming WIFI
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Jaroslaw Ilgiewicz (jarekil) wrote :
Jaroslaw Ilgiewicz (jarekil) wrote :

version.log

Jaroslaw Ilgiewicz (jarekil) wrote :

lspci-vnvn.log

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Jaroslaw Ilgiewicz (jarekil) wrote :

I remotely connected with ssh to my frozen desktop and generated dmesg2.log. You can see in this file errors related to GPU.

affects: linux (Ubuntu) → nvidia-graphics-drivers-390 (Ubuntu)
Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: Confirmed → New
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-390 (Ubuntu):
status: New → Confirmed
Gerhard Hagerer (ghagerer) wrote :

I got a workaround for suspend working on Ubuntu 18.04 with a NVIDIA GeForce GTX 1050 Mobile and proprietary nvidia drivers 390. I installed pm-suspend via ```sudo apt-get install pm-utils```. Then, I switch from Gnome Shell to the terminal via Ctrl+Alt+f6. After the login, I do ```sudo pm-suspend```. After waking up from standby, I change back to Gnome Shell via Ctrl+Alt+f1. Done!

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers