NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

besstsoft@gmail.com · 2026-07-17 18:23:44

Hi everyone,

I'm experiencing an issue with suspend on my ASUS VivoBook X510UF running Arch Linux.

Suspend works normally in most situations, but it consistently fails when Haruna is open playing a video (even if the video is paused). If I close the laptop lid while Haruna is still open, the system attempts to suspend but immediately resumes and prints kernel messages on the console.

If I close Haruna first, suspend works perfectly.

The same is true if I'm only using a web browser or editing documents—closing the lid suspends the laptop without any issues.

Laptop: ASUS VivoBook S15 X510UF
CPU: Intel Core i5-8250U
iGPU: Intel UHD Graphics 620
dGPU: NVIDIA GeForce MX130 (Optimus)
RAM: 16 GB
Arch Linux
Kernel: 7.1.3-arch2-1
KDE Plasma 6.7.3
Wayland
NVIDIA Driver: 580.173.02
root=PARTUUID=4a94c7ce-f378-4b0d-9ed9-1e026506aa3b \
zswap.enabled=0 \
rootflags=subvol=@ \
rw rootfstype=btrfs \
quiet splash loglevel=3 \
usbcore.quirks=13d3:5a07:i \
acpi_osi="Windows 2015" \
nvidia_drm.modeset=1 \
nvidia.NVreg_PreserveVideoMemoryAllocations=1
PreserveVideoMemoryAllocations: 1
DynamicPowerManagement: 3
TemporaryFilePath: "/var/tmp"

$ cat /sys/power/mem_sleep
s2idle [deep]

$ systemctl status nvidia-suspend.service
enabled

$ systemctl status nvidia-resume.service
enabled

$ systemctl status nvidia-hibernate.service
enabled

$ glxinfo -B

OpenGL renderer string: Mesa Intel(R) UHD Graphics 620

$ prime-run glxinfo -B

OpenGL renderer string: NVIDIA GeForce MX130/PCIe/SSE2

Error shown on the console

When closing the lid while Haruna is open, I get the following messages:

NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set.

nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend() returns -5

PM: failed to suspend async: error -5

PM: Some devices failed to suspend, or early wake event detected

After that, the system immediately resumes instead of entering suspend.

Questions
Is this a known issue with NVIDIA driver 580.xx?
Could NVreg_PreserveVideoMemoryAllocations=1 be causing this?
Has anyone experienced the same problem with Haruna or other MPV-based players on Optimus laptops?

Any suggestions or things I should test would be appreciated.

Thanks!

seth · 2026-07-17 19:15:23

Does haruna decode on the nvidia GPU?
Do you have the same problem w/ mpv itself?

You'd typically get this if the userspace services for the VRAM preservation are not running or fail - anything interesting about those services (or userspace in general) in the system journal?

besstsoft@gmail.com · 2026-07-17 20:25:28

seth wrote:

Does haruna decode on the nvidia GPU?
Do you have the same problem w/ mpv itself?
You'd typically get this if the userspace services for the VRAM preservation are not running or fail - anything interesting about those services (or userspace in general) in the system journal?

I checked with nvidia-smi while Haruna is playing a video. Haruna does not appear in the process list and only kwin_wayland is using the NVIDIA GPU (2 MiB). The same is true while watching YouTube in my browser. It looks like video playback is not using the NVIDIA GPU directly.

I also discovered that the issue is not specific to Haruna. I can reproduce the same suspend failure while watching YouTube in my browser. If I close the video player/browser before closing the lid, suspend works normally.

seth · 2026-07-17 20:48:23

Ok, so somehow™ playing a video on the IGP makes the nvidia VRAM preservation service fail… wtf?

seth wrote:

anything interesting about those services (or userspace in general) in the system journal?

In doubt post your complete system journal for the boot after such failure

sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

besstsoft@gmail.com · 2026-07-18 11:14:59

seth wrote:

Ok, so somehow™ playing a video on the IGP makes the nvidia VRAM preservation service fail… wtf?
seth wrote:
anything interesting about those services (or userspace in general) in the system journal?
In doubt post your complete system journal for the boot after such failure
sudo journalctl -b | curl -s -H "Accept: application/json, */*" --upload-file - 'https://paste.c-net.org/'

I intentionally triggered the error and captured the boot journal as requested.

Here is the link to the journal:

https://paste.c-net.org/ResetEarning

And here are the specific errors that occurred:

nvidia-sleep.sh[4011]: exited with irqs disabled
nvidia-sleep.sh[4011]: exited with irq/preempt_count 1

PM: suspend entry (deep)

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

nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
nvidia 0000:01:00.0: PM: failed to suspend: error -5

