[Dell XPS 15 7590] Cannot resume after suspend

Bug #1975454 reported by fcole90
54
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

For some weeks I notice that my laptop cannot resume after suspend. When I try to resume it, instead of the usual password prompt, I'm greeted by a black screen with the following text:

```
Bluetooth hcio: Timed out waiting for suspend events
Bluetooth hcio: Suspend timeout bit: 6
Bluetooth hcio: Suspend notifier action (3) failed: -110
```
(There might be typos, I retyped it from a photo)

Then, I don't seem able to do anything, not even change virtual terminal. So I need to reboot and lose my previous session.

I noticed it seemed to happen since 22.04 came out of beta, but the timing also coincides with me starting using a Bluetooth mouse, so that might be connected.

Let me know if you need more information or digging into the logs

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.129.06 Thu May 12 22:52:02 UTC 2022
 GCC version: gcc version 11.2.0 (Ubuntu 11.2.0-19ubuntu1)
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May 23 08:44:30 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 nvidia/470.129.06, 5.15.0-27-generic, x86_64: installed
 nvidia/470.129.06, 5.15.0-30-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-30-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:0905]
   Subsystem: Dell TU117M [GeForce GTX 1650 Mobile / Max-Q] [1028:0905]
InstallationDate: Installed on 2020-04-03 (779 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
MachineType: Dell Inc. XPS 15 7590
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-30-generic root=UUID=4f215b94-50a2-44af-b8c6-faf7cea8214a ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/09/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 0VYV0G
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/09/2021:br1.15:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr:sku0905:
dmi.product.family: XPS
dmi.product.name: XPS 15 7590
dmi.product.sku: 0905
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

Revision history for this message
fcole90 (fcole90) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks for the bug report. Next time the problem happens, after rebooting run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

tags: added: nvidia
affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Miha Wagner (mishmash) wrote :

I got the exact same bug as described in this ticket. Today I upgraded from 20.04.4 to 22.04. Before I never got this bug but first time opening the lid after upgrade I got this and had to reboot the system.

Attached is the prevboot.txt as requested in the above comment.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Miha, please open a new bug of your own with that attachment.

Revision history for this message
Triangle Stone (shaped-rock) wrote :

Same issue, same device. I've tried creating a new bug report but it just gets stuck on 'Please wait while bug data is processed. This page will refresh every 10 seconds until processing is complete.' indefinitely so I'm posting my logs here.

summary: - Cannot resume after suspend
+ [Dell XPS 15 7590] Cannot resume after suspend
affects: ubuntu → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
fcole90 (fcole90) wrote :

Hej, I had been waiting to reproduce this, in order to upload the needed logs, but this has never happened again since my report.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Make sure you don't have 'tlp' installed because it can cause problems like this on any machine type.

Revision history for this message
Triangle Stone (shaped-rock) wrote :

'tlp' is not installed on my machine.

Revision history for this message
Daniel van Vugt (vanvugt) wrote (last edit ):

Incomplete: Waiting for the original reporter (fcole90) to answer comment #2.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
fcole90 (fcole90) wrote :

Hi Daniel, this just happened again but it seems I had no persistent journaling..

$ journalctl -b-1 > prevboot.txt
An error was encountered while opening journal file or directory /var/log/journal, ignoring file: Not a directory
Specifying boot ID or boot offset has no effect, no persistent journal was found.

I'm now setting it up following this guide: https://gist.github.com/JPvRiel/b7c185833da32631fa6ce65b40836887

I filed another bug report related to this, but for something that happened after the reboot:
 - Bluetooth icon appears and disappears after reboot https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1981117

Revision history for this message
fcole90 (fcole90) wrote :

P.S. No, tlp is not installed on my machine

$ sudo apt purge tlp
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'tlp' is not installed, so not removed

I update this as soon as I'm able to get the journal log you need.

Have a good day!

Revision history for this message
Philippe (philippepiatkiewitz) wrote (last edit ):

I have the same issue, also on an XPS-15 (9500).
I have attached the boot log from when it happened.

The relevant section is:

Jul 20 08:21:07 philippe-XPS-15 systemd-logind[805]: Lid opened.
Jul 20 08:21:09 philippe-XPS-15 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Failed to acquire idle monitor proxy: Timeout was reached
Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
Jul 20 08:21:20 philippe-XPS-15 gsd-power[2784]: Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Reached target Sleep.
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting Record successful boot for GRUB...
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting NVIDIA system suspend actions...
Jul 20 08:21:20 philippe-XPS-15 suspend[8292]: nvidia-suspend.service
Jul 20 08:21:20 philippe-XPS-15 logger[8292]: <13>Jul 20 08:21:20 suspend: nvidia-suspend.service
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: grub-common.service: Deactivated successfully.
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Finished Record successful boot for GRUB.
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Starting GRUB failed boot detection...
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Jul 20 08:21:20 philippe-XPS-15 systemd[1]: Finished GRUB failed boot detection.
Jul 20 08:21:28 philippe-XPS-15 gsd-color[2772]: failed to set xrandr-Sharp Corporation color transform matrix: Timeout was reached
Jul 20 08:21:29 philippe-XPS-15 systemd-logind[805]: Power key pressed.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Philippe, please open a new bug from that machine by running:

  ubuntu-bug linux

Revision history for this message
Philippe (philippepiatkiewitz) wrote :
Revision history for this message
fcole90 (fcole90) wrote :

Hi, here's the needed log, finally :D

Changed in linux (Ubuntu):
status: Incomplete → New
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. The log in comment #15 looks like the system is trying to resume, and Xorg is trying to resume. So I would bet this is probably an Nvidia driver problem.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

fcole90,

The next step is to temporarily remove Nvidia from the equation. Please try:

  * Disable the Nvidia GPU in the BIOS if you can; or
  * Uninstall the Nvidia driver; or
  * Select 'Ubuntu on Wayland' at the login screen

affects: linux (Ubuntu) → ubuntu
Changed in ubuntu:
status: Confirmed → Incomplete
Revision history for this message
fcole90 (fcole90) wrote :

Thanks, I will keep you up to date!

After checking the logs, do you have some suggestions on reproducing this quickly, without needing to wait for it to happen randomly? Otherwise, after disabling the GPU, it'd be hard to say if it just didn't happen by chance, or if it's not going to happen anymore 🤔

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I would start by finding out how frequently resume fails with the Nvidia driver still active. Like reproducing the bug 5 times. Then you have a good idea for whether removing it later has made a difference.

Revision history for this message
fcole90 (fcole90) wrote :

Since I reported this, it happened only 3-4 times (that's why it took me so long before adding the logs). So, I'd say it's not frequent at all.

I normally use my laptop with the charger always connected. I think this bug has often happened when the laptop was not charging (I don't remember however if it was not connected only when it went into suspend, only when it woke up, or both). I might try to take the charger out from time to time, to see if I can make it happen more often and see a pattern.

Revision history for this message
Ernst Persson (ernstp) wrote :

I had something similar happen on a HP Pavilion All-in-One Desktop 27-ca1xxx with hybrid Nvidia graphics. Ubuntu 22.04, Nvidia 515. So it's a desktop but the graphics setup is basically a laptop. RTX 3050 Ti.
Some percentage of every suspend resume gets stuck in console mode, perhaps 20% of the time. This was with everything X11.

I found a workaround was to switch to Wayland actually. Switched GDM and my session.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ernst, please report your own bug so we can investigate the system in detail. To report a new bug just run:

  ubuntu-bug gnome-shell

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.