[nvidia] Corrupted/missing shell textures when switching users or resuming from suspend

I've seen the same issue with focal and System76 Stable PPA's 460.32.03-1pop0~1611601564~20.04~11a4029~dev nvidia packaging. All text was corrupted after waking from suspend but it has only occurred once so far.

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

If you are using a Xorg session (and you probably are with Nvidia) then restarting gnome-shell might work around the problem:

1. Alt+F2

2. Type: r

3. Hit Enter

Same problem occurs for me with nvidia-driver-470. The graphical effect / issue is a bit different, yet. See attached pic... My Ubuntu 20.04 is as up-to-date as possible.

The last suggested solution is working for me (restarting gnome-shell), but this is still annoying... I've just read this : https://www.reddit.com/r/gnome/comments/k5ea3g/text_and_icon_glitching_out_after_resuming_from/ so it seems we won't have any solution before quite a long time... Fed up with nvidia !

I wonder if Nvidia has made progress on this in 510.60 since they say:

"Fixed a regression that could cause OpenGL applications to hang or render incorrectly after suspend/resume cycles or VT-switches"

[https://www.nvidia.com/download/driverResults.aspx/187162/en-us]

See also bug 1855757.

Copied the finding from https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1969142 since this bug is created long time.

Pieces of log
```
 四 14 22:55:10 kernel: NVRM: GPU at PCI:0000:01:00: GPU-581d669f-ec00-4588-ca5f-15ab24136974
 四 14 22:55:10 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=798, Graphics Exception: Shader Program Header 18 Error
 四 14 22:55:10 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=798, Graphics Exception: ESR 0x405840=0x82040000
 四 14 22:55:10 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=798, Graphics Exception: ESR 0x405848=0x80000000
 四 14 22:55:10 kernel: NVRM: Xid (PCI:0000:01:00): 13, pid=1270, Graphics Exception: ChID 0010, Class 0000c597, Offset 00000000, Data 00000000
```

For nvidia-driver, u-d-c, we need to follow
https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html
to setup the parameters after some checks.

I appended the parameters:
options nvidia NVreg_TemporaryFilePath=/run
options nvidia NVreg_PreserveVideoMemoryAllocations=1

and then the problem solved.

Tried 510.60 as well and the problem is persistent.

I can confirm that adding this file fixes the problem on Ubuntu 22.04 (using Nvidia 3080 card):

$ cat /etc/modprobe.d/nvidia-power-management.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=1

I did not have to set NVreg_TemporaryFilePath

With this set I can also use Wayland but that brings other problems, such as really stuttery video playback in at least firefox + youtube. So I stayed in X11 for now. Just note that 22.04 will default to Wayland with the above file present so I had to manually choose Ubuntu on X.org in the login screen.

I used a fresh install of 22.04.

Blank screen on 22.04 after upgrade. Re-installed nvidia 510 driver.

Even adding the following to /etc/modprobe.d/nvidia-power-management.conf does not fix the problem.

options nvidia NVreg_TemporaryFilePath=/run
options nvidia NVreg_PreserveVideoMemoryAllocations=1

Tried both gdm3 and lightdm, always get a black screen on resume. Using both MATE and default Ubuntu environments.

For comment#10:

NVreg_TemporaryFilePath means to use the specific path, if you didn't specify it then it will default to use /tmp. (if your /tmp has enough space to use then it's fine)

FWIK, the firefox is now from snap and the stable firefox is disable Wayland. Thus, it could be the other problem.

---

For comment#11:

Looks like the other issue, probably attach the log on a new bug report?

I tried to set both options mentioned on comment #11 and with X11 after resume I got corrupted lock screen and corrupted shell. I had to restart shell with alt+f2 and type r. Furthermore, I think this is the kind of problem the bug talks about.
I have a laptop with an option on BIOS to always use the NVIDIA card instead of hybrid approach, so in some cases laptops will be affected too because they act as desktops in this aspect.

Hi Marcos,

For bug description:
---
[Workarounds]

* Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter

* https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0
---

It should be workaround by adding "NVreg_PreserveVideoMemoryAllocations".
Would you please share $ cat /proc/driver/nvidia/params ?

@os369510,

Here is the content of the file as requested.