sd 0:0:0:0: [sda] Synchronizing SCSI cache
PM: Some devices failed to suspend, or early wake event detected

OOM killer enabled.
Restarting tasks: Starting
Restarting tasks: Done

efiwarts: resyncing variable state
efiwarts: finished resyncing variable state

random: crng reseeded on system resumption

PM: suspend exit
PM: suspend entry (s2idle)

nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
nvidia 0000:01:00.0: PM: failed to suspend: error -5

NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set.
System Power Management attempted without driver procfs suspend interface.

seth · 2026-07-18 16:10:30

The journal covers only 80s and no sleep attempt, did you reboot after the sleep attempt failed? Why?
You'd have to access the journal of the previous boot (… -b -1) then.

besstsoft@gmail.com · 2026-07-18 18:27:25

seth wrote:

The journal covers only 80s and no sleep attempt, did you reboot after the sleep attempt failed? Why?
You'd have to access the journal of the previous boot (… -b -1) then.

I had to reboot because when this error occurs, the system completely freezes. The screen goes entirely black, the laptop gets very hot, and the cooling fans spin up to 100%. The system becomes completely unresponsive, and the only way to recover or restart is to perform a hard reset by holding down the power button.

I reproduced the crash and pulled the journal from the previous boot using -b -1.

Here is the link to the correct journal:
https://paste.c-net.org/FraizhSnails

https://ibb.co/DPPSTDf9

seth · 2026-07-18 20:44:32

