575 release feedback & discussion

[dmakc]

Just tried new beta under Debian 12 with kernel 6.12.12+bpo-amd64 and I can’t successfully logon to KDE Plasma X11 when using proprietary NVidia kernel module with options nvidia NVreg_EnableGpuFirmware=1. I’m getting black screen on secondary (external) monitor, directly connected to my dGPU (NVIDIA GeForce RTX 3050 Ti Laptop GPU) on my laptop Acer Nitro AN515-58:

At the same time laptop’s iGPU monitor (eDP-1 output) works perfectly. There is no errors in dmesg or Xorg logs.

If I set options nvidia NVreg_EnableGpuFirmware=0 and reboot I can successfully log in and Plasma X11 works.

NVidia open kernel modules do not work the same as proprietary ones with options nvidia NVreg_EnableGpuFirmware=1: I’m getting black screen on my external monitor in Plasma X11, no image at all.

nvidia-bug-report.log.gz (2.1 MB)

PS: Plasma Wayland works in both of above cases, but it’s so slow, that make it totally unusable.

[ptr1337]

Did you install the open-dkms package? Can you try to use a LTS Kernel?

You can also gain logs from the previous boot with:
journalctl -b -1 | paste-cachyos

[v19930312]

@ptr1337

Did you install the open-dkms package?

Yes - to be more exact, I’ve installed (well, updated to) all packages from that link except for non-open dkms one.

@ptr1337

Can you try to use a LTS Kernel?

The exact same problem happens.

@ptr1337

You can also gain logs from the previous boot with:
journalctl -b -1 | paste-cachyos

That’s how I originally got that snippet :) But sure, here are the full logs for regular and LTS (with LTO) kernels.

[ptr1337]

Thanks! Appears to be a null ptr:

