Issues resuming from hybrid-sleep

Graphics / Linux Linux
1

Hi,

Foremost I would like to emphasize that “systemctl suspend” and “systemctl hibernate” works without issues. However, I have an issue resuming from “systemctl hybrid-sleep”. When resuming, the display shows the same as before suspending but the system is completely unresponsive (although I can ssh in perfectly fine) and Xorg is spinning at at 100% on one cpu thread.

dmesg has the following error is present:

nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices

Checking the Xorg.log has the following:

[ 417.567] (II) modeset(0): EDID vendor “AUO”, prod id 13035
[ 417.567] (II) modeset(0): Printing DDC gathered Modelines:
[ 417.567] (II) modeset(0): Modeline "3840x2160"x0.0 533.30 3840 3888 3920 4000 2160 2163 2168 2222 -hsync -vsync (133.3 kHz eP)
[ 417.583] (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
[ 417.583] (–) NVIDIA(GPU-0): DFP-0: disconnected
[ 417.583] (–) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 417.583] (–) NVIDIA(GPU-0): DFP-0: 1440.0 MHz maximum pixel clock
[ 417.583] (–) NVIDIA(GPU-0):
[ 417.583] (–) NVIDIA(GPU-0): DFP-1: disconnected
[ 417.583] (–) NVIDIA(GPU-0): DFP-1: Internal DisplayPort
[ 417.583] (–) NVIDIA(GPU-0): DFP-1: 1440.0 MHz maximum pixel clock
[ 417.583] (–) NVIDIA(GPU-0):
[ 417.583] (–) NVIDIA(GPU-0): DFP-2: disconnected
[ 417.583] (–) NVIDIA(GPU-0): DFP-2: Internal TMDS
[ 417.583] (–) NVIDIA(GPU-0): DFP-2: 165.0 MHz maximum pixel clock
[ 417.583] (–) NVIDIA(GPU-0):
[ 417.583] (EE) NVIDIA(GPU-0): Failed to query object info.
[ 417.583] (EE) NVIDIA(GPU-0): Failed to query object info.
[ 417.590] (EE) NVIDIA(GPU-0): Failed to query object info.

System is a Lenovo Thinkpad X1E Gen.1 with GTX 1050 Ti Max-Q, running with 440.100 driver and 5.7.7 kernel. It is set up with Prime working (as er instructions here on the forum)

Following troubleshooting attempted:
Tried enabling and disabling the i915 module in initramfs
Tried running intel card with “intel” and “modesetting” driver
Running nvidia with systemd power management and without
Tried boot parameters acpi_osi=! "acpi_osi=Windows 2015" and acpi_osi=Linux"

I’m at a loss so any help is greatly appreciated.

2

Hi @henriker, did you ever solve this issue? I am running into something similar when resuming from hybrid-sleep. Sleep and regular hibernate work just fine.

Specs:
Arch Linux
Kernel 5.11.2
RTX 3090 with 460.56 drivers