лип 18 21:15:23 AsusX510UF kernel: BUG: kernel NULL pointer dereference, address: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel: fbcon: Taking over console
лип 18 21:15:23 AsusX510UF kernel: #PF: supervisor read access in kernel mode
лип 18 21:15:23 AsusX510UF kernel: #PF: error_code(0x0000) - not-present page
лип 18 21:15:23 AsusX510UF kernel: PGD 0 P4D 0 
лип 18 21:15:23 AsusX510UF kernel: Oops: Oops: 0000 [#1] SMP PTI
лип 18 21:15:23 AsusX510UF kernel: CPU: 3 UID: 0 PID: 85218 Comm: nvidia-sleep.sh Tainted: P           OE       7.1.3-arch2-1 #1 PREEMPT(full)  5a9a9b5536df0b7dd390564d644acc7c1955622a
лип 18 21:15:23 AsusX510UF kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
лип 18 21:15:23 AsusX510UF kernel: Hardware name: ASUSTeK COMPUTER INC. VivoBook S15 X510UF/X510UF, BIOS X510UF.304 09/06/2019
лип 18 21:15:23 AsusX510UF kernel: RIP: 0010:_raw_q_schedule+0x2f/0xb0 [nvidia_uvm]
лип 18 21:15:23 AsusX510UF kernel: Code: 48 83 ec 20 48 89 5c 24 08 48 89 fb 48 83 c7 10 48 89 6c 24 10 48 89 f5 e8 9e 1b 72 f1 48 89 c1 48 3b 6d 00 75 5b 48 8b 73 08 <48> 3b 1e 0f 85 f8 22 0c 00 48 39 f5 0f 84 ef 22 0c 00 48 39 dd 0f
лип 18 21:15:23 AsusX510UF kernel: RSP: 0018:ffffd27152fd79a8 EFLAGS: 00010046
лип 18 21:15:23 AsusX510UF kernel: RAX: 0000000000000286 RBX: ffffd271529ef308 RCX: 0000000000000286
лип 18 21:15:23 AsusX510UF kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffd271529ef318
лип 18 21:15:23 AsusX510UF kernel: RBP: ffffd27152fd79d0 R08: ffffffffc7be4320 R09: 0000000000000001
лип 18 21:15:23 AsusX510UF kernel: R10: 0000000000000010 R11: 0000000000000000 R12: ffffd27152fd79f8
лип 18 21:15:23 AsusX510UF kernel: R13: ffffd27152fd7a08 R14: ffffd271529ef308 R15: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel: FS:  00007f92a72bbb80(0000) GS:ffff8c092aa11000(0000) knlGS:0000000000000000
лип 18 21:15:23 AsusX510UF kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
лип 18 21:15:23 AsusX510UF kernel: CR2: 0000000000000000 CR3: 000000011cd70006 CR4: 00000000003726f0
лип 18 21:15:23 AsusX510UF kernel: Call Trace:
лип 18 21:15:23 AsusX510UF kernel:  <TASK>
лип 18 21:15:23 AsusX510UF kernel:  nv_kthread_q_flush+0x7f/0x130 [nvidia_uvm 2e6718167d7228f900daaea15e3761b965ada3db]
лип 18 21:15:23 AsusX510UF kernel:  ? __pfx__q_flush_function+0x10/0x10 [nvidia_uvm 2e6718167d7228f900daaea15e3761b965ada3db]
лип 18 21:15:23 AsusX510UF kernel:  ? thread_context_current+0x75/0x140 [nvidia_uvm 2e6718167d7228f900daaea15e3761b965ada3db]
лип 18 21:15:23 AsusX510UF kernel:  uvm_suspend.isra.0+0x9f/0x1b0 [nvidia_uvm 2e6718167d7228f900daaea15e3761b965ada3db]
лип 18 21:15:23 AsusX510UF kernel:  uvm_suspend_entry+0xad/0xd0 [nvidia_uvm 2e6718167d7228f900daaea15e3761b965ada3db]
лип 18 21:15:23 AsusX510UF kernel:  nv_uvm_suspend+0x2f/0x60 [nvidia 5fe9e5435466696c79f68b931fb60c398ef60c11]
лип 18 21:15:23 AsusX510UF kernel:  nv_set_system_power_state+0x3fe/0x4d0 [nvidia 5fe9e5435466696c79f68b931fb60c398ef60c11]
лип 18 21:15:23 AsusX510UF kernel:  nv_procfs_write_suspend+0x102/0x1a0 [nvidia 5fe9e5435466696c79f68b931fb60c398ef60c11]
лип 18 21:15:23 AsusX510UF kernel:  proc_reg_write+0x5a/0xb0
лип 18 21:15:23 AsusX510UF kernel:  vfs_write+0xe6/0x570
лип 18 21:15:23 AsusX510UF kernel:  ? get_page_from_freelist+0x18c0/0x1c20
лип 18 21:15:23 AsusX510UF kernel:  ksys_write+0x7b/0x110
лип 18 21:15:23 AsusX510UF kernel:  do_syscall_64+0xaa/0x660
лип 18 21:15:23 AsusX510UF kernel:  ? __alloc_frozen_pages_noprof+0x1a0/0x380
лип 18 21:15:23 AsusX510UF kernel:  ? __mod_memcg_lruvec_state+0xeb/0x1b0
лип 18 21:15:23 AsusX510UF kernel:  ? lruvec_stat_mod_folio+0x93/0xd0
лип 18 21:15:23 AsusX510UF kernel:  ? __folio_mod_stat+0x2d/0x90
лип 18 21:15:23 AsusX510UF kernel:  ? map_anon_folio_pte_nopf+0xc7/0x160
лип 18 21:15:23 AsusX510UF kernel:  ? do_anonymous_page+0x10b/0x890
лип 18 21:15:23 AsusX510UF kernel:  ? __pte_offset_map+0x1b/0x100
лип 18 21:15:23 AsusX510UF kernel:  ? __handle_mm_fault+0xb72/0xf80
лип 18 21:15:23 AsusX510UF kernel:  ? __x64_sys_close+0x47/0xa0
лип 18 21:15:23 AsusX510UF kernel:  ? count_memcg_events+0xd1/0x190
лип 18 21:15:23 AsusX510UF kernel:  ? handle_mm_fault+0x1e5/0x2c0
лип 18 21:15:23 AsusX510UF kernel:  ? do_user_addr_fault+0x23b/0x730
лип 18 21:15:23 AsusX510UF kernel:  ? do_syscall_64+0x5f/0x660
лип 18 21:15:23 AsusX510UF kernel:  ? exc_page_fault+0x90/0x1f0
лип 18 21:15:23 AsusX510UF kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
лип 18 21:15:23 AsusX510UF kernel: RIP: 0033:0x7f92a709405e
лип 18 21:15:23 AsusX510UF kernel: Code: 4d 89 d8 e8 84 bf 00 00 4c 8b 5d f8 41 8b 93 08 03 00 00 59 5e 48 83 f8 fc 74 11 c9 c3 0f 1f 80 00 00 00 00 48 8b 45 10 0f 05 <c9> c3 83 e2 39 83 fa 08 75 e7 e8 03 ff ff ff 0f 1f 00 f3 0f 1e fa
лип 18 21:15:23 AsusX510UF kernel: RSP: 002b:00007ffc270c7ca0 EFLAGS: 00000202 ORIG_RAX: 0000000000000001
лип 18 21:15:23 AsusX510UF kernel: RAX: ffffffffffffffda RBX: 00007f92a7213580 RCX: 00007f92a709405e
лип 18 21:15:23 AsusX510UF kernel: RDX: 0000000000000008 RSI: 00005604ec488f80 RDI: 0000000000000001
лип 18 21:15:23 AsusX510UF kernel: RBP: 00007ffc270c7cb0 R08: 0000000000000000 R09: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel: R10: 0000000000000000 R11: 0000000000000202 R12: 0000000000000008
лип 18 21:15:23 AsusX510UF kernel: R13: 0000000000000008 R14: 00005604ec488f80 R15: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel:  </TASK>
лип 18 21:15:23 AsusX510UF kernel: Modules linked in: tun rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ccm algif_aead des_generic libdes algif_skcipher md4 algif_hash af_alg bnep snd_hda_codec_intelhdmi intel_rapl_msr snd_hda_codec_hdmi vfat intel_uncore_frequency fat intel_uncore_frequency_common snd_hda_codec_generic iwlmvm intel_tcc_cooling snd_hda_intel x86_pkg_temp_thermal snd_soc_avs intel_powerclamp coretemp snd_soc_hda_codec mac80211 snd_hda_ext_core snd_hda_codec snd_hda_core kvm_intel ptp snd_intel_dspcfg pps_core snd_intel_sdw_acpi snd_hwdep libarc4 btusb uvcvideo kvm snd_soc_core btmtk iwlwifi videobuf2_vmalloc btrtl snd_compress uvc iTCO_wdt btbcm ac97_bus videobuf2_memops irqbypass ee1004 snd_pcm_dmaengine intel_pmc_bxt btintel videobuf2_v4l2 aesni_intel asus_nb_wmi mei_hdcp mei_pxp asus_armoury hid_multitouch snd_pcm
лип 18 21:15:23 AsusX510UF kernel:  i2c_i801 videobuf2_common processor_thermal_device_pci_legacy gf128mul cfg80211 bluetooth firmware_attributes_class aead processor_thermal_device snd_timer videodev i2c_smbus rapl mei_me processor_thermal_wt_hint asus_wmi snd intel_cstate soundcore intel_uncore mc pcspkr sparse_keymap mxm_wmi wmi_bmof i2c_mux 8250_dw rfkill platform_temperature_control i2c_hid_acpi processor_thermal_soc_slider mei intel_pch_thermal processor_thermal_rfim i2c_hid intel_pmc_core processor_thermal_rapl intel_rapl_common pmt_telemetry intel_oc_wdt processor_thermal_wt_req int3403_thermal processor_thermal_power_floor pmt_discovery processor_thermal_mbox pmt_class joydev int3400_thermal int340x_thermal_zone intel_xhci_usb_role_switch intel_pmc_ssram_telemetry intel_soc_dts_iosf asus_wireless intel_vsec roles acpi_thermal_rel acpi_pad mousedev mac_hid ntsync pkcs8_key_parser i2c_dev crypto_user zram 842_decompress 842_compress lz4hc_compress lz4_compress nvidia_drm(POE) nvidia_uvm(POE) nvidia_modeset(POE) hid_logitech_hidpp
лип 18 21:15:23 AsusX510UF kernel:  spi_pxa2xx_platform dw_dmac spi_pxa2xx_core intel_lpss_pci intel_lpss nvidia(POE) idma64 hid_logitech_dj serio_raw i915 drm_buddy i2c_algo_bit intel_gtt drm_display_helper drm_ttm_helper video ttm cec wmi
лип 18 21:15:23 AsusX510UF kernel: CR2: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel: ---[ end trace 0000000000000000 ]---
лип 18 21:15:23 AsusX510UF kernel: RIP: 0010:_raw_q_schedule+0x2f/0xb0 [nvidia_uvm]
лип 18 21:15:23 AsusX510UF kernel: Code: 48 83 ec 20 48 89 5c 24 08 48 89 fb 48 83 c7 10 48 89 6c 24 10 48 89 f5 e8 9e 1b 72 f1 48 89 c1 48 3b 6d 00 75 5b 48 8b 73 08 <48> 3b 1e 0f 85 f8 22 0c 00 48 39 f5 0f 84 ef 22 0c 00 48 39 dd 0f
лип 18 21:15:23 AsusX510UF kernel: RSP: 0018:ffffd27152fd79a8 EFLAGS: 00010046
лип 18 21:15:23 AsusX510UF kernel: RAX: 0000000000000286 RBX: ffffd271529ef308 RCX: 0000000000000286
лип 18 21:15:23 AsusX510UF kernel: RDX: 0000000000000001 RSI: 0000000000000000 RDI: ffffd271529ef318
лип 18 21:15:23 AsusX510UF kernel: RBP: ffffd27152fd79d0 R08: ffffffffc7be4320 R09: 0000000000000001
лип 18 21:15:23 AsusX510UF kernel: R10: 0000000000000010 R11: 0000000000000000 R12: ffffd27152fd79f8
лип 18 21:15:23 AsusX510UF kernel: R13: ffffd27152fd7a08 R14: ffffd271529ef308 R15: 0000000000000000
лип 18 21:15:23 AsusX510UF kernel: FS:  00007f92a72bbb80(0000) GS:ffff8c092aa11000(0000) knlGS:0000000000000000
лип 18 21:15:23 AsusX510UF kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
лип 18 21:15:23 AsusX510UF kernel: CR2: 0000000000000000 CR3: 000000011cd70006 CR4: 00000000003726f0
лип 18 21:15:23 AsusX510UF kernel: note: nvidia-sleep.sh[85218] exited with irqs disabled
лип 18 21:15:23 AsusX510UF kernel: note: nvidia-sleep.sh[85218] exited with preempt_count 1

LIBVA_DRIVER_NAME=iHD mpv --hwdec=vaapi someporn.mp4

https://wiki.archlinux.org/title/Hardwa … ing_VA-API

The VRAM userspace sleep process triggers a nullptr in nvidia_uvm (cuda/nvdec related, so the video thing makes sense) and that prevents the GPU from entering the the sleep.
From what I can tell what's then causing some trouble is the webcam, at least it flares up on the fast-ish re-connect.

The question is whether we can get VAAPI completely away from nvdec and whether that protects the UVM module.
Brute-force solution would be to blacklist that, but it would break anything CUDA related.

besstsoft@gmail.com · Yesterday 07:16:36

I set LIBVA_DRIVER_NAME=iHD as discussed and rebooted. The system still fails to suspend, but the behavior has changed. Instead of a total black screen lockup with 100% fan speed, the suspend process now aborts, and I get a kernel output on the screen with two distinct issues.

1. NVIDIA power management failure:
The suspend is aborted by the NVIDIA driver returning a -5 error. It complains about the power management interface:

NVRM: GPU 0000:01:00.0: PreserveVideoMemoryAllocations module parameter is set. System Power Management attempted without driver procfs suspend interface. Please refer to the 'Configuring Power Management' section in the driver README.
nvidia 0000:01:00.0: PM: pci_pm_suspend(): nv_pmops_suspend [nvidia] returns -5
nvidia 0000:01:00.0: PM: dpm_run_callback(): pci_pm_suspend returns -5
PM: Some devices failed to suspend, or early wake event detected

Immediately after this failure, the USB webcam (13d3:5a07) goes into an infinite loop of disconnecting and reconnecting.

2. A FUSE process blocking the freeze:
On another attempt, the user space processes refused to freeze entirely due to what looks like a hanging FUSE filesystem:

Freezing user space processes failed after 20.004 seconds (1 tasks refusing to freeze, wq_busy=0):
Call Trace:
<TASK>
...
fuse_simple_request
fuse_lookup_name
...
vfs_statx

Regarding the NVIDIA error, should I enable the nvidia-suspend.service (and related hibernate/resume services) to fix the NVRM procfs issue, or is this still a symptom of the UVM module conflict?

Also, regarding the webcam errors: the camera has a hardware issue with its ribbon cable. I previously disabled it on the system level (though I honestly don't remember the exact method or commands I used to do it). That probably explains why it falls into an infinite disconnect/reconnect loop when the system crashes.

https://ibb.co/RGGpv0dN
https://ibb.co/gL9Y8vYL

seth · Yesterday 11:28:28

Do you have the journal from that boot?
The nvidia-suspend.service was enabled, but failed (apparently because of the nvidia_uvm crash) - no idea why the kioworker freaks out (you'd also want to check what fuse mounts you actually hold) but it looks like it's a result of the hiccup-wakeup as well.

Can you disable the webcam in the BIOS/UEFI settings?

Next step would be to flat out blacklist nvidia_uvm to at least see whether it's the origin of the troubles or just another symptom.
Why mpv (what about vlc?) would dog around on the nvidia GPU when VAPPI is explicitly directed towards iHD is kinda beyond me

Arch Linux

#1 2026-07-17 18:23:44

NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#2 2026-07-17 19:15:23

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#3 2026-07-17 20:25:28

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#4 2026-07-17 20:48:23

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#5 2026-07-18 11:14:59

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#6 2026-07-18 16:10:30

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#7 2026-07-18 18:27:25

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#8 2026-07-18 20:44:32

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#9 Yesterday 07:16:36

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

#10 Yesterday 11:28:28

Re: NVIDIA suspend fails with nv_pmops_suspend() returns -5 when Haruna is

Board footer