Apr 18 11:17:41 kernel: BUG: kernel NULL pointer dereference, address: 000000000000002c
Apr 18 11:17:41 kernel: #PF: supervisor write access in kernel mode
Apr 18 11:17:41 kernel: #PF: error_code(0x0002) - not-present page
Apr 18 11:17:41 kernel: PGD 131f21067 P4D 131f21067 PUD 131f26067 PMD 0 
Apr 18 11:17:41 kernel: Oops: Oops: 0002 [#1] PREEMPT SMP NOPTI
Apr 18 11:17:41 kernel: CPU: 12 UID: 0 PID: 627 Comm: nvidia-powerd Tainted: G           OE      6.14.2-2-cachyos #1 a696f967e54068959683a60c6843f390e83efcd1
Apr 18 11:17:41 kernel: Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Apr 18 11:17:41 kernel: Hardware name: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507NV_FA507NV/FA507NV, BIOS FA507NV.316 11/04/2024
Apr 18 11:17:41 kernel: RIP: 0010:serverResLock_Epilogue+0x3b/0x50 [nvidia]
Apr 18 11:17:41 kernel: Code: 8b 01 a8 08 74 17 41 8b 7e 30 31 f6 e8 ee c6 e5 ff 41 80 66 2c fb 8b 03 83 e0 f7 89 03 a8 04 74 11 31 ff 31 f6 e8 05 c6 e5 ff <41> 80 66 2c fd 80 23 fb 5b 41 5e 5d c3 cc cc cc cc cc cc cc cc 66
Apr 18 11:17:41 kernel: RSP: 0018:ffffb5e44210f768 EFLAGS: 00010286
Apr 18 11:17:41 kernel: RAX: 0000000000000000 RBX: ffffb5e44210f7c8 RCX: ffffb5e44210f9e0
Apr 18 11:17:41 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff9e48785a7790
Apr 18 11:17:41 kernel: RBP: ffffb5e44210f778 R08: 0000000000000000 R09: 0000000000000001
Apr 18 11:17:41 kernel: R10: 0000000000000273 R11: 0000000000000000 R12: ffff9e48516c9018
Apr 18 11:17:41 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffc0ab7200
Apr 18 11:17:41 kernel: FS:  00007fbb619ad500(0000) GS:ffff9e4b8ea00000(0000) knlGS:0000000000000000
Apr 18 11:17:41 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 18 11:17:41 kernel: CR2: 000000000000002c CR3: 000000012cdd4000 CR4: 0000000000f50ef0
Apr 18 11:17:41 kernel: PKRU: 55555554
Apr 18 11:17:41 kernel: Call Trace:
Apr 18 11:17:41 kernel:  <TASK>
Apr 18 11:17:41 kernel:  serverControl_Epilogue+0x25/0x60 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  resControl_IMPL+0x1ad/0x1c0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  serverControl+0x294/0x490 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  rmapiControlWithSecInfo+0x5a4/0x7b0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  rmapiControlWithSecInfoTls+0x6f/0xc0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  Nv04ControlWithSecInfo+0x97/0xb0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  ? os_acquire_spinlock+0x12/0x30 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  ? portSyncSpinlockAcquire+0x15/0x20 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  ? threadStateFree+0x145/0x2e0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? rm_ioctl+0x2e5/0x470 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  RmIoctl+0x6ae/0xa60 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? os_get_current_tick+0x46/0xa0 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  rm_ioctl+0x2d4/0x470 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel:  nvidia_unlocked_ioctl+0x653/0x750 [nvidia 9e8d463dc491461427adc735efc78fc0a76b7955]
Apr 18 11:17:41 kernel: amdgpu 0000:36:00.0: amdgpu: SMU is initialized successfully!
Apr 18 11:17:41 kernel: [drm] Seamless boot condition check passed
Apr 18 11:17:41 kernel:  __x64_sys_ioctl+0x12c/0x1d0
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  do_syscall_64+0x85/0x11e
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  ? srso_alias_return_thunk+0x5/0xfbef5
Apr 18 11:17:41 kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Apr 18 11:17:41 kernel: RIP: 0033:0x7fbb6171cc1f
Apr 18 11:17:41 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00
Apr 18 11:17:41 kernel: RSP: 002b:00007ffc14bb24d0 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Apr 18 11:17:41 kernel: RAX: ffffffffffffffda RBX: 0000000000000020 RCX: 00007fbb6171cc1f
Apr 18 11:17:41 kernel: RDX: 00007ffc14bb2630 RSI: 00000000c020462a RDI: 0000000000000005
Apr 18 11:17:41 kernel: RBP: 00007ffc14bb2630 R08: 00007ffc14bb2630 R09: 00007ffc14bb264c
Apr 18 11:17:41 kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000005
Apr 18 11:17:41 kernel: R13: 00000000c020462a R14: 000000000000002a R15: 00007ffc14bb264c
Apr 18 11:17:41 kernel:  </TASK>
Apr 18 11:17:41 kernel: Modules linked in: snd_hda_codec_realtek(+) snd_hda_scodec_component vfat snd_hda_codec_generic snd_hda_codec_hdmi fat snd_acp6x_pdm_dma snd_soc_dmic snd_soc_acp6x_mach snd_sof_amd_acp70 snd_sof_amd_acp63 snd_sof_amd_vangogh amdgpu(+) snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_pci_ps rtw89_8852be snd_soc_acpi_amd_match rtw89_8852b soundwire_amd soundwire_generic_allocation rtw89_8852b_common snd_amd_sdw_acpi rtw89_pci soundwire_bus intel_rapl_msr amd_atl asus_nb_wmi intel_rapl_common snd_soc_sdca rtw89_core snd_soc_core uvcvideo snd_hda_intel drm_panel_backlight_quirks ac97_bus uvc drm_buddy snd_intel_dspcfg videobuf2_vmalloc snd_pcm_dmaengine videobuf2_memops nvidia_drm(OE) asus_armoury snd_intel_sdw_acpi videobuf2_v4l2 snd_compress gpu_sched mac80211 btusb snd_rpl_pci_acp6x nvidia_modeset(OE) amdxcp videobuf2_common snd_hda_codec btbcm snd_acp_pci firmware_attributes_class drm_suballoc_helper drm_exec snd_hda_core kvm_amd
Apr 18 11:17:41 kernel:  snd_acp_legacy_common btintel asus_wmi i2c_algo_bit videodev snd_hwdep btrtl drm_ttm_helper snd_pci_acp6x libarc4 platform_profile btmtk snd_pcm drm_display_helper ucsi_acpi wmi_bmof nvidia_wmi_ec_backlight spd5118 sparse_keymap r8169 mc snd_pci_acp5x ttm snd_timer cec typec_ucsi kvm cfg80211 realtek bluetooth snd_rn_pci_acp3x joydev mdio_devres video snd_acp_config snd typec snd_soc_acpi thunderbolt mousedev i2c_piix4 ccp libphy soundcore wmi pcspkr roles snd_pci_acp3x rfkill amd_pmc rapl k10temp mac_hid pkcs8_key_parser i2c_smbus nvidia_uvm(OE) nvidia(OE) ntsync i2c_dev crypto_user loop dm_mod nfnetlink lz4 zram 842_decompress 842_compress lz4hc_compress lz4_compress ip_tables x_tables nvme atkbd serio_raw libps2 vivaldi_fmap aesni_intel nvme_core hid_multitouch crypto_simd ghash_clmulni_intel i8042 hid_generic polyval_clmulni sha512_ssse3 polyval_generic cryptd sha256_ssse3 sha1_ssse3 nvme_auth serio i2c_hid_acpi i2c_hid
Apr 18 11:17:41 kernel: CR2: 000000000000002c
Apr 18 11:17:41 kernel: ---[ end trace 0000000000000000 ]---
Apr 18 11:17:41 kernel: RIP: 0010:serverResLock_Epilogue+0x3b/0x50 [nvidia]
Apr 18 11:17:41 kernel: Code: 8b 01 a8 08 74 17 41 8b 7e 30 31 f6 e8 ee c6 e5 ff 41 80 66 2c fb 8b 03 83 e0 f7 89 03 a8 04 74 11 31 ff 31 f6 e8 05 c6 e5 ff <41> 80 66 2c fd 80 23 fb 5b 41 5e 5d c3 cc cc cc cc cc cc cc cc 66
Apr 18 11:17:41 kernel: RSP: 0018:ffffb5e44210f768 EFLAGS: 00010286
Apr 18 11:17:41 kernel: RAX: 0000000000000000 RBX: ffffb5e44210f7c8 RCX: ffffb5e44210f9e0
Apr 18 11:17:41 kernel: RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff9e48785a7790
Apr 18 11:17:41 kernel: RBP: ffffb5e44210f778 R08: 0000000000000000 R09: 0000000000000001
Apr 18 11:17:41 kernel: R10: 0000000000000273 R11: 0000000000000000 R12: ffff9e48516c9018
Apr 18 11:17:41 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: ffffffffc0ab7200
Apr 18 11:17:41 kernel: FS:  00007fbb619ad500(0000) GS:ffff9e4b8ea00000(0000) knlGS:0000000000000000
Apr 18 11:17:41 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 18 11:17:41 kernel: CR2: 000000000000002c CR3: 000000012cdd4000 CR4: 0000000000f50ef0
Apr 18 11:17:41 kernel: PKRU: 55555554
Apr 18 11:17:41 kernel: note: nvidia-powerd[627] exited with irqs disabled

Last thing you could try is:

1. Disabling sched-ext
2. Switching to official archlinux kernel: sudo pacman -S linux linux-headers

But I guess its a nvidia issue and needs to be fixed on their side.

[evorster]

I am still having this issue:

[Bug] External monitor fails to wake up from powersave mode if refresh rate is higher than 30Hz

I have an external monitor connected to my Advanced Optimus laptop. The cable connecting the monitor and laptop is confirmed to be HDMI 2.1 The dGPU on the laptop is an nVidia 4090 laptop edition. When this monitor is configured for an update rate of 30Hz, it wakes up normally from powersave. When higher display update rates are selected, it looks like the monitor is waking up, but it claims that there is no signal present and goes back to sleep. A second or so later, the monitor looks like …

This is with the kernel version 6.14.2, and nVidia drivers 575.51.02
HDR on or off does not seem to make a difference.
With nvidia drivers 550 series, I did not have this issue after a firmware update on my monitor, but the issue persists with the latest beta drivers.

[ptr1337]

@v19930312

(AMD Radeon 680M + NVIDIA GeForce RTX 4060 Laptop GPU

Does switching to the closed source module (use the nvidia-dkms in the archive) fixes it maybe?

[v19930312]

Somewhat surprisingly closed source version does boot and run without issues! So the problem seems to be in the open source-specific part of the kernel module.

EDIT: also can confirm that games that used to hang with PROTON_ENABLE_WAYLAND=1 are now running perfectly fine! Now only if mouse input worked properly for all of them, but this one’s not on Nvidia.

[pfirsicheisen]

It seems, that version 575.51.02 fixed my issue:

Kernel Oops with 570.124.04 and 570.86.16

Version 565.77 with kernel 6.12.10 was the last one working for me. HP EliteBook 8770w, Geforce GTX980M. Starting with 570.86.16 and actually 570.124.04 with kernel 6.13.x, login screen (GDM) appears as expected, but after login screens (one notebook internal + one external) go dark and system is unusable. Switching to console doesn’t work. System is only accessible via ssh and systemd journal shows a kernel Oops: Feb 28 20:46:45 elitebook kernel: BUG: kernel NULL pointer dereference, address…

[xeeynamo]

I consistently get NVRM: Xid (PCI:0000:01:00): 109, pid=4683, name=GameThread, Ch 00000016, errorString CTX SWITCH TIMEOUT, Info 0x2ec026 with this new driver when running Black Myth Wukong Benchmark Tool on my 5080. I never had this issue with the 570 drivers.

[thesword53]

Power management with multiple monitors is still not fixed: GPU is stuck to maximun power state at idle when using multiple monitors

[opisalwaysgreat]

This driver is still buggy for me when I toggle hybrid mode in optimus-manager, and only use the external HDMI output of my laptop (Vulkan not working, screen freezing etc.)
nvidia-bug-report.log.gz (1.3 MB)

[evorster]

Just to be sure, I tried both the open and proprietary kernel modules of 575.

[ptr1337]

Please also attach the sudo nvidia-bug-report.sh output - otherwise there can be not helped.

[evorster]

The output of nvidia-bug-report.sh is in the bug report [Bug] External monitor fails to wake up from powersave mode if refresh rate is higher than 30Hz - #22 by evorster

[ethanh20009]

Still getting the stutters shown by this issue:

NVAPI causing huge constant stuttering regression

vkWaitSemaphores seems to cause a lot of stuttering with games with frame gen.

[zebcom]

Is it a Samsung screen?
I have a very weird thing with my Samsung 4K TV I use as monitor. After it goes to power saving (e.g. after 1 hour with screen off) I can only wake it up by going to a TTY as off, then switching on (and switching back to GUI). If I switch it on while in saving mode, it does not wake up even trying to switch to TTY while on.

[BlueGoliath]

Looks like this driver added a bug with display outputs where you need to unplug and plug back in HDMI/DP to get it to show anything. Really nice QA.

[luisalvaradox]

Thisss. Thank you.

[evorster]

Hi there!
I think while the issue might be related, it is a different issue. The monitor is a BenQ. I manged to solve a lot of the issues with this monitor by updating the firmware. Now, with older drivers and on Windows, I have no issues with the monitor. Past 550 though, the system does not wake up the monitor properly when the refresh rate is higher than 30Hz

[zebcom]

Yes, I also thought it may be a different issue. There are a lot of reports with Samsung screens that have this problem, and it could be on Samsung side too (they have sometimes bugs in implementing standards).