You are not logged in.

#26 2024-07-21 21:24:23

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

Ah, soory - I confused you for the OP.
The overall situation is known and the 555xx drivers actually disable the user session freeze - saronno probably has a somewhat different issue (also the session freeze will break the suspend *entirely*, not cause some black session sometims)

Offline

#27 2024-07-21 21:34:25

NotYourAlejandro
Member
Registered: 2024-07-21
Posts: 5

Re: Nvidia and systemd .... I can't resume properly.

lol no worries tongue
I'm not 100% sure what OP's issue is, but mine was mostly about visual corruption when resuming from suspend on Wayland, and for some reason I was curious as to why some userspace applications were preventing suspend (leaving the system in a hung black-screen-but-still-awake state) on both my desktop and laptop. I had that same log entry and the problem behavior appears to be quite similar, so fingers crossed this works for OP.

On another note, I do wonder why that environment variable is set to 0 in the first place. The mailing list says it's a known issue that could cause some sort of issues with the nvidia proprietary driver, but I wish I knew what the issue(s) were. I might do some deeper investigation since I'm kinda bored and curious.

Offline

#28 2024-07-21 22:14:54

NotYourAlejandro
Member
Registered: 2024-07-21
Posts: 5

Re: Nvidia and systemd .... I can't resume properly.

Well, after some brief searching, it appears this is a known regression in systemd version 256 (which would explain why this thread is so recent). A fix for this has been made and has been pushed appropriately. Of course, all of this is assuming this was the solution to OP's issue in the first place.
https://github.com/systemd/systemd/issues/33626

Offline

#29 2024-07-21 22:20:41

seth
Member
Registered: 2012-09-03
Posts: 61,014

Offline

#30 2024-07-21 22:29:26

NotYourAlejandro
Member
Registered: 2024-07-21
Posts: 5

Re: Nvidia and systemd .... I can't resume properly.

Neat, I'm glad that's the case.

Best of luck, OP, to figuring this out.

Offline

#31 2024-07-27 22:04:13

saronno
Member
Registered: 2009-10-02
Posts: 213

Re: Nvidia and systemd .... I can't resume properly.

yep, I can confirm it's another problem .... still fighting.

Offline

#32 2024-07-28 08:03:34

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

Could you confirm that

seth wrote:

If it's VRAM decay, longer sleeps have a much higher chance of causing this.

and did you

seth wrote:

try to add sleep hooks to disable and re-enable the compositor around the S3

?

Offline

#33 2025-01-29 21:18:23

asklow
Member
Registered: 2022-11-07
Posts: 63

Re: Nvidia and systemd .... I can't resume properly.

User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).

Doesn't this mean that we shouldn't explicitly request user freeze ? Like:

$SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=1

?

Offline

#34 2025-01-29 23:08:26

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

Session freeze is the default behavior but has caused several issues (which are not actually limited to the nvidia driver) which is why the nvidia-utils packages disables them, resulting in that message.

Offline

#35 2025-01-30 02:29:39

asklow
Member
Registered: 2022-11-07
Posts: 63

Re: Nvidia and systemd .... I can't resume properly.

I regularly have this issue while suspend. It's too annoying that I stopped suspending altogether. Isn't there at least a temporary solution for this memory thing ?

Offline

#36 2025-01-30 08:08:43

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

What issue? On what status quo?
The thread started out 6 months w/ missing VRAM preservation (which has nothing to do with the user session freeze which is disabled and enabling it will unlikely help you w/ S2/3 issues)

Please don't hijack threads that sound vaguely related by posting some unrelated out of context token and then asking what to do about your situation.
Open a new thread, explain the problem you're facing and ideally illustrate it with the system journal covering such incident resp. the general configuration of your system.

Storing the VRAM in some tmpfs will cause issues if you've a lot of VRAM and little (free) RAM and vram preservation + early kms + S4 ("hibernation") is recorded to not work for a race condition.

Offline

#37 2025-01-30 12:37:06

asklow
Member
Registered: 2022-11-07
Posts: 63

Re: Nvidia and systemd .... I can't resume properly.

Because I face the same issue. I don't seem to see any journal error other than the above user freeze warning. As others said, the only way to fix it is to force shut down, in which the journal stops logging and starts logging the next session. And it's very random too. Sometimes shuts down normally and sometimes doesn't & goes blank.

This is when the hang occured & I have to abrupt force reboot:

