[nvidia] System freezes on resume from suspend

[Marcel Beerli]

Linux Version: 4.15.0-36-generic
on resume from suspend, this could be a login or a minute after the screen freezes. Mouse does not move any longer.
Total crash/hang this is new since about 3 weeks or so.
All updates are installed.
I attached kern.log, about 9:14 this morning I had to reboot again.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 12 09:30:00 2018
DistUpgraded: 2018-07-08 17:00:19,279 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 640 OEM] [1043:8597]
InstallationDate: Installed on 2018-05-28 (136 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
MachineType: ASUSTeK COMPUTER INC. M70AD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=2fab21eb-af61-44eb-8a0a-f863dcc151ee ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-07-08 (95 days ago)
dmi.bios.date: 03/19/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0802
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M70AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0802:bd03/19/2014:svnASUSTeKCOMPUTERINC.:pnM70AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM70AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: M70AD
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jul 9 17:58:45 2018
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. 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.

[Daniel van Vugt (vanvugt)]

Also, next time the problem happens and you need to reboot, please collect the log of the previous boot where the bug occurred:

  journalctl -b-1 > previous_boot.txt

and attach the file previous_boot.txt here.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

Here the crash files, they are not uploading via ubuntu-bug

mbeerli@GS1:~$ ubuntu-bug _usr_share_apport_apport-gtk.0.crash
Gtk-Message: 13:34:22.500: GtkDialog mapped without a transient parent. This is discouraged.
mbeerli@GS1:~$ ubuntu-bug /var/crash/_usr_share_apport_apport-gtk.0.crash
Gtk-Message: 13:34:34.780: GtkDialog mapped without a transient parent. This is discouraged.
mbeerli@GS1:~$ sudo ubuntu-bug /var/crash/_usr_share_apport_apport-gtk.0.crash
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect: Connection refused
Segmentation fault (core dumped)
mbeerli@GS1:~$

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

Since 1. failed
2:
https://errors.ubuntu.com/user/230b4c65c3987a78cc956c8f58273b870218dcc359f8b69389d8186574ccdf290a72652c83f6032d2bb69a8b8a42cb904555b3bd931d85829dccb84aec250996

the one from 10-12-18 (today)

Here the previous_boot.txt file

[Daniel van Vugt (vanvugt)]

Thanks. I have opened bug 1797820 for your most recent desktop crash. But that's likely not the freeze we're talking about here.

Also, I can see two more problems with the system:

1. You have gnome-shell extensions running. Please disable ALL extensions and tell us if the problem still persists.

2. Strange log messages about the 'nouveau' driver. Please try installing the official nvidia driver instead:

  sudo apt install nvidia-driver-390

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

to 1)
sudo apt-get remove --auto-remove snapd

done

2)
E: Unable to locate package nvidia-driver-390

I think I tried a few things because in my settings I am missing the "Dock" option, but now it is there.

I will let you know if I have another freeze. It does not happen every time after suspend.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

Next freeze happened.
I woke system up, logged in and started Thunderbird. Thunderbird was not open yet but froze. Funny thing is that it seemed to ru in the background, because when I get a new msg, it will play a wave file and it played it.

Maybe something in the syslog file?

[Daniel van Vugt (vanvugt)]

1. Gnome shell extensions need to be disabled from the Gnome Tweaks app.

2. Try this:

  sudo apt update
  sudo apt install nvidia-driver-390

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

In the tweak app there is nothing under shell, see screenshot (its grayed out)

to 2)
the package can not be found

Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
mbeerli@GS1:~$ sudo apt install nvidia-driver-390
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package nvidia-driver-390
mbeerli@GS1:~$

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

I think you meant disable all gnome-shell extensions. I think I did now
see screenshot

[Daniel van Vugt (vanvugt)]

Click on "Extensions" in the Gnome Tweaks app.

[Daniel van Vugt (vanvugt)]

