tmpfs is a temporary filesystem that resides in memory and/or swap partition(s). Mounting directories as tmpfs can be an effective way of speeding up accesses to their files, or to ensure that their contents are automatically cleared upon reboot.
Having your resume file cleared upon reboot sounds like a no go. As the file is gone.
Can you please do systemctl status nvidia-suspend nvidia-hibernate nvidia-resume to verify that the systemd services are actually enabled? Also, how did you trigger the suspend? You need to use systemctl suspend or systemctl hibernate rather than writing to /sys/power/state directly.
Data in tmpfs is included in the hibernation image that the kernel writes to the disk, so that data should still be there during a resume from hibernation. I.e. it might be slower but it should at least still work as long as tmpfs has enough space to store the contents of video memory.
Yes, quite a bit changed in v465. There were some fixes for data corruption on some GPUs and the interaction between the X server and OpenGL clients during VT switches (which happen during suspend too) was significantly simplified when NVreg_PreserveVideoMemory=1 is enabled.
Yeah, if it actually started that service during hibernate then there should be messages about it in the journal. My system isn’t set up for hibernate but this is what I get for the similar suspend path:
> systemctl status systemd-suspend
● systemd-suspend.service - Suspend
Loaded: loaded (/usr/lib/systemd/system/systemd-suspend.service; static)
Active: inactive (dead)
Mar 30 23:08:49 aplattner systemd: Starting Suspend...
Mar 30 23:08:49 aplattner systemd-sleep: Suspending system...
Mar 31 07:43:38 aplattner systemd-sleep: System resumed.
Mar 31 07:43:38 aplattner systemd: systemd-suspend.service: Succeeded.
Mar 31 07:43:38 aplattner systemd: Finished Suspend.
Mar 31 23:29:18 aplattner systemd: Starting Suspend...
Mar 31 23:29:18 aplattner systemd-sleep: Suspending system...
Apr 01 00:39:58 aplattner systemd-sleep: System resumed.
Apr 01 00:39:58 aplattner systemd: systemd-suspend.service: Succeeded.
Apr 01 00:39:58 aplattner systemd: Finished Suspend.
I could give that beta a try later on, but at the moment i’m not sure my setup is configured correctly, so i cannot be sure that hibernate is totally non-usable with the latest PPA driver i have…
My concern about betas is that this is my main PC and crippling it with beta drivers doesn’t sound like a good idea…
If i do systemctl suspend then i can also see some log-messages as you have. These messages do not live across reboots, so i cannot 100% verify if they are there for systemctl hibernate because when i wake up from hibernate - system can’t resume and reboots, so after reboot these messages are gone
It’s good to know that you’re at least seeing the log messages from suspend. Is suspend & resume working correctly for you and it’s just hibernate that’s not working?
If possible, it might be useful to run journalctl -f & from an SSH session before triggering hibernate. If there’s something going wrong during the hibernation phase then maybe you’d see it that way. If the problem is occurring during resume then it’s a little tougher – you might be able to enable verbose logging on the kernel command line somewhere to see if there are any errors on the console, but you won’t be able to see them on the SSH connection that way.
Edit: Oh, I guess the messages in your earlier commentare from the resume phase. It’s strange that the nvidia kernel module doesn’t think it was suspended with the procfs/systemd interface there.
I’ve tried latest beta today, but i unfortunately couldn’t install it.
I first removed existing drivers with apt remove and then proceeded installing beta by running: sudo ./NVIDIA-Linux-x86_64-465.19.01.run, but installation fails. I attach /var/log/nvidia-installer.log file
With 460 and 465 versions of the driver, I cannot even see the login screen on my Ubuntu 20.04. I was able to figure out the cause was Nvidia drivers and remove them in the recovery mode. After the removal of the drivers, I can now boot my Ubuntu without any issues. However, the open-source driver is nowhere near the Nvidia drivers. So, the performance is really bad.
Although the topic is about the freezes happening after resuming from the sleep mode, I cannot even boot my Ubuntu with the 460 and 465 versions of the driver. The issue happens when booting the PC normally. I am using RTX 2060 Super.
Edit: It looks like my system upgraded the drivers from 460.73.01 to 460.80. 460.73.01 was working without issues. So, it must be related to the changes made in 460.80.
Edit 2: I downloaded 460.73.01 from launchpad and manually installed it. My system boots without issues now. I hope this gets fixed in the next release.