Jan 30 07:55:05 arch systemd-logind[659]: The system will suspend now!
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8631] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8631] device (enp4s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8715] manager: NetworkManager state is now ASLEEP
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8717] device (enp0s20f0u7): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 30 07:55:05 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 30 07:55:05 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8966] device (enp0s20f0u7): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8968] dhcp4 (enp0s20f0u7): canceled DHCP transaction
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8968] dhcp4 (enp0s20f0u7): activation: beginning transaction (timeout in 45 seconds)
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.8968] dhcp4 (enp0s20f0u7): state changed no lease
Jan 30 07:55:05 arch systemd-resolved[513]: enp0s20f0u7: Bus client set default route setting: no
Jan 30 07:55:05 arch systemd-resolved[513]: enp0s20f0u7: Bus client reset DNS server list.
Jan 30 07:55:05 arch NetworkManager[655]: <info>  [1738203905.9446] device (enp0s20f0u7): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 30 07:55:05 arch systemd[1]: Reached target Sleep.
Jan 30 07:55:05 arch systemd[1]: Starting NVIDIA system suspend actions...
Jan 30 07:55:05 arch suspend[28072]: nvidia-suspend.service
Jan 30 07:55:05 arch logger[28072]: <13>Jan 30 07:55:05 suspend: nvidia-suspend.service
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/ldac
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aptx
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aac
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aac
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_g
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_g
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/sbc
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/sbc
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/faststream
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_05
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_05
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 30 07:55:06 arch bluetoothd[656]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 30 07:55:06 arch systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 30 07:55:06 arch systemd[1]: Finished NVIDIA system suspend actions.
Jan 30 07:55:06 arch systemd[1]: nvidia-suspend.service: Consumed 707ms CPU time, 354.4M memory peak.
Jan 30 07:55:06 arch systemd[1]: Starting System Suspend...
Jan 30 07:55:06 arch systemd-sleep[28093]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jan 30 07:55:06 arch systemd-sleep[28093]: This is not recommended, and might result in unexpected behavior, particularly
Jan 30 07:55:06 arch systemd-sleep[28093]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 30 07:55:06 arch systemd-sleep[28093]: Performing sleep operation 'suspend'...
Jan 30 07:55:06 arch kernel: PM: suspend entry (deep)
-- Boot ea38a5c8002a411c87befc7a568fd504 --
Jan 30 08:50:15 arch kernel: Linux version 6.12.10-zen1-1-zen (linux-zen@archlinux) (gcc (GCC) 14.2.1 20240910, GNU ld (GNU Binutils) 2.43.1) #1 ZEN SMP PREEMPT_DYNAMIC Sat, 18 Jan 2025 02:26:52 +0000

This is when it normally suspended, waited 10 sec & then resumed just now:

