[nvidia] X Server session crash with "No space left on device" and then "EnterVT failed for gpu screen 0"

[giacof]

Ubuntu Release: Ubuntu 18.04.1 LTS
Package version: xserver-xorg: 1:7.7+19ubuntu7.1

When my laptop resumes after suspend, the desktop session crashes and a new one is started. So each time I lose all open applications and unsaved data!
The expected behavior would be obviously to restore the suspended session.

I had a look through log files and found that Xorg.0.log ends with the following error lines:

[ 6004.019] (II) NVIDIA(0): Setting mode "NULL"
[ 6004.026] (EE) modeset(G0): failed to set mode: No space left on device
[ 6004.026] (EE)
Fatal server error:
[ 6004.026] (EE) EnterVT failed for gpu screen 0
[ 6004.027] (EE)
[ 6004.027] (EE)
Please consult the The X.Org Foundation support
  at http://wiki.x.org
 for help.
[ 6004.027] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 6004.027] (EE)
[ 6004.065] (EE) Server terminated with error (1). Closing log file.

[Daniel van Vugt (vanvugt)]

"No space left on device" usually means your disk is full, so check that. It can also mean that the process (X server or shell) has just leaked and exhausted some particular resource.

Since it's a crash we require a stack trace to identify it properly, since it's likely other people are reporting the same. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[giacof (giacof)]

I found the file _usr_bin_nautilus.1000.crash in the directory /var/crash.
Running ubuntu-bug on that file only shows a popup and then exits, but there's an older bug I already submitted a few weeks ago: it's https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1788512

[giacof (giacof)]

By the way, I also did check my HDD and can confirm it is not full.

[giacof (giacof)]

The bug is still occurring, it is a severe bug as it makes suspend functionality totally unusable!
Do you need any further information?

[Launchpad Janitor (janitor)]

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

[Ben Echols (benpechols)]

This is happening to me right now (On Ubuntu 19.10, kernel 5.3.0 and 5.3.9, nvidia drivers version 435 and 440)

It only happens when using nvidia GPU. If I prime-select my intel GPU then there is no issue.

It seems related to the laptop display being on some internal display port that gets disconnected when the lid is closed.

If I type 'systemctl suspend' before closing my lid everything works fine when I open.

I suspect this is actually a bug in nvidia drivers and not in xorg-server

[Yaroslav Halchenko (yarikoptic)]

exactly the same issue as for Ben Echols on a Debian system with recent nvidia drivers. Initially I suspected some racing within systemd, thus filed (and later closed for now) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945158 which has supporting documentation. Did not find a workaround yet, besides making sure that laptop is fully suspended before closing the lid.

Here is the relevant diff of journalctl output (with dates etc replaceD) between two sessions (-good, +bad) which highlights the disconnect Ben was talking about and then "out of cheese" error:

-<DATE> lena gnome-shell[<PID>]: Window manager warning: Overwriting existing binding of keysym 60 with keysym 2f7259c9 (keycode 31).
+<DATE> lena systemd-logind[<PID>]: Lid closed.
+<DATE> lena gsd-color[<PID>]: failed to set screen _ICC_PROFILE: Failed to open file “/home/yoh/.local/share/icc/edid-aae8f9ad98a49dd9b5e20a8dfbf85689.icc”: Permission denied
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: 2660.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-0: 2660.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-1: 2660.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: disconnected
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: Internal TMDS
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
+<DATE> lena /usr/lib/gdm3/gdm-x-session[<PID>]: (--) NVIDIA(GPU-0):
 <DATE> lena systemd[<PID>]: Reached target Sleep.
 <DATE> lena systemd[<PID>]: Starting NVIDIA system suspend act...

[Yaroslav Halchenko (yarikoptic)]

Filed a question within nvidia forum: https://devtalk.nvidia.com/default/topic/1066963/linux/if-laptop-lid-is-closed-during-suspend-quot-failed-to-set-mode-no-space-left-on-device-quot-upon-resume/post/5406357/ so far no closure

[Giovanni Beltrame (giovanni-beltrame)]

And apparently I solved the mystery. As a desperate attempt I changed the refresh rate of the from 59.xx Hz to 60 Hz, and Xorg stopped crashing coming out of suspend. I suggest giving it a try. Note: I do not know why the screen was initially set to 59.xx Hz.

[andy1279 (michael2718)]

Changing the frame rate to 60Hz isn't an option for me. The only available frame rates are 119.99Hz, 119.97Hz, 59.96Hz and 59.95Hz.

[Daniel van Vugt (vanvugt)]

It looks like bug 1897530 might cover this but it's unclear. The fix for that is only in Ubuntu 20.10 so far.