Good. Now the extensions are disabled, reboot and retest. Does the problem reoccur?

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

Yes it does.
Today is the 10-18 and it froze again. About 5-10 Standby's.
When I installed 18.04, it mentioned something about the nouveau driver.
But everything worked. This freezing is very recent, so I would think it has to do with one of the recent kernel version, maybe the 4.15.0-36 ?

Any other logs I can provide?

[Daniel van Vugt (vanvugt)]

Next please try installing the nvidia driver, using these commands:

  sudo apt update
  sudo apt install nvidia-driver-390

If that fails then please paste the full output of the failed command including the command line you typed.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

This morning was the next time.
Here the screenshot

[Daniel van Vugt (vanvugt)]

It appears that either your mirror.switch.ch server is missing the required files, or you don't have the required channel enabled.

To fix both of those, please:

 1. Open app "Software & Updates"

 2. Tick the first 4 out of 5 checkboxes.

 3. Change "Download from" to "Main server".

 4. Close the app "Software & Updates".

 5. Run: sudo apt update

 6. Run: sudo apt install nvidia-driver-390

If that fails then please paste the full output of the failed command including the command line you typed.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

I did not have "Proprietary drivers for devices (restricted)" checked.
After that I was able to install the nvidia-driver-390
I rebooted
If the hang happens again, I will report it.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

On the first wake up, the system was hanging. Worse then before with the nvidia driver, see screenshopt for options.
Should I go back to the nuveau driver?

[Daniel van Vugt (vanvugt)]

Thanks.

Next time the freeze happens again (using nvidia-390), please reboot and then run:

  journalctl -b-1 > prev_boot.txt

and attach it here.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

here the file

[Daniel van Vugt (vanvugt)]

It seems everything started to fail after resume because the X server went away:

Okt 25 05:43:31 GS1 gnome-shell[1346]: gnome-shell: Fatal IO error 0 (Success) on X server :0.

However Xorg did not crash. It just decided to shut down on system resume:

Okt 25 05:43:31 GS1 /usr/lib/gdm3/gdm-x-session[1302]: (II) Server terminated successfully (0). Closing log file.

I don't know why Xorg would decide to shut down on resume. Maybe it was a delayed reaction to using the power button? If you use the power button in a normal Linux console then indeed the normal behaviour is to shut down.

Maybe the problem was that gnome-shell misinterpreted "Fatal IO error 0 (Success)" which then started the shutdown.

[Daniel van Vugt (vanvugt)]

Oooh... that was the login screen's Xorg shutting down. So Xorg exiting was not an error:

Okt 25 05:43:31 GS1 /usr/lib/gdm3/gdm-x-session[1302]: (II) Server terminated successfully (0). Closing log file.
Okt 25 05:43:31 GS1 kernel: rfkill: input handler enabled
Okt 25 05:43:31 GS1 gdm-launch-environment][1247]: pam_unix(gdm-launch-environment:session): session closed for user gdm

Almost as if a VT switch has happened on resume.

However we're now talking about a different problem to that in the bug description. The bug description talks about problems during login. But your title was "System freezes after suspend".

So which bug would you like to discuss?

[Daniel van Vugt (vanvugt)]

Please change the bug title and description to cover just one problem, because it sounds like two unrelated issues at the moment.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

My main issue is "on resume from suspend" which I never had with 16.04. I probably had 30-50 resumes before I rebooted after a kernel update.
In the mean time I am on 4.15.0-38.
I assume I removed the gnome-shell, also I switched from nouveau to nvidia-driver-390
I had several (5) resumes after my last reboot and no issue yet. It does not happen all the time.
I did change the subject as suggested.

[Daniel van Vugt (vanvugt)]

Please also change the bug description in the same way.

[Marcel Beerli (493pocbrcycmdw7yksonho9o2qzzq06652mtv6nw76-admin-d18ecat4t1b76tkfi3vttrkfngli4hci2jxl2sxy9j)]

done

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.