Jan 30 18:01:34 arch systemd-logind[653]: The system will suspend now!
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.5835] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.5836] device (enp4s0): state change: unavailable -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.5924] manager: NetworkManager state is now ASLEEP
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.5925] device (enp0s20f0u7): state change: activated -> deactivating (reason 'sleeping', managed-type: 'full')
Jan 30 18:01:34 arch systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 30 18:01:34 arch systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.6166] device (enp0s20f0u7): state change: deactivating -> disconnected (reason 'sleeping', managed-type: 'full')
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.6168] dhcp4 (enp0s20f0u7): canceled DHCP transaction
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.6168] dhcp4 (enp0s20f0u7): activation: beginning transaction (timeout in 45 seconds)
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.6168] dhcp4 (enp0s20f0u7): state changed no lease
Jan 30 18:01:34 arch systemd-resolved[532]: enp0s20f0u7: Bus client set default route setting: no
Jan 30 18:01:34 arch systemd-resolved[532]: enp0s20f0u7: Bus client reset DNS server list.
Jan 30 18:01:34 arch NetworkManager[649]: <info>  [1738240294.6546] device (enp0s20f0u7): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', managed-type: 'full')
Jan 30 18:01:34 arch systemd[1]: Reached target Sleep.
Jan 30 18:01:34 arch systemd[1]: Starting NVIDIA system suspend actions...
Jan 30 18:01:34 arch suspend[1865]: nvidia-suspend.service
Jan 30 18:01:34 arch logger[1865]: <13>Jan 30 18:01:34 suspend: nvidia-suspend.service
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/ldac
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aptx
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/aac
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aac
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_g
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_g
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/sbc
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/sbc
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/faststream
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_05
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_05
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 30 18:01:34 arch bluetoothd[650]: Endpoint unregistered: sender=:1.20 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 30 18:01:35 arch systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jan 30 18:01:35 arch systemd[1]: Finished NVIDIA system suspend actions.
Jan 30 18:01:35 arch systemd[1]: nvidia-suspend.service: Consumed 673ms CPU time, 226.9M memory peak.
Jan 30 18:01:35 arch systemd[1]: Starting System Suspend...
Jan 30 18:01:35 arch systemd-sleep[1884]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jan 30 18:01:35 arch systemd-sleep[1884]: This is not recommended, and might result in unexpected behavior, particularly
Jan 30 18:01:35 arch systemd-sleep[1884]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jan 30 18:01:35 arch systemd-sleep[1884]: Performing sleep operation 'suspend'...
Jan 30 18:01:35 arch kernel: PM: suspend entry (deep)
Jan 30 18:01:35 arch kernel: Filesystems sync: 0.231 seconds
Jan 30 18:01:45 arch kernel: Freezing user space processes
Jan 30 18:01:45 arch kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jan 30 18:01:45 arch kernel: OOM killer disabled.
Jan 30 18:01:45 arch kernel: Freezing remaining freezable tasks
Jan 30 18:01:45 arch kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
Jan 30 18:01:45 arch kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jan 30 18:01:45 arch kernel: serial 00:02: disabled
Jan 30 18:01:45 arch kernel: parport_pc 00:01: disabled
Jan 30 18:01:45 arch kernel: ACPI: PM: Preparing to enter system sleep state S3
Jan 30 18:01:45 arch kernel: ACPI: PM: Saving platform NVS memory
Jan 30 18:01:45 arch kernel: Disabling non-boot CPUs ...
Jan 30 18:01:45 arch kernel: smpboot: CPU 5 is now offline
Jan 30 18:01:45 arch kernel: smpboot: CPU 4 is now offline
Jan 30 18:01:45 arch kernel: smpboot: CPU 3 is now offline
Jan 30 18:01:45 arch kernel: smpboot: CPU 2 is now offline
Jan 30 18:01:45 arch kernel: smpboot: CPU 1 is now offline
Jan 30 18:01:45 arch kernel: ACPI: PM: Low-level resume complete
Jan 30 18:01:45 arch kernel: ACPI: PM: Restoring platform NVS memory
Jan 30 18:01:45 arch kernel: Enabling non-boot CPUs ...
Jan 30 18:01:45 arch kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jan 30 18:01:45 arch kernel: CPU1 is up
Jan 30 18:01:45 arch kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jan 30 18:01:45 arch kernel: CPU2 is up
Jan 30 18:01:45 arch kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jan 30 18:01:45 arch kernel: CPU3 is up
Jan 30 18:01:45 arch kernel: smpboot: Booting Node 0 Processor 4 APIC 0x8
Jan 30 18:01:45 arch kernel: CPU4 is up
Jan 30 18:01:45 arch kernel: smpboot: Booting Node 0 Processor 5 APIC 0xa
Jan 30 18:01:45 arch kernel: CPU5 is up
Jan 30 18:01:45 arch kernel: ACPI: PM: Waking up from system sleep state S3
Jan 30 18:01:45 arch kernel: parport_pc 00:01: activated
Jan 30 18:01:45 arch kernel: serial 00:02: activated
Jan 30 18:01:45 arch kernel: xhci_hcd 0000:01:00.2: xHC error in resume, USBSTS 0x401, Reinit
Jan 30 18:01:45 arch kernel: usb usb3: root hub lost power or was reset
Jan 30 18:01:45 arch kernel: usb usb4: root hub lost power or was reset
Jan 30 18:01:45 arch kernel: OOM killer enabled.
Jan 30 18:01:45 arch kernel: Restarting tasks ... done.
Jan 30 18:01:45 arch kernel: random: crng reseeded on system resumption
Jan 30 18:01:45 arch systemd-resolved[532]: Clock change detected. Flushing caches.
Jan 30 18:01:45 arch systemd-sleep[1884]: System returned from sleep operation 'suspend'.
Jan 30 18:01:45 arch bluetoothd[650]: Controller resume with wake event 0x0
Jan 30 18:01:45 arch kernel: PM: suspend exit
Jan 30 18:01:45 arch kernel: nvme nvme0: 6/0/0 default/read/poll queues
Jan 30 18:01:45 arch systemd[1]: systemd-suspend.service: Deactivated successfully.
Jan 30 18:01:45 arch systemd[1]: Finished System Suspend.
Jan 30 18:01:45 arch systemd[1]: Stopped target Sleep.
Jan 30 18:01:45 arch systemd[1]: Reached target Suspend.
Jan 30 18:01:45 arch systemd-logind[653]: Operation 'suspend' finished.
Jan 30 18:01:45 arch systemd-resolved[532]: Closing all remaining TCP connections.
Jan 30 18:01:45 arch systemd-resolved[532]: Resetting learnt feature levels on all servers.
Jan 30 18:01:45 arch NetworkManager[649]: <info>  [1738240305.9966] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Jan 30 18:01:45 arch NetworkManager[649]: <info>  [1738240305.9966] device (enp0s20f0u7): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 30 18:01:45 arch NetworkManager[649]: <info>  [1738240305.9974] device (enp4s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')
Jan 30 18:01:45 arch systemd[1]: Starting NVIDIA system resume actions...
Jan 30 18:01:45 arch systemd[1]: Stopped target Suspend.
Jan 30 18:01:45 arch wireplumber[713]: default: Failed to get percentage from UPower: org.freedesktop.DBus.Error.NameHasNoOwner
Jan 30 18:01:46 arch wireplumber[713]: spa.bluez5.midi: org.bluez.GattManager1.RegisterApplication() failed: GDBus.Error:org.bluez.Error.AlreadyExists: Already Exists
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/ldac
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx_hd
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_hd
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aptx
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/aac
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aac
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_g
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_g
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/sbc
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/sbc
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/faststream_duplex
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Jan 30 18:01:46 arch bluetoothd[650]: Endpoint registered: sender=:1.45 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Jan 30 18:01:46 arch suspend[1962]: nvidia-resume.service
Jan 30 18:01:46 arch logger[1962]: <13>Jan 30 18:01:46 suspend: nvidia-resume.service
Jan 30 18:01:46 arch systemd[1]: nvidia-resume.service: Deactivated successfully.
Jan 30 18:01:46 arch systemd[1]: Finished NVIDIA system resume actions.
Jan 30 18:01:46 arch kernel: Generic FE-GE Realtek PHY r8169-0-400:00: attached PHY driver (mii_bus:phy_addr=r8169-0-400:00, irq=MAC)
Jan 30 18:01:46 arch NetworkManager[649]: <info>  [1738240306.1416] manager: NetworkManager state is now DISCONNECTED

And I haven't modifed root at all. It also seems that the no freeze config already exists

 ~ $ cat /usr/lib/systemd/system/systemd-suspend.service.d/10-nvidia-no-freeze-session.conf 
[Service]
Environment="SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=false"
 ~ $ 

The specs are GTX1660S (with 6 gigs VRAM) and 16 gigs ddr4. I do have tmpfs through pam which is around 50% by default.

Last edited by asklow (2025-01-30 12:54:07)

Offline

#38 2025-01-30 13:51:10

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

Forget about the systemd thing, in doubt try to disable https://wiki.archlinux.org/title/NVIDIA … er_suspend (module parameter and services)
This will lead to corrupted GL contexts, wayland and GL compositors will not respond well to that ansd show you black or garbled pixmaps.

Wrt you're not getting any journal, it cannot be synced to disk when you push the power button - see whether you can reboot using the https://wiki.archlinux.org/title/Keyboa … el_(SysRq) (nb. thatyou've to enable that before any crash)