Mar 05 20:52:52 benxiao-arch01 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 05 20:52:52 benxiao-arch01 kernel: nvidia-modeset: ERROR: GPU:0: Failed detecting connected display devices
Mar 05 20:52:52 benxiao-arch01 kernel: nvidia-modeset: WARNING: GPU:0: Failure processing EDID for display device Acer XB271HU (DP-2).
Mar 05 20:52:52 benxiao-arch01 upowerd[1487]: treating change event as add on /sys/devices/pci0000:00/0000:00:01.2/0000:01:00.0/0000:02:08.0/0000:09:00.3/usb3/3-4
Mar 05 20:52:52 benxiao-arch01 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device Acer XB271HU (DP-2)
Mar 05 20:52:52 benxiao-arch01 kernel: nvidia-modeset: ERROR: GPU:0: Failure reading maximum pixel clock value for display device DP-2.
Mar 05 20:52:52 benxiao-arch01 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000224
Mar 05 20:52:52 benxiao-arch01 kernel: #PF: supervisor read access in kernel mode
Mar 05 20:52:52 benxiao-arch01 kernel: #PF: error_code(0x0000) - not-present page
Mar 05 20:52:52 benxiao-arch01 kernel: PGD 0 P4D 0 
Mar 05 20:52:52 benxiao-arch01 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Mar 05 20:52:52 benxiao-arch01 kernel: CPU: 9 PID: 990 Comm: Xorg Tainted: P           OE     5.11.2-arch1-1 #1
Mar 05 20:52:52 benxiao-arch01 kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./X570 Taichi, BIOS P4.00 01/19/2021
Mar 05 20:52:52 benxiao-arch01 kernel: RIP: 0010:_nv002315kms+0x57/0xa0 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel: Code: 28 00 48 89 46 18 48 8b 87 e8 05 00 00 48 8b 80 a8 01 00 00 48 85 c0 74 52 53 48 89 f3 e8 b1 54 56 c6 ba 04 00 00 00 48 63 ca <8b> 74 c8 08 85 f6 74 29 48 8d 04 c8 0f b7 48 08 66 89 4b 20 0f b7
Mar 05 20:52:52 benxiao-arch01 kernel: RSP: 0018:ffffadec01e97998 EFLAGS: 00010206
Mar 05 20:52:52 benxiao-arch01 kernel: RAX: 00000000000001fc RBX: ffffadec01e97c90 RCX: 0000000000000004
Mar 05 20:52:52 benxiao-arch01 kernel: RDX: 0000000000000004 RSI: ffffadec01e97c90 RDI: ffff9cf6aba63008
Mar 05 20:52:52 benxiao-arch01 kernel: RBP: ffffadec01e85008 R08: 0000000000000280 R09: ffffadec00715008
Mar 05 20:52:52 benxiao-arch01 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9cf68b939c08
Mar 05 20:52:52 benxiao-arch01 kernel: R13: 0000000000000001 R14: ffff9cf6b7002814 R15: 0000000000000000
Mar 05 20:52:52 benxiao-arch01 kernel: FS:  00007f6ea29d3940(0000) GS:ffff9cfd9ec40000(0000) knlGS:0000000000000000
Mar 05 20:52:52 benxiao-arch01 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 05 20:52:52 benxiao-arch01 kernel: CR2: 0000000000000224 CR3: 0000000123876000 CR4: 0000000000350ee0
Mar 05 20:52:52 benxiao-arch01 kernel: Call Trace:
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000076kms+0x118/0x170 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv002327kms+0xb3/0x5b0 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv002457kms+0x53/0x60 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? __d_alloc+0x22/0x1e0
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000742kms+0xfc/0x370 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000742kms+0xbf/0x370 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? desc_read_finalized_seq+0x37/0x90
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv002771kms+0x433/0x600 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv002771kms+0x3fc/0x600 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? nvkms_alloc+0x61/0x90 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000742kms+0x40/0x40 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? _nv000744kms+0x2a/0x40 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? nvkms_ioctl+0x10f/0x180 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? nvidia_frontend_unlocked_ioctl+0x37/0x50 [nvidia]
Mar 05 20:52:52 benxiao-arch01 kernel:  ? __x64_sys_ioctl+0x83/0xb0
Mar 05 20:52:52 benxiao-arch01 kernel:  ? do_syscall_64+0x33/0x40
Mar 05 20:52:52 benxiao-arch01 kernel:  ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
Mar 05 20:52:52 benxiao-arch01 kernel: Modules linked in: snd_seq_dummy snd_hrtimer snd_seq rfcomm ccm hid_logitech_hidpp mousedev joydev hid_logitech_dj uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_usb_audio snd_usbmidi_lib ses snd_rawmidi enclosure snd_seq_device scsi_>
Mar 05 20:52:52 benxiao-arch01 kernel:  xt_addrtype snd_compress xt_tcpudp kvm ac97_bus snd_pcm_dmaengine irqbypass snd_pcm drm_kms_helper crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel snd_timer wmi_bmof mxm_wmi crypto_simd cryptd glue_helper xt_conntrack cec snd rapl syscopyarea sysfillrect sysimg>
Mar 05 20:52:52 benxiao-arch01 kernel: CR2: 0000000000000224
Mar 05 20:52:52 benxiao-arch01 kernel: ---[ end trace 2fe4d965292e60bc ]---
Mar 05 20:52:52 benxiao-arch01 kernel: RIP: 0010:_nv002315kms+0x57/0xa0 [nvidia_modeset]
Mar 05 20:52:52 benxiao-arch01 kernel: Code: 28 00 48 89 46 18 48 8b 87 e8 05 00 00 48 8b 80 a8 01 00 00 48 85 c0 74 52 53 48 89 f3 e8 b1 54 56 c6 ba 04 00 00 00 48 63 ca <8b> 74 c8 08 85 f6 74 29 48 8d 04 c8 0f b7 48 08 66 89 4b 20 0f b7
Mar 05 20:52:52 benxiao-arch01 kernel: RSP: 0018:ffffadec01e97998 EFLAGS: 00010206
Mar 05 20:52:52 benxiao-arch01 kernel: RAX: 00000000000001fc RBX: ffffadec01e97c90 RCX: 0000000000000004
Mar 05 20:52:52 benxiao-arch01 kernel: RDX: 0000000000000004 RSI: ffffadec01e97c90 RDI: ffff9cf6aba63008
Mar 05 20:52:52 benxiao-arch01 kernel: RBP: ffffadec01e85008 R08: 0000000000000280 R09: ffffadec00715008
Mar 05 20:52:52 benxiao-arch01 kernel: R10: 0000000000000000 R11: 0000000000000001 R12: ffff9cf68b939c08
Mar 05 20:52:52 benxiao-arch01 kernel: R13: 0000000000000001 R14: ffff9cf6b7002814 R15: 0000000000000000
Mar 05 20:52:52 benxiao-arch01 kernel: FS:  00007f6ea29d3940(0000) GS:ffff9cfd9ec40000(0000) knlGS:0000000000000000
Mar 05 20:52:52 benxiao-arch01 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Mar 05 20:52:52 benxiao-arch01 kernel: CR2: 0000000000000224 CR3: 0000000123876000 CR4: 0000000000350ee0
3

