535 Driver breaks S3 suspend preserving video memory on RTX 4000 SFF Ada, 525 & 530 fine

My computer, a ThinkStation P360 Ultra, contains an NVIDIA RTX 4000 SFF Ada card, and supports S3 deep sleep by default. As you might know, nvidia.NVreg_PreserveVideoMemoryAllocations=1is required to preserve video memory in RAM or on disk when the computer enters S3 sleep. This parameter used to work flawlessly on 525 and 530, but if I include this kernel parameter on the 535 driver, my computer will no longer suspend at all unless the preserve video memory parameter is removed, even when nvidia.NVreg_TemporaryFilePath is set to /tmp or /var/tmp. Instead, the computer just wakes right back up and never enters full suspend. I get a bunch of errors in the logs about the pcie video card not being handled properly by the kernel on suspend, namely a failure to enter a certain power state. Without the preserve memory parameter, this means it’s impossible to preserve video memory on suspend with 535, which is highly frustrating. I’ve tested this across multiple Linux distros including Manjaro Arch, EndeavourOS Arch, Ubuntu, Linux Mint 21.2, and Fedora 38 and the behavior is all the same, where suspend doesn’t work and the computer just wakes back up with this parameter passed. Doesn’t seem to matter what kernel version either, tried 5.19 through 6.4. Without the inclusion of this particular parameter, upon resume suspend video memory might as well have been discarded completely and it’s impossible to resume playing videos or games without reopening them. I have even experienced crashing on Firefox with a YouTube video paused post resume without nvidia.NVreg_PreserveVideoMemoryAllocations=1set in the kernel parameters. What gives? I’m not sure if something has changed in the new drivers that needs to be set, or if NVIDIA has forsaken proper S3 suspend support for their most expensive SFF card on the market (RTX 4000 SFF Ada) on Linux. I can produce logs on Linux Mint which I’m currently running if required, but I’d rather stay on a working driver for the moment. Please let me know what can be done about this problem or if anyone else is experiencing this suspend issue on this card or other cards. Thank you for your help and please let me know if you need something to confirm this bug.

1 Like

Have you found anything new? I have the same problem. I would downgrade if i could, but i need cuda 12 and it will automatically uninstall driver 525 and install 535. Steam proton games also don’t work with 535.

Well, I actually managed to downgrade to the old 530 release and the original 525 release myself in Linux Mint and the problem still persisted. I then swapped out the RTX 4000 SFF Ada with the RTX A2000 in my Lenovo P360 Ultra and unfortunately suspend didn’t work there either even after reinstalling multiple different Linux distros. It appears this might actually be a Lenovo BIOS issue, I recall there being several BIOS updates relatively recently. I guess… I’ll have to get another machine. :(

I’m trying out a maxed out configuration of the Lenovo P3 Ultra with NVIDIA A5500 Mobile graphics courtesy of the Labor Day sale and I’ll let you know if suspend works on Linux there, if not I’m returning it.

Please let me know if you manage to get suspend working on the old RTX A2000 12GB card that comes with the machine. Thanks! It was a royal pain to replace the card myself and I don’t want to risk breaking my computer by attempting to swap it out with the RTX 4000 SFF Ada again.

I think something may be wrong with Lenovo’s firmware on the P360 Ultra.

I have a RTX A1000 I think and I can downgrade to 525 (and lose cuda 12) but then suspend works again.
It is a Dell 35xx and i also latly had a few bios updates but the problem for me is 535.