Offline

#39 2025-02-04 09:41:46

asklow
Member
Registered: 2022-11-07
Posts: 63

Re: Nvidia and systemd .... I can't resume properly.

I don't think it is power button issue, as it's consistent behaviour across suspensions, reboots, shutdown command & power button too.
An interesting thing is I have tried disabling memory allocation using official documentation through kernel parameter

NVreg_PreserveVideoMemoryAllocations=0

& ran mkinitcpio. I will report back whether it fixed or not. Because this issue is very random & was occuring when I suspend multiple times.

Last edited by asklow (2025-02-04 10:12:41)

Offline

#40 2025-02-04 10:31:22

GrimBandito
Member
Registered: 2016-12-04
Posts: 46

Re: Nvidia and systemd .... I can't resume properly.

Long shot but could you check the following services are enabled in systemd....

sudo systemctl enable nvidia-suspend.service
sudo systemctl enable nvidia-hibernate.service
sudo systemctl enable nvidia-resume.service

The nvidia driver should enable these by default, however I have found this not to always be the case.

Try the above and give your system a reboot.

Last edited by GrimBandito (2025-02-04 11:12:51)

Offline

#41 2025-02-04 10:56:28

asklow
Member
Registered: 2022-11-07
Posts: 63

Re: Nvidia and systemd .... I can't resume properly.

They are enabled by default on arch, including the memory allocation. These weren't enabled by default before. Now they do.
Although, I do think they may not be necessary if I disable memory preservation ? I will try different combinations of configurations, with or without services, with or without memory preservation and check if any combination is stable enough to make suspension work.

Last edited by asklow (2025-02-04 10:57:01)

Offline

#42 2025-02-04 14:24:37

seth
Member
Registered: 2012-09-03
Posts: 61,014

Re: Nvidia and systemd .... I can't resume properly.

I don't think it is power button issue

The point was that as soon as you push the power button to reboot, you cannot expect any journals of the previous boot to be preserved - they got lost between RAM and SSD.

Although, I do think they may not be necessary if I disable memory preservation ?

If you don't keep them in sync, the services will complain about the state of the module parameter.

Offline

Board footer

Powered by FluxBB