I have the exact same issue when resuming from hybrid-sleep: X server process takes 100% CPU and can’t be killed even with SIGKILL. Restarting the display manager from an ssh session works after a long timeout for the systemd unit. I didn’t get anything fishy in the kernel log, though. The only error I have is in the Xorg.0.log, which says

(EE) NVIDIA(GPU-0): Failed to query object info.

systemd suspend and systemd hibernate work just fine.

My spec:
Arch Linux with 5.11.6 kernel
GPU 1650Ti with driver 460.56

4

Hi,

Same problem here, same log entries as OP.

Lenovo Ideapad Z500, kernel 5.10.27, Nvidia drivers 460.xx.

Can someone from Nvidia please help?

Thanks

5

I have the same issue.

Device: MSI GL63-8SE
Kernel: 5.12.18-1-ck-skylake
Driver: nvidia-dkms-470.63.01
GPU: RTX 2060 Mobile

If someone at Nvidia can help, it would be greatly appreciated.

Thanks in advance.

6

Just confirming that I have the same issue. Tried modesetting driver, changing acpi into firmware, and also this solution: Systemd's suspend-then-hibernate not working in NVIDIA Optimus laptop - #4 by charles15 . Nothing worked. Hibernation and sleep work just fine.

Kernel: Linux 6.0.11-arch1-1 x86_64
GPU: RTX 3070
Nvidia driver: 525.60.11-2

7

I still have the very same issue in 2024. Hibernate and suspend work fine, the problem only occurs on waking up from hybrid-suspend.

System: Ubuntu 22.04 LTS
Device: Dell Inspiron 7590 with built-in display
Kernel: Linux 6.5.0-35-generic x86_64
GPU: NVIDIA GeForce GTX 1650
Driver: 550.67

The issue was also active on driver version 535.171.04. And a complete uninstall of the driver does solve the issue (but I still need the driver).

The only useful information from journalctl is “Failed to enter interactive mode” and “Failed to query object info”.

systemd[1]: Stopped target Sleep.
systemd[1]: Stopped target Hybrid Suspend+Hibernate.
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:69
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:74
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:67
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:65
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:73
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:75
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:66
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:68
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:71
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 13:72
/usr/libexec/gdm-x-session[2240]: (II) systemd-logind: got resume for 226:0
/usr/libexec/gdm-x-session[2240]: (II) AIGLX: Resuming AIGLX clients after VT switch
systemd-logind[912]: Operation 'sleep' finished.
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): EDID vendor "AUO", prod id 9453
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Printing DDC gathered Modelines:
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (67.1 kHz eP)
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Modeline "1920x1080"x0.0  112.80  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (53.7 kHz e)
ModemManager[956]: <info>  [sleep-monitor-systemd] system is resuming
NetworkManager[874]: <info>  [1718186915.8193] manager: sleep: wake requested (sleeping: yes  enabled: yes)
NetworkManager[874]: <info>  [1718186915.8194] device (wlp61s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
kernel: rfkill: input handler disabled
kernel: iwlwifi 0000:3d:00.0: WRT: Invalid buffer destination
kernel: workqueue: set_brightness_delayed hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): EDID vendor "AUO", prod id 9453
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Printing DDC gathered Modelines:
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (67.1 kHz eP)
/usr/libexec/gdm-x-session[2240]: (II) modeset(0): Modeline "1920x1080"x0.0  112.80  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (53.7 kHz e)
/usr/libexec/gdm-x-session[2240]: (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
/usr/libexec/gdm-x-session[2240]: (EE) NVIDIA(GPU-0): Failed to query object info.
/usr/libexec/gdm-x-session[2240]: (EE) NVIDIA(GPU-0): Failed to query object info.
/usr/libexec/gdm-x-session[2240]: (EE) NVIDIA(GPU-0): Failed to query object info.

I’m still happy to test out other solutions or provide a more detailed log if someone with expertise would specify.

8

Hi All,
I tried to reproduce issue internally on notebook with GeForce RTX 4060 and latest beta driver 555.42.02 but no luck.
Request to please share nvidia bug report from repro state along with repro frequency.
Also please let us know how long you usually keep system in sleep mode before resuming it.

10

tl;dr

I tried to add an nvidia-hybrid-sleep service but there was no luck.

After investigating the systemd files installed by nvidia driver,
I found that the systemd-hybrid-sleep.service doesn’t depend on either
nvidia-suspend.service or nvidia-hibernate.service
like systemd-suspend and systemd-hibernate do.

Those two nvidia services execute the /usr/bin/nvidia-sleep.sh script before suspend/hibernate. Without dependencies, the script won’t run at all throughout the hybrid sleep power cycle. So I add a custom systemd file to imitate the behaviour of nvidia-hibernate.service.

$ sudo nano /etc/systemd/system/nvidia-hybrid-sleep.service

[Unit]
Description=NVIDIA system hybrid-suspend service
Before=systemd-hybrid-sleep.service

[Service]
Type=oneshot
ExecStart=/usr/bin/logger -t hibernate -s "nvidia-hybrid-sleep.service"
ExecStart=/usr/bin/nvidia-sleep.sh "hibernate"

[Install]
WantedBy=systemd-hybrid-sleep.service

As well as a drop-in for nvidia-resume.service to let it be depended on system-hybrid-sleep.service.

$ sudo mkdir /etc/systemd/system/nvidia-resume.service.d
$ sudo nano /etc/systemd/system/nvidia-resume.service.d/override.conf

[Unit]
After=systemd-hybrid-sleep.service

[Install]
WantedBy=systemd-hybrid-sleep.service

Then reload systemctl and enable those services.

$ sudo systemctl daemon-reload
$ sudo systemctl enable nvidia-resume.service
$ sudo systemctl enable nvidia-hybrid-sleep.service

After all of this work, the nvidia-sleep.sh is properly run both before hybrid sleep and after resume like it would do during a normal hibernation.

The bad news is the script itself isn’t working as intended, as it would taint the kernel.

kernel: ------------[ cut here ]------------
kernel: WARNING: CPU: 11 PID: 10889 at /var/lib/dkms/nvidia/550.67/build/nvidia/nv.c:4522 nv_set_system_power_state+0x2e9/0x460 [nvidia]
kernel: Modules linked in: tls rfcomm ccm nvidia_uvm(POE) snd_ctl_led snd_soc_skl_hda_dsp snd_soc_intel_hda_dsp_common snd_soc_hdac_hdmi snd_sof_probes snd_hda_codec_hdmi snd_hda_codec_re>
kernel:  intel_rapl_msr nls_iso8859_1 dell_smm_hwmon mac80211 snd_pcm libarc4 i915 snd_seq_midi snd_seq_midi_event uvcvideo intel_cstate dell_wmi snd_rawmidi videobuf2_vmalloc btusb btrtl>
kernel:  x_tables autofs4 usbhid hid_sensor_custom hid_sensor_hub intel_ishtp_hid nvme hid_generic nvme_core spi_intel_pci i2c_i801 crc32_pclmul spi_intel i2c_smbus nvme_common ucsi_acpi >
kernel: CPU: 11 PID: 10889 Comm: nvidia-sleep.sh Tainted: P        W  OE      6.5.0-35-generic #35~22.04.1-Ubuntu
kernel: Hardware name: Dell Inc. Inspiron 7590/0JKGD4, BIOS 1.22.0 09/12/2023
kernel: RIP: 0010:nv_set_system_power_state+0x2e9/0x460 [nvidia]
kernel: Code: 48 8b 75 d0 84 c0 0f 84 6e ff ff ff 48 8b 3d 06 99 cd 00 e8 b9 17 14 c9 e9 5d ff ff ff 4c 89 f7 e8 fc 4b e1 c9 e9 50 ff ff ff <0f> 0b e9 34 fe ff ff 48 8b 3d e1 98 cd 00 4c >
kernel: RSP: 0018:ffffae3051ca3d18 EFLAGS: 00010206
kernel: RAX: 0000000000000011 RBX: 0000000000000002 RCX: 0000000000000000
kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
kernel: RBP: ffffae3051ca3d50 R08: 0000000000000000 R09: 0000000000000000
kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff98e9db2f7000
kernel: R13: 0000000000000000 R14: 0000000000000006 R15: 0000000000000007
kernel: FS:  00007e5d6cb82740(0000) GS:ffff98ed2d6c0000(0000) knlGS:0000000000000000
kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
kernel: CR2: 0000641a83b7f008 CR3: 0000000158056002 CR4: 00000000003706e0
kernel: Call Trace:
kernel:  <TASK>
kernel:  ? show_regs+0x6d/0x80
kernel:  ? __warn+0x89/0x160
kernel:  ? nv_set_system_power_state+0x2e9/0x460 [nvidia]
kernel:  ? report_bug+0x17e/0x1b0
kernel:  ? handle_bug+0x46/0x90
kernel:  ? exc_invalid_op+0x18/0x80
kernel:  ? asm_exc_invalid_op+0x1b/0x20
kernel:  ? nv_set_system_power_state+0x2e9/0x460 [nvidia]
kernel:  ? nv_set_system_power_state+0x11c/0x460 [nvidia]
kernel:  ? __check_object_size.part.0+0x3a/0x150
kernel:  nv_procfs_write_suspend+0x106/0x1c0 [nvidia]
kernel:  proc_reg_write+0x69/0xb0
kernel:  vfs_write+0xff/0x440
kernel:  ksys_write+0x73/0x100
kernel:  __x64_sys_write+0x19/0x30
kernel:  x64_sys_call+0x1d63/0x20b0
kernel:  do_syscall_64+0x55/0x90
kernel:  ? exit_to_user_mode_prepare+0x30/0xb0
kernel:  ? syscall_exit_to_user_mode+0x37/0x60
kernel:  ? do_syscall_64+0x61/0x90
kernel:  ? do_syscall_64+0x61/0x90
kernel:  entry_SYSCALL_64_after_hwframe+0x73/0xdd
kernel: RIP: 0033:0x7e5d6c914887
kernel: Code: 10 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 0f 1f 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 48 89 >
kernel: RSP: 002b:00007ffda2ac5528 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
kernel: RAX: ffffffffffffffda RBX: 0000000000000007 RCX: 00007e5d6c914887
kernel: RDX: 0000000000000007 RSI: 0000641a83b7f100 RDI: 0000000000000001
kernel: RBP: 0000641a83b7f100 R08: 0000000000000000 R09: 0000641a83b7f100
kernel: R10: 0000000000000077 R11: 0000000000000246 R12: 0000000000000007
kernel: R13: 00007e5d6ca1b780 R14: 00007e5d6ca17600 R15: 00007e5d6ca16a00
kernel:  </TASK>
kernel: ---[ end trace 0000000000000000 ]---
gdm3[1378]: GLib: Source ID 82 was not found when attempting to remove it
systemd[1]: systemd-hybrid-sleep.service: Deactivated successfully.
systemd[1]: Finished Hybrid Suspend+Hibernate.
systemd[1]: systemd-hybrid-sleep.service: Consumed 2.665s CPU time.
systemd[1]: Reached target Hybrid Suspend+Hibernate.
systemd[1]: Stopped target Sleep.
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:69
systemd[1]: Starting NVIDIA system resume actions...
systemd[1]: Stopped target Hybrid Suspend+Hibernate.
suspend[10913]: nvidia-resume.service
logger[10913]: <13>Jun 13 05:38:46 suspend: nvidia-resume.service
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:72
systemd[1]: nvidia-resume.service: Deactivated successfully.
systemd[1]: Finished NVIDIA system resume actions.
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:67
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:65
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:70
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 13:71
/usr/libexec/gdm-x-session[2348]: (II) systemd-logind: got resume for 226:0
/usr/libexec/gdm-x-session[2348]: (II) AIGLX: Resuming AIGLX clients after VT switch
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): EDID vendor "AUO", prod id 9453
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Printing DDC gathered Modelines:
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (67.1 kHz eP)
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Modeline "1920x1080"x0.0  112.80  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (53.7 kHz e)
systemd-logind[925]: Operation 'sleep' finished.
kernel: rfkill: input handler disabled
ModemManager[977]: <info>  [sleep-monitor-systemd] system is resuming
NetworkManager[894]: <info>  [1718228326.8459] manager: sleep: wake requested (sleeping: yes  enabled: yes)
NetworkManager[894]: <info>  [1718228326.8461] device (wlp61s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): EDID vendor "AUO", prod id 9453
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Printing DDC gathered Modelines:
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Modeline "1920x1080"x0.0  141.00  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (67.1 kHz eP)
/usr/libexec/gdm-x-session[2348]: (II) modeset(0): Modeline "1920x1080"x0.0  112.80  1920 2028 2076 2100  1080 1090 1100 1118 +hsync -vsync (53.7 kHz e)
kernel: iwlwifi 0000:3d:00.0: WRT: Invalid buffer destination
/usr/libexec/gdm-x-session[2348]: (WW) NVIDIA(GPU-0): Failed to enter interactive mode.
/usr/libexec/gdm-x-session[2348]: (EE) NVIDIA(GPU-0): Failed to query object info.
/usr/libexec/gdm-x-session[2348]: (EE) NVIDIA(GPU-0): Failed to query object info.
kernel: workqueue: set_brightness_delayed hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND
/usr/libexec/gdm-x-session[2348]: (EE) NVIDIA(GPU-0): Failed to query object info.

I’ve also tried “suspend” as the parameter of the nvidia-sleep.sh script and enabled “NVreg_PreserveVideoMemoryAllocations” as other solutions suggested, but that gives a similar outcome. I hope someone in Nvidia would help to fix this compatibility issue.

11

Hi amrits,

I exported a bug report through ssh after reproducing the issue. I’ve reverted all the changes I mentioned in the previous comment.

nvidia-bug-report.log (2.5 MB)