I can confirm the "nouveau.modeset=0" trick seems to be working for me
so far (meaning, I am able to suspend the system again).
I upgraded from 16.04 two days ago - suspend has been working fine for
the entire lifetime of the 16.04 install.
A colleague has also reported suspend/hibernate problems on her new
windows-based machine,also with nVidia screen card. Strange.
Hardware:
MSI Ge62 2QE Apache Pro
Intel Core i7
nVidia GTX965M
`uname -r` :
4.15.0-32-generic
`lsb_release --all` :
LSB Version:core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
`lshw -c video | grep configuration`
configuration: driver=nvidia latency=0
configuration: driver=i915 latency=0
` modinfo nvidia`:
filename: /lib/modules/4.15.0-32-generic/updates/dkms/nvidia.ko
alias: char-major-195-*
version:390.48
supported: external
license:NVIDIA
srcversion: FA33B00C00A6F70EC9CF314
alias: pci:v10DEd0E00sv*sd*bc04sc80i00*
alias: pci:v10DEd*sv*sd*bc03sc02i00*
alias: pci:v10DEd*sv*sd*bc03sc00i00*
depends:ipmi_msghandler
retpoline: Y
name: nvidia
vermagic: 4.15.0-32-generic SMP mod_unload
parm: NVreg_Mobile:int
parm: NVreg_ResmanDebugLevel:int
parm: NVreg_RmLogonRC:int
parm: NVreg_ModifyDeviceFiles:int
parm: NVreg_DeviceFileUID:int
parm: NVreg_DeviceFileGID:int
parm: NVreg_DeviceFileMode:int
parm: NVreg_UpdateMemoryTypes:int
parm: NVreg_InitializeSystemMemoryAllocations:int
parm: NVreg_UsePageAttributeTable:int
parm: NVreg_MapRegistersEarly:int
parm: NVreg_RegisterForACPIEvents:int
parm: NVreg_CheckPCIConfigSpace:int
parm: NVreg_EnablePCIeGen3:int
parm: NVreg_EnableMSI:int
parm: NVreg_TCEBypassMode:int
parm: NVreg_UseThreadedInterrupts:int
parm: NVreg_EnableStreamMemOPs:int
parm: NVreg_EnableBacklightHandler:int
parm: NVreg_EnableUserNUMAManagement:int
parm: NVreg_EnableIBMNPURelaxedOrderingMode:int
parm: NVreg_MemoryPoolSize:int
parm: NVreg_IgnoreMMIOCheck:int
parm: NVreg_RegistryDwords:charp
parm: NVreg_RegistryDwordsPerDevice:charp
parm: NVreg_RmMsg:charp
parm: NVreg_AssignGpus:charp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1774950
Title:
Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and
Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Fix Released
Bug description:
===SRU Justification===
[Impact]
Systems with acpi-lpss can't do S3/S4 on Bionic.
[Test]
Users confirmed these patches work for them.
[Fix]
Commit a192aa923b66a (ACPI / LPSS: Consolidate runtime PM and system
sleep handling) applies quirks for both runtime and system suspend.
This causes problems for some systems, so avoid using quirks on S3 and
S4.
[Regression Potential]
Low. These patches are in upstream stable, and it brings back driver's
old behavior.
===Original Bug Report===
I have installed Kubuntu 18.04 on 3 different machines (my friend's and my
own) with no suspend problems but my HP Pavilion 11 x360 does not suspend.
It suspends fine with Ubuntu 17.10, Kubuntu 17.10, Devuan Jesse,
Devuan ASCII and Windows 10 but fails with Ubuntu 18.04 and Kubuntu
18.04.
I have also tried suspend using a live USB of 18.04 on this machine
and it fails in the same way, so does not appear to be caused by any
additional programs that I had installed.
By installing an older kernel (4.14) on Kubuntu 18.04 the suspend
function works as expected.
Running Kubuntu 18.04 with kernels 4.15, 4.16, 4.17 results in the
suspend failure that freezes the machine and requires a hard reset.
Correct behaviour is -
Screen goes blank, fan goes off, power LED flashes to show machine is
in suspend. Pressing power button triggers 'resume' function.
What happens -
Screen goes blank, fan stays on, power LED stays on. Machine stays in
this state and does not respond to any keyboard interaction, mouse
movement or power button presses.
Ctrl + Alt + f1 (or f2, f3, f4 etc) does not get any response.
The only way to use the machine is to shut down by holding down the
power button.
Checking the logs suggests that the machine believes it is in suspend
mode sleep [deep] when it isn't.
Having to hard reset to get any response means that the kernel logs
say no more than sleep [deep]
pm-suspend also results in the same pr