```
ResmanDebugLevel: 4294967295
RmLogonRC: 1
ModifyDeviceFiles: 1
DeviceFileUID: 0
DeviceFileGID: 0
DeviceFileMode: 438
InitializeSystemMemoryAllocations: 1
UsePageAttributeTable: 4294967295
EnableMSI: 1
RegisterForACPIEvents: 1
EnablePCIeGen3: 0
MemoryPoolSize: 0
KMallocHeapMaxSize: 0
VMallocHeapMaxSize: 0
IgnoreMMIOCheck: 0
TCEBypassMode: 0
EnableStreamMemOPs: 0
EnableUserNUMAManagement: 1
NvLinkDisable: 0
RmProfilingAdminOnly: 1
PreserveVideoMemoryAllocations: 1
EnableS0ixPowerManagement: 0
S0ixPowerManagementVideoMemoryThreshold: 256
DynamicPowerManagement: 3
DynamicPowerManagementVideoMemoryThreshold: 200
RegisterPCIDriver: 1
EnablePCIERelaxedOrderingMode: 0
EnableGpuFirmware: 18
EnableDbgBreakpoint: 0
RegistryDwords: ""
RegistryDwordsPerDevice: ""
RmMsg: ""
GpuBlacklist: ""
TemporaryFilePath: "/run"
ExcludedGpus: ""
```

Hi Macros,

would you please share the output of `journalctl -b` when issuing happening?

I executed 'journalctl -b -f' to get the logs (they are in the file) and executed systemctl suspend.

I've seen most people talking about the first solution that Nvidia documents, which is probably slow:

  "Save allocations in an unnamed temporary file"

The faster solution would be:

  "S0ix-based power management"

Both are documented in https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0

I think this highlights why the bug exists in the first place -- keeping Nvidia GPU memory alive during sleep requires more power than the GPU would usually receive (or that you would like it to use) in a sleep state.

Daniel: Desktop motherboards usually do not support "S0ix-based power management" so the other option is the only viable one for desktops.

I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the S0ix option fixed the problem for me.

I've added the following option "nvidia.NVreg_EnableS0ixPowerManagement=1" to GRUB_CMDLINE_LINUX_DEFAULT.

Unfortunately nvidia.NVreg_EnableS0ixPowerManagement=1 did not work on an old Asus Rog Maximus VIII mobo (Kabylake), nvidia 1650.

I also tried this:
/etc/modprobe.d/nvidia-power-management.conf
options nvidia NVreg_PreserveVideoMemoryAllocations=1

and it didn't work either. Missing textures after suspend. Any other hint?

Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by @vanvugt

You may wanna change the file path of the temporary file thought for better performance.

@Sebastian adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland.

Curiously though, when I try systemctl suspend-then-hibernate (my default way of suspending), I get the following in dmesg:

NVRM: GPU 0000:02:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management Support' section in the driver README.

and the machine does not suspend (I get a login prompt after 30 seconds or so). After this issue is triggered once, "systemctl suspend" also seems to break until the next reboot.

Note that "systemctl hibernate" works fine on wayland and Xorg. Also, on xorg, systemctl suspend-then-hibernate also works fine.
Could this be a bug on systemd?

>adding both the kernel parameter and the two lines in the nvidia module conf file works for "systemctl suspend" - the machine can now resume OK when on wayland.

I've tried this solution. There's a chance I've done it wrong though.

cat /etc/modprobe.d/nvidia-power-management.conf
options nvidia NVreg_TemporaryFilePath=/run
options nvidia NVreg_PreserveVideoMemoryAllocations=1

AND:

cat /etc/default/grub | grep "CMD"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia.NVreg_EnableS0ixPowerManagement=1"
GRUB_CMDLINE_LINUX=""

Upon systemctl suspend the monitor loses connection then gets its back after about 30 seconds and shows the login screen.

@robswc

I understand what you mean. I get the solution from this page:
https://forums.developer.nvidia.com/t/trouble-suspending-with-510-39-01-linux-5-16-0-freezing-of-tasks-failed-after-20-009-seconds/200933/12?u=user126177
I don't even need anyone of these configurations, just the method indicated in the post.

@mhalano

I actually just found that too!

Its amazing. I've since put it here:

https://github.com/robswc/ubuntu-22-nvidia-suspend-fix-script/blob/main/README.md

To quickly run through the steps for my other PCs.

Dear Mr Bug Watch Updater: If you are referring to https://gitlab.gnome.org/GNOME/mutter/-/issues/1942 then I would like to inform you that it was closed without fixing and the problem still remains so please explain in what way the fix is released.

Thanks.

'Fix Released' is the only supported closed state for upstream bug tasks, even when an upstream bug is closed without a fix.

'nvidia-wayland' means a bug only happens on Wayland, which this does not.

We use the 'wayland' tag to indicate that a bug can occur on Wayland, which was already done in comment #9.

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