[nouveau] Screen freeze after closing lid and suspend

[Chelmite]

Starting a few days ago, after I close my laptop lid and Ubuntu suspends, I get only a black screen (and the power light is on) when I open the laptop lid.
I tried various 3-finger salutes, and nothing changes. There is no cursor. I cannot get to the console screens. The only thing that works is holding the power button until the laptop shuts off.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-7642.46~1598628707~20.04~040157c~dev-generic 5.4.44
Uname: Linux 5.4.0-7642-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu27.10
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus]
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 21 14:25:22 2020
DistUpgraded: 2020-05-01 18:43:33,860 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703]
InstallationDate: Installed on 2017-11-01 (1085 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System76, Inc. Serval WS
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7642-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro acpi_sleep=nonvs quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-05-02 (172 days ago)
dmi.bios.date: 07/11/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.10RSA1
dmi.board.asset.tag: Tag 12345
dmi.board.name: Serval WS
dmi.board.vendor: System76, Inc.
dmi.board.version: serw9
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Serval WS
dmi.product.sku: Not Applicable
dmi.product.version: serw9
dmi.sys.vendor: System76, Inc.
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

[Chelmite (steve-kelem)]

The same thing happens when I lock my screen. When I come back, the power has shut off. Pressing the power button starts what looks like a power-up, but it ends up with just a black screen. None of the keys seem to do anything. I have to power-cycle my laptop to get it to work again.

[Daniel van Vugt (vanvugt)]

This is probably due to the open source 'nouveau' driver the system is using. Please open the 'Additional Drivers' app and use it to install the Nvidia driver it recommends.

If the problem continues to happen after that then next time the freeze occurs:

  1. Wait for 10 seconds.

  2. Reboot.

  3. Run these commands:

     journalctl -b-1 > prevboot.txt
     lspci -kv > newlspci.txt

     and attach the resulting text files here.

[Chelmite (steve-kelem)]

Installing the nvidia driver did the trick. It wasn't easy...it wanted to create a userid and gid=122, which was already occupied by a different group. I created them manually at uid=gid=152, and then I was able to install, after getting rid of the --extragroups option to useradd.

[Daniel van Vugt (vanvugt)]

OK well if you are happy then we can declare this "Won't Fix". Because the slower, buggier, open source driver probably won't get fixed if nobody *needs* it and is motivated to debug it.

[Chelmite (steve-kelem)]

I'm (sort of) happy that I can use my computer again.

If this project is active, then change the status of this bug to something appropriate, and I'll support you.

Philosophically, I'd prefer to be running an open-source version of the software, but I need to get stuff done in the meantime.

Installing the proprietary version is a workaround. (Which has its own problems...after awakening from Suspend, screen icon text is illegible.)

[Daniel van Vugt (vanvugt)]

> If this project is active, then change the status of this bug to something appropriate, and I'll support you.

OK in that case I can reopen this bug and we next request that you:

 1. Uninstall the proprietary Nvidia driver.

 2. Reproduce the original bug.

 3. Test newer kernel versions and tell us which, if any, fix the problem:
    https://kernel.ubuntu.com/~kernel-ppa/mainline/

> Installing the proprietary version is a workaround. (Which has its own
> problems...after awakening from Suspend, screen icon text is illegible.)

I know that problem - it is specific to the Nvidia driver. But I am not aware of any official bug report for it yet. Please open a new bug for that.

[Launchpad Janitor (janitor)]

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