555 release feedback & discussion

i found out that 550.90 is stable and i installed it using nvidia-all, nvidia-all is broken i tried to even install 555 with it, encoders doesnt work, well 550.90 seems to have broken watts in most games, like what the hell this is 75w gpu why it it only using 33wats with 100% gpu usage, vram usage was less in 550.90 tho, i think 550.90 have working vram management and broken power management, 535 525 555 have working power management and i cant really test 535 and 525 since vkd3d requires atlest 550

what distro am i using? cachy os

Is there a fix for this yet?

XWAYLAND: wp_linux_drm_syncobj_surface_v1#65: error 3: explicit sync is used, but no buffer is attached

You can use the beta version until the issue is fixed. Or disable wayland support.

GTX 980 Ti - Arch Linux x86_64 - Linux 6.9.7-arch1-1 - 555.58.02

As stated by other people, I have frequent crashes (less than 1 minute after opening a project) with Unreal Engine and Blender with 555.58.02 drivers. Rollbacked to 550.90.07 which have some graphical glitches with Wayland, but at least no crash when working with Unreal

1 Like

With nvidia proprietary linux driver 555, nvidia.NVreg_EnableGpuFirmware=0 kernel option, Wayland and KDE Plasma 6.1 I have low CPU usage (around 5-20% for one core activity for kwin_wayland) and hight frame rate (around 70-75 fps with monitor refresh rate 75 Hz) on external monitor connected to nvidia HDMI port but I have kernels panics as in case Series 550 freezes laptop - #176 by tm4ig

With nvidia open linux driver 555, Wayland and KDE Plasma 6.1 I have hight CPU usage (around 20-80% for one core with activity for kwin_wayland) and low frame rate (around 65-70 fps with monitor refresh rate 75 Hz) on external monitor connected to nvidia HDMI port but I have not kernels panics as in case Series 550 freezes laptop - #176 by tm4ig

With nvidia proprietary linux driver 555, nvidia.NVreg_EnableGpuFirmware=1 kernel option, Wayland and KDE Plasma 6.1 I have hight CPU usage (around 20-80% for one core with activity for kwin_wayland) and low frame rate (around 65-70 fps with monitor refresh rate 75 Hz) on external monitor connected to nvidia HDMI port and I have kernels panics as in case Series 550 freezes laptop - #176 by tm4ig

So on nvidia proprietary driver (full closed mode) I have best performance, but I also have kernel panics
On nvidia open driver I have low performance, but have not kernel panics
On nvidia proprietary driver with Gpu Firmware enabled (default for 555) I have low performance and I have kernels panics.

Nvidia can not fix kernel panics with hybrid graphics five months

I’ve identified a regression in the “stable” 555 drivers that were pushed to Arch stable that removes functionality present within the latest 550 branch that, for almost a month, lead me to believe my system was completely broken.

My GPU (RTX 3070 non-super) can no longer drive my high refresh rate primary monitor over HDMI higher than 120 Hz on the 555 branch. This functionality is restored if I roll back to the 550 branch, and I can drive my monitor to the full 165Hz I need it to be.

Please let me know what logs and config files I need to provide in order to diagnose and remedy this issue.

Made an account just to report that the 555.X.X drivers on Archlinux (as far as I’m aware) has a major regression when using the Unreal Engine 5 editor, it crashes constantly, sometimes instantly sometimes within a few minutes of using it, doesn’t seem to matter which version 5.4.2 or 5.4.1, it crashes with the same error, the UE5 editor has crashed on older drivers but not as often only occasionally, downgrading back to 550.X.X seems to have “fixed” this issue and it hasn’t crashed as often or as quickly.

Here’s the log from the UE5 editor.

LoginId:d531a1789ece4256887e8466a17d08d6-000003e8

Caught signal 11 Segmentation fault

libnvidia-glcore.so.555.58.02!UnknownFunction(0xa08b47)
libnvidia-glcore.so.555.58.02!UnknownFunction(0xde7a38)
libnvidia-glcore.so.555.58.02!UnknownFunction(0xdff14f)
libnvidia-glcore.so.555.58.02!UnknownFunction(0xd3b7ad)
libUnrealEditor-VulkanRHI.so!VulkanRHI::FFenceManager::WaitForFence(VulkanRHI::FFence*, unsigned long long) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanMemory.cpp:4690]
libUnrealEditor-VulkanRHI.so!FVulkanCommandBufferManager::WaitForCmdBuffer(FVulkanCmdBuffer*, float) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanCommandBuffer.cpp:502]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::WaitForFrameEventCompletion() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:278]
libUnrealEditor-VulkanRHI.so!FVulkanViewport::Present(FVulkanCommandListContext*, FVulkanCmdBuffer*, FVulkanQueue*, FVulkanQueue*, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanViewport.cpp:1048]
libUnrealEditor-VulkanRHI.so!FVulkanCommandListContext::RHIEndDrawingViewport(FRHIViewport*, bool, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/VulkanRHI/Private/VulkanRHI.cpp:1184]
libUnrealEditor-RHI.so!FRHICommand<FRHICommandEndDrawingViewport, FRHICommandEndDrawingViewportString2188>::ExecuteAndDestruct(FRHICommandListBase&, FRHICommandListDebugContext&) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/RHI/Public/RHICommandList.h:1295]
libUnrealEditor-RHI.so!FRHICommandListBase::Execute(TRHIPipelineArray<IRHIComputeContext*>&, FRHICommandListBase::FPersistentState::FGPUStats*) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RHI/Private/RHICommandList.cpp:477]
libUnrealEditor-RHI.so!UE::Core::Private::Function::TFunctionRefCaller<FRHICommandListImmediate::ExecuteAndReset(bool)::$_0, void ()>::Call(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Templates/Function.h:405]
libUnrealEditor-Core.so!TGraphTask<TFunctionGraphTaskImpl<void (), (ESubsequentsMode::Type)0> >::ExecuteTask(TArray<FBaseGraphTask*, TSizedDefaultAllocator<32> >&, ENamedThreads::Type, bool) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Public/Async/TaskGraphInterfaces.h:1235]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksNamedThread(int, bool) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:760]
libUnrealEditor-Core.so!FNamedTaskThread::ProcessTasksUntilQuit(int) [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/Async/TaskGraph.cpp:650]
libUnrealEditor-RenderCore.so!FRHIThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/RenderCore/Private/RenderingThread.cpp:330]
libUnrealEditor-Core.so!FRunnableThreadPThread::Run() [/mnt/horde/++UE5/Sync/Engine/Source/./Runtime/Core/Private/HAL/PThreadRunnableThread.cpp:25]
libUnrealEditor-Core.so!FRunnableThreadPThread::_ThreadProc(void*) [/mnt/horde/++UE5/Sync/Engine/Source/Runtime/Core/Private/HAL/PThreadRunnableThread.h:187]
libc.so.6!UnknownFunction(0x92dec)
libc.so.6!UnknownFunction(0x1160db)
1 Like

I have an issue on KDE Fedora 40 where my system will completely freeze after enabling HDR. It happens with the stable 550 drivers as well as the latest beta 555.58.02. The issue is as described here: 488941 – Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled

It looks like the issue was determined to be a driver issue rather than a KDE issue, so I’m posting here for some visibility.

If there’s any additional logs I can post to help, just point me to what’s needed.

Personally I’m experiencing “no signal” to my monitor when I update nvidia-utils nvidia (i tried nvidia-dkms as well) lib32-nvidia-utils, and the other ones. new kernel worked fine.
plymouth boot animation shows to, but after it starts up where the gnome login screen poof no signal. I’m using HDMI to connect.

i downgraded to nvidia 550 and suddenly, it works again. it’s very weird. i haven’t found any working solution yet.

the most notable of my xorg logs is this:
[ 58.727] (==) NVIDIA(0): **
[ 58.727] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
[ 58.727] (==) NVIDIA(0): will be used as the requested mode.
[ 58.727] (==) NVIDIA(0): **
[ 58.728] (II) NVIDIA(0): Validated MetaModes:
[ 58.728] (II) NVIDIA(0): “DFP-4:nvidia-auto-select”
[ 58.728] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 58.768] (–) NVIDIA(0): DPI set to (69, 70); computed from “UseEdidDpi” X config
[ 58.768] (–) NVIDIA(0): option
[ 58.768] () NVIDIA(G0): Depth 24, (–) framebuffer bpp 32

[ 58.768] (==) NVIDIA(G0): RGB weight 888
[ 58.768] (==) NVIDIA(G0): Default visual is TrueColor
[ 58.768] (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0)
[ 58.768] (II) Applying OutputClass “nvidia” options to /dev/dri/card2
[ 58.768] () NVIDIA(G0): Option “AllowEmptyInitialConfiguration”

[ 58.768] () NVIDIA(G0): Option “Coolbits” “8”**
[ 58.768] () NVIDIA(G0): Enabling 2D acceleration**
[ 58.768] (II) NVIDIA: The X server supports PRIME Render Offload.
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (EE) NVIDIA(G0): Failing initialization of X screen
[ 58.768] (II) UnloadModule: “nvidia”
[ 58.768] (II) UnloadSubModule: “wfb”
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (II) NVIDIA(GPU-1): Deleting GPU-1
[ 58.769] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[ 58.769] (II) NVIDIA: access.
[ 58.778] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 58.778] (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
[ 58.778] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 58.778] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 58.778] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 58.778] (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
[ 58.778] (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
[ 58.778] (II) NVIDIA(0): Config Options in the README.
[ 58.792] (II) NVIDIA(0): Setting mode “DFP-4:nvidia-auto-select”
[ 58.898] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 58.898] (==) NVIDIA(0): Backing store enabled
[ 58.898] (==) NVIDIA(0): Silken mouse enabled
[ 58.898] () NVIDIA(0): DPMS enabled**
[ 58.898] (II) Loading sub module “dri2”
and heres some more of the nvidia messages in xorg if you wanna view more ill upload the full log but i personally think this is a nvidia issue since i signaled it all out the only thing that causes this problem is the 555.58 drivers.

[ 57.331] (==) Log file: “/var/log/Xorg.0.log”, Time: Sun Jul 7 18:23:48 2024
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 57.332] (==) Using config file: “/etc/X11/xorg.conf”
[ 57.332] (==) Using config directory: “/etc/X11/xorg.conf.d”
[ 57.332] (==) Using system config directory “/usr/share/X11/xorg.conf.d”
[ 57.333] (==) ServerLayout “Layout0”
[ 57.333] () |–>Screen “Screen0” (0)
[ 57.333] (
) | |–>Monitor “Monitor0”
[ 57.334] (==) No device specified for screen “Screen0”.
Using the first device section listed.
[ 57.334] () | |–>Device “NVIDIA RTX 4060”
[ 57.334] (
) |–>Input Device “Keyboard0”
[ 57.351] (II) NVIDIA dlloader X Driver 555.58.02 Tue Jun 25 01:14:56 UTC 2024
[ 57.351] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 57.354] () NVIDIA(0): Depth 24, (–) framebuffer bpp 32
[ 57.354] (==) NVIDIA(0): RGB weight 888
[ 57.354] (==) NVIDIA(0): Default visual is TrueColor
[ 57.354] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 57.354] (
) NVIDIA(0): Option “Coolbits” “8”
[ 57.354] () NVIDIA(0): Enabling 2D acceleration
[ 57.354] (II) Loading sub module “glxserver_nvidia”
[ 57.354] (II) LoadModule: “glxserver_nvidia”
[ 57.354] (II) Loading /usr/lib/nvidia/xorg/libglxserver_nvidia.so
[ 57.412] (II) Module glxserver_nvidia: vendor=“NVIDIA Corporation”
[ 57.412] compiled for 1.6.99.901, module version = 1.0.0
[ 57.413] Module class: X.Org Server Extension
[ 57.413] (II) NVIDIA GLX Module 555.58.02 Tue Jun 25 01:12:27 UTC 2024
[ 57.413] (II) NVIDIA: The X server supports PRIME Render Offload.
[ 58.645] (–) NVIDIA(0): Valid display device(s) on GPU-0 at PCI:1:0:0
[ 58.645] (–) NVIDIA(0): DFP-0
[ 58.645] (–) NVIDIA(0): DFP-1
[ 58.645] (–) NVIDIA(0): DFP-2
[ 58.645] (–) NVIDIA(0): DFP-3
[ 58.645] (–) NVIDIA(0): DFP-4 (boot)
[ 58.645] (–) NVIDIA(0): DFP-5
[ 58.645] (–) NVIDIA(0): DFP-6
[ 58.651] (II) NVIDIA(0): NVIDIA GPU NVIDIA GeForce RTX 4060 (AD107-A) at PCI:1:0:0
[ 58.651] (II) NVIDIA(0): (GPU-0)
[ 58.651] (–) NVIDIA(0): Memory: 8384512 kBytes
[ 58.652] (–) NVIDIA(0): VideoBIOS: 95.07.36.00.e1
[ 58.652] (II) NVIDIA(0): Detected PCI Express Link width: 8X
[ 58.652] (–) NVIDIA(GPU-0): DFP-0: disconnected
[ 58.652] (–) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[ 58.652] (–) NVIDIA(GPU-0): DFP-0: 2670.0 MHz maximum pixel clock
[ 58.652] (–) NVIDIA(GPU-0):
[ 58.652] (–) NVIDIA(GPU-0): DFP-1: disconnected
[ 58.652] (–) NVIDIA(GPU-0): DFP-1: Internal TMDS
[ 58.652] (–) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[ 58.652] (–) NVIDIA(GPU-0):
[ 58.652] (–) NVIDIA(GPU-0): DFP-2: disconnected
[ 58.652] (–) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[ 58.652] (–) NVIDIA(GPU-0): DFP-2: 2670.0 MHz maximum pixel clock
[ 58.652] (–) NVIDIA(GPU-0):
[ 58.652] (–) NVIDIA(GPU-0): DFP-3: disconnected
[ 58.652] (–) NVIDIA(GPU-0): DFP-3: Internal TMDS
[ 58.652] (–) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[ 58.652] (–) NVIDIA(GPU-0):
[ 58.697] (–) NVIDIA(GPU-0): AOP 32HC5QR S (DFP-4): connected
[ 58.697] (–) NVIDIA(GPU-0): AOP 32HC5QR S (DFP-4): Internal TMDS
[ 58.697] (–) NVIDIA(GPU-0): AOP 32HC5QR S (DFP-4): 600.0 MHz maximum pixel clock
[ 58.697] (–) NVIDIA(GPU-0):
[ 58.697] (–) NVIDIA(GPU-0): DFP-5: disconnected
[ 58.697] (–) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[ 58.697] (–) NVIDIA(GPU-0): DFP-5: 2670.0 MHz maximum pixel clock
[ 58.697] (–) NVIDIA(GPU-0):
[ 58.698] (–) NVIDIA(GPU-0): DFP-6: disconnected
[ 58.698] (–) NVIDIA(GPU-0): DFP-6: Internal TMDS
[ 58.698] (–) NVIDIA(GPU-0): DFP-6: 165.0 MHz maximum pixel clock
[ 58.698] (–) NVIDIA(GPU-0):
[ 58.727] (==) NVIDIA(0):
[ 58.727] (==) NVIDIA(0): No modes were requested; the default mode “nvidia-auto-select”
[ 58.727] (==) NVIDIA(0): will be used as the requested mode.
[ 58.727] (==) NVIDIA(0):
[ 58.728] (II) NVIDIA(0): Validated MetaModes:
[ 58.728] (II) NVIDIA(0): “DFP-4:nvidia-auto-select”
[ 58.728] (II) NVIDIA(0): Virtual screen size determined to be 1920 x 1080
[ 58.768] (–) NVIDIA(0): DPI set to (69, 70); computed from “UseEdidDpi” X config
[ 58.768] (–) NVIDIA(0): option
[ 58.768] (
) NVIDIA(G0): Depth 24, (–) framebuffer bpp 32
[ 58.768] (==) NVIDIA(G0): RGB weight 888
[ 58.768] (==) NVIDIA(G0): Default visual is TrueColor
[ 58.768] (==) NVIDIA(G0): Using gamma correction (1.0, 1.0, 1.0)
[ 58.768] (II) Applying OutputClass “nvidia” options to /dev/dri/card2
[ 58.768] () NVIDIA(G0): Option “AllowEmptyInitialConfiguration”
[ 58.768] (
) NVIDIA(G0): Option “Coolbits” “8”
[ 58.768] () NVIDIA(G0): Enabling 2D acceleration
[ 58.768] (II) NVIDIA: The X server supports PRIME Render Offload.
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (EE) NVIDIA(G0): Failing initialization of X screen
[ 58.768] (II) UnloadModule: “nvidia”
[ 58.768] (II) UnloadSubModule: “wfb”
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (II) NVIDIA(GPU-1): Deleting GPU-1
[ 58.769] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[ 58.769] (II) NVIDIA: access.
[ 58.778] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 58.778] (II) NVIDIA(0): may not be running or the “AcpidSocketPath” X
[ 58.778] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 58.778] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 58.778] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 58.778] (II) NVIDIA(0): details, please see the “ConnectToAcpid” and
[ 58.778] (II) NVIDIA(0): “AcpidSocketPath” X configuration options in Appendix B: X
[ 58.778] (II) NVIDIA(0): Config Options in the README.
[ 58.792] (II) NVIDIA(0): Setting mode “DFP-4:nvidia-auto-select”
[ 58.898] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 58.898] (==) NVIDIA(0): Backing store enabled
[ 58.898] (==) NVIDIA(0): Silken mouse enabled
[ 58.898] (
) NVIDIA(0): DPMS enabled
[ 58.898] (II) Loading sub module “dri2”
[ 58.898] (II) LoadModule: “dri2”
[ 58.898] (II) Module “dri2” already built-in
[ 58.898] (II) NVIDIA(0): [DRI2] Setup complete
[ 58.898] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 58.987] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event12)
[ 58.987] (II) No input driver specified, ignoring this device.
[ 58.987] (II) This device may have been added with another device file.
[ 58.987] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event13)
[ 58.987] (II) No input driver specified, ignoring this device.
[ 58.987] (II) This device may have been added with another device file.
[ 58.987] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 58.987] (II) No input driver specified, ignoring this device.
[ 58.987] (II) This device may have been added with another device file.
[ 58.987] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event15)
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (EE) NVIDIA(G0): Failing initialization of X screen
[ 58.768] (II) UnloadModule: “nvidia”
[ 58.768] (II) UnloadSubModule: “wfb”
[ 58.768] (EE) NVIDIA(GPU-1): Failed to initialize the NVIDIA graphics device!
[ 58.768] (II) NVIDIA(GPU-1): Deleting GPU-1
[ 58.769] (II) NVIDIA: Reserving 24576.00 MB of virtual memory for indirect memory
[ 58.769] (II) NVIDIA: access.
[ 58.778] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon

attachment: its .txt fyi
log.txt (37.4 KB)

I can reproduce this on other GNOME versions such as 46.2, 46.3 and 47.alpha.
The monitors used are not a factor in this and likely every driver of the 555 series presents this issue; nvidia-drm.fbdev is not a factor and I don’t think the GSP Firmware is either although I haven’t tested with it enabled for the already reported and partially mitigated stutter issues.
So far I’ve tested 555.58.02 and 555.52.04 while user35044 tested 555.42.02.

The logs are similar to user35044’s and, as per Michel Dänzer, the “Operation not permitted” error can’t be emitted by the kernel so it’s likely NVIDIA Driver related:

“Operation not permitted” is EPERM (error value 1). I can’t find any code in the kernel which could return that error from the atomic commit ioctl, so it’s probably from the nvidia driver. I’d suggest reporting this to Nvidia.

I have tested an identical software configuration, also running the same monitors, on an AMD system and couldn’t reproduce this issue so it’s likely a regression starting from 555.42.02 as I can recall it working on the latest 550/545 Beta drivers.

Also, as 555 is in the New Features branch, and likely being shipped in many distros already, I would suggest checking how widespread this issue is as Direct Scanout provides latency and efficiency improvements and it would be a shame to have this problem reach Stable.
It would be great if anyone could test whether a similar issue happen in KDE Plasma as well.

lug 12 00:45:22 mattia-desktop gnome-shell[2090]: RENDER: Buffer not scanout compatible (see also KMS debug topic)
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: RENDER: Could not acquire scanout
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Swap buffers: 1 frames pending (double-buffering)
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Assigning buffer to primary plane update on CRTC (42) with src rect 0,000000,0,000000 2560,000000x1440,000000 and dst rect 0,0 2560x1440
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Posting primary plane composite update for CRTC 42 (/dev/dri/card0)
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Processing update
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Assigning primary plane (35, /dev/dri/card0) to 109, 2560x1440+0+0 -> 2560x1440+0+0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'FB_ID' (17) to 109
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_ID' (20) to 42
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_X' (9) to 0,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_Y' (10) to 0,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_W' (11) to 2560,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_H' (12) to 1440,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_X' (13) to 0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_Y' (14) to 0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_W' (15) to 2560
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_H' (16) to 1440
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane (35, /dev/dri/card0) rotation to 1
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'rotation' (37) to 1
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Committing update flags: ATOMIC_NONBLOCK|PAGE_FLIP_EVENT
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Adding page flip data for (42, /dev/dri/card0): 0x712aa80531e0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Page flip callback for CRTC (42, /dev/dri/card0), data: 0x712aa80531e0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Setting page flip timings for CRTC (42, /dev/dri/card0), sequence: 0, sec: 5671, usec: 325563
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Assigning buffer to primary plane update on CRTC (42) with src rect 0,000000,0,000000 2560,000000x1440,000000 and dst rect 0,0 2560x1440
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: Posting direct scanout test update for CRTC 42 (/dev/dri/card0) synchronously
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Processing update
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Assigning primary plane (35, /dev/dri/card0) to 108, 2560x1440+0+0 -> 2560x1440+0+0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'FB_ID' (17) to 108
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_ID' (20) to 42
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_X' (9) to 0,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_Y' (10) to 0,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_W' (11) to 2560,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'SRC_H' (12) to 1440,00
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_X' (13) to 0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_Y' (14) to 0
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_W' (15) to 2560
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'CRTC_H' (16) to 1440
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'IN_FENCE_FD' (18) to 136
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane (35, /dev/dri/card0) rotation to 1
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Setting plane 35 (/dev/dri/card0) property 'rotation' (37) to 1
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] Committing update flags: ATOMIC_NONBLOCK|TEST_ONLY
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: KMS: [atomic] KMS update failed: drmModeAtomicCommit: Operation not permitted
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: RENDER: Buffer not scanout compatible (see also KMS debug topic)
lug 12 00:45:22 mattia-desktop gnome-shell[2090]: RENDER: Could not acquire scanout

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

I had a similar issue on RHEL9, and it was resolved by removing older/unused kernel packages.

I just wanted to say that I am also experiencing GSP issues under wayland. I disabled the gsp firmware using nvidia.NVreg_EnableGpuFirmware=0 in the systemd bootloader arguments and kde is actually usable now. I am on arch (kernel: linux 6.9.9) with a normal 4070 using firmware 555.58.02.

This may be off topic given I don’t know how some aspects of the driver releases are handled but that is also why I’m asking.

So what is happening with 555 if 560 and supposedly everything after going to be the “open” drivers? Will 555 be fixed up or will those fixes be in 560?

Also will there be any efforts to make the open drivers NOT conflict with the proprietary ones? Right now my machine has Pascal and Turing based cards. From what I have read the Turing is supported by the open drivers, the Pascal is not meaning I am stuck on the old 555 line which is horribly broken (and whatever becomes of it) unless I can install/build/load both drivers side by side. Worst case will there be efforts to allow the “open” drivers to run along side the nouveau drivers?

Given the drivers have been all down hill since 525 this is starting to feel like a hell of a squeeze.

You really have to read with a little bit of attention.

For mixed deployments with older and newer GPUs in the same system, continue to use the proprietary driver.

To sum it up; they recommend switching to open kernel modules if possible, not mandating it.

They do recommend that because it has feature parity and further improvements,features will focus on that stack.

Well I didn’t read the news from nVidia’s own post i.e. details were likely omitted from the sources I saw reporting on this without citation etc.

Since the last update driver update to 555.58.02 I can’t suspend&resume my laptop anymore. Suspend works, but on resume the device driver crashes and all displays stay black. Looking into the logs after reboot I see unhandled page faults caused by the nvidia device driver, and multiple follow-on errors.

I’ve meanwhile tested multiple permutations of module parameters. All of these fail in the same/similar way:

options nvidia-drm fbdev=1
options nvidia-drm fbdev=0
options nvidia NVreg_PreserveVideoMemoryAllocations=1
options nvidia NVreg_PreserveVideoMemoryAllocations=0

Distribution: Fedora 40
Kernel: 6.9.9-200.fc40.x86_64
GPU: NVIDIA T1200 Laptop GPU
Driver: 555.58.02

Jul 18 19:32:34 kernel: BUG: unable to handle page fault for address: ffffbe3894fa9604
Jul 18 19:32:34 kernel: #PF: supervisor read access in kernel mode
Jul 18 19:32:34 kernel: #PF: error_code(0x0000) - not-present page
Jul 18 19:32:34 kernel: PGD 100000067 P4D 100000067 PUD 1002ab067 PMD 0
Jul 18 19:32:34 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Jul 18 19:32:34 kernel: CPU: 0 PID: 562 Comm: irq/145-nvidia Tainted: P           OE      6.9.9-200.fc40.x86_64 #1
Jul 18 19:32:34 kernel: Hardware name: LENOVO 20Y4S32J06/20Y4S32J06, BIOS N40ET46W (1.28 ) 05/07/2024
Jul 18 19:32:34 kernel: RIP: 0010:_nv012398rm+0xbd/0x130 [nvidia]
Jul 18 19:32:34 kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 ef 78 65 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Jul 18 19:32:34 kernel: RSP: 0018:ffffbe388084fce0 EFLAGS: 00010286
Jul 18 19:32:34 kernel: RAX: ffff9ceb8c9412d8 RBX: 0000000000000001 RCX: ffffbe3894fa9600
Jul 18 19:32:34 kernel: RDX: fffffffffffffff0 RSI: ffff9ceac2763008 RDI: ffff9ceac27638e8
Jul 18 19:32:34 kernel: RBP: ffff9ceae705abf0 R08: 0000000000000000 R09: 0000000000000020
Jul 18 19:32:34 kernel: R10: ffff9ceae705ac24 R11: ffffffffc0df3cd0 R12: ffff9ceb8c9412d8
Jul 18 19:32:34 kernel: R13: ffff9ceac27638e8 R14: ffff9ceac2763008 R15: 0000000000000000
Jul 18 19:32:34 kernel: FS:  0000000000000000(0000) GS:ffff9cf1fb000000(0000) knlGS:0000000000000000
Jul 18 19:32:34 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 18 19:32:34 kernel: CR2: ffffbe3894fa9604 CR3: 00000002a0428002 CR4: 0000000000f70ef0
Jul 18 19:32:34 kernel: PKRU: 55555554
Jul 18 19:32:34 kernel: Call Trace:
Jul 18 19:32:34 kernel:  <TASK>
Jul 18 19:32:34 kernel:  ? __die_body.cold+0x19/0x27
Jul 18 19:32:34 kernel:  ? page_fault_oops+0x15a/0x2c0
Jul 18 19:32:34 kernel:  ? search_module_extables+0x19/0x60
Jul 18 19:32:34 kernel:  ? search_bpf_extables+0x5f/0x80
Jul 18 19:32:34 kernel:  ? exc_page_fault+0x170/0x180
Jul 18 19:32:34 kernel:  ? asm_exc_page_fault+0x26/0x30
Jul 18 19:32:34 kernel:  ? _nv012399rm+0x1f0/0x1f0 [nvidia]
Jul 18 19:32:34 kernel:  ? _nv012398rm+0xbd/0x130 [nvidia]
Jul 18 19:32:34 kernel:  _nv035255rm+0x19c/0x2f0 [nvidia]
Jul 18 19:32:34 kernel:  _nv030184rm+0x25/0x130 [nvidia]
Jul 18 19:32:34 kernel:  _nv021803rm+0xa2/0x2af [nvidia]
Jul 18 19:32:34 kernel:  _nv031947rm+0x60/0xc0 [nvidia]
Jul 18 19:32:34 kernel:  _nv012544rm+0x27f/0x3f0 [nvidia]
Jul 18 19:32:34 kernel:  _nv031957rm+0x167/0x1d0 [nvidia]
Jul 18 19:32:34 kernel:  _nv000735rm+0x113/0x150 [nvidia]
Jul 18 19:32:34 kernel:  rm_isr_bh+0x20/0x5c [nvidia]
Jul 18 19:32:34 kernel:  nvidia_isr_kthread_bh+0x1f/0x50 [nvidia]
Jul 18 19:32:34 kernel:  irq_thread_fn+0x20/0x60
Jul 18 19:32:34 kernel:  irq_thread+0x1b3/0x2f0
Jul 18 19:32:34 kernel:  ? __pfx_irq_thread_fn+0x10/0x10
Jul 18 19:32:34 kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
Jul 18 19:32:34 kernel:  ? __pfx_irq_thread+0x10/0x10
Jul 18 19:32:34 kernel:  kthread+0xcf/0x100
Jul 18 19:32:34 kernel:  ? __pfx_kthread+0x10/0x10
Jul 18 19:32:34 kernel:  ret_from_fork+0x31/0x50
Jul 18 19:32:34 kernel:  ? __pfx_kthread+0x10/0x10
Jul 18 19:32:34 kernel:  ret_from_fork_asm+0x1a/0x30
Jul 18 19:32:34 kernel:  </TASK>
Jul 18 19:32:34 kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_redir nf_conntrack_tftp bridge stp llc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_h>
Jul 18 19:32:34 kernel:  soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match soundwire_generic_allocation snd_>
Jul 18 19:32:34 kernel:  processor_thermal_wt_req gpu_sched thunderbolt i2c_i801 platform_profile processor_thermal_power_floor snd_timer mei processor_thermal_mbox drm_ttm_helper spi_intel i2c_smbus idma64 intel_soc_dts_iosf snd>
Jul 18 19:32:34 kernel: CR2: ffffbe3894fa9604
Jul 18 19:32:34 kernel: ---[ end trace 0000000000000000 ]---
Jul 18 19:32:34 kernel: RIP: 0010:_nv012398rm+0xbd/0x130 [nvidia]
Jul 18 19:32:34 kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 ef 78 65 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Jul 18 19:32:34 kernel: RSP: 0018:ffffbe388084fce0 EFLAGS: 00010286
Jul 18 19:32:34 kernel: RAX: ffff9ceb8c9412d8 RBX: 0000000000000001 RCX: ffffbe3894fa9600
Jul 18 19:32:34 kernel: RDX: fffffffffffffff0 RSI: ffff9ceac2763008 RDI: ffff9ceac27638e8
Jul 18 19:32:34 kernel: RBP: ffff9ceae705abf0 R08: 0000000000000000 R09: 0000000000000020
Jul 18 19:32:34 kernel: R10: ffff9ceae705ac24 R11: ffffffffc0df3cd0 R12: ffff9ceb8c9412d8
Jul 18 19:32:34 kernel: R13: ffff9ceac27638e8 R14: ffff9ceac2763008 R15: 0000000000000000
Jul 18 19:32:34 kernel: FS:  0000000000000000(0000) GS:ffff9cf1fb000000(0000) knlGS:0000000000000000
Jul 18 19:32:34 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 18 19:32:34 kernel: CR2: ffffbe3894fa9604 CR3: 00000002a0428002 CR4: 0000000000f70ef0
Jul 18 19:32:34 kernel: PKRU: 55555554
Jul 18 19:32:34 kernel: note: irq/145-nvidia[562] exited with irqs disabled
Jul 18 19:32:34 kernel: kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
Jul 18 19:32:34 kernel: BUG: unable to handle page fault for address: ffff9ceaf1bcaf40
Jul 18 19:32:34 kernel: #PF: supervisor instruction fetch in kernel mode
Jul 18 19:32:34 kernel: #PF: error_code(0x0011) - permissions violation
Jul 18 19:32:34 kernel: PGD 2a1801067 P4D 2a1801067 PUD 10249c063 PMD 131adf063 PTE 8000000131bca163
Jul 18 19:32:34 kernel: Oops: 0011 [#2] PREEMPT SMP NOPTI
Jul 18 19:32:34 kernel: CPU: 0 PID: 562 Comm: irq/145-nvidia Tainted: P      D    OE      6.9.9-200.fc40.x86_64 #1
Jul 18 19:32:34 kernel: Hardware name: LENOVO 20Y4S32J06/20Y4S32J06, BIOS N40ET46W (1.28 ) 05/07/2024
Jul 18 19:32:34 kernel: RIP: 0010:0xffff9ceaf1bcaf40
Jul 18 19:32:34 kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <00> 40 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Jul 18 19:32:34 kernel: RSP: 0018:ffffbe388084feb0 EFLAGS: 00010286
Jul 18 19:32:34 kernel: RAX: ffff9ceaf1bcaf40 RBX: ffffffff8f15452d RCX: 00000000000001c0
Jul 18 19:32:34 kernel: RDX: 0000000000000001 RSI: 0000000000000282 RDI: ffffbe388084feb0
Jul 18 19:32:34 kernel: RBP: ffff9ceaf1bcaf40 R08: 0000000000000000 R09: 312f717269203a65
Jul 18 19:32:34 kernel: R10: ffffbe388084fd08 R11: 7269203a65746f6e R12: ffff9ceaf1bcbc1c
Jul 18 19:32:34 kernel: R13: ffff9ceaf1ba5a01 R14: 0000000000000000 R15: 0000000000000000
Jul 18 19:32:34 kernel: FS:  0000000000000000(0000) GS:ffff9cf1fb000000(0000) knlGS:0000000000000000
Jul 18 19:32:34 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 18 19:32:34 kernel: CR2: ffff9ceaf1bcaf40 CR3: 00000002a0428002 CR4: 0000000000f70ef0
Jul 18 19:32:34 kernel: PKRU: 55555554
Jul 18 19:32:34 kernel: Call Trace:
Jul 18 19:32:34 kernel:  <TASK>
Jul 18 19:32:34 kernel:  ? __die_body.cold+0x19/0x27
Jul 18 19:32:34 kernel:  ? page_fault_oops+0x15a/0x2c0
Jul 18 19:32:34 kernel:  ? search_module_extables+0x19/0x60
Jul 18 19:32:34 kernel:  ? exc_page_fault+0x170/0x180
Jul 18 19:32:34 kernel:  ? asm_exc_page_fault+0x26/0x30
Jul 18 19:32:34 kernel:  ? task_work_run+0x4d/0x90
Jul 18 19:32:34 kernel:  ? task_work_run+0x59/0x90
Jul 18 19:32:34 kernel:  ? do_exit+0x31b/0xac0
Jul 18 19:32:34 kernel:  ? make_task_dead+0x90/0x90
Jul 18 19:32:34 kernel:  ? rewind_stack_and_make_dead+0x16/0x20
Jul 18 19:32:34 kernel:  </TASK>
Jul 18 19:32:34 kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_redir nf_conntrack_tftp bridge stp llc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_h>
Jul 18 19:32:34 kernel:  soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match soundwire_generic_allocation snd_>
Jul 18 19:32:34 kernel:  processor_thermal_wt_req gpu_sched thunderbolt i2c_i801 platform_profile processor_thermal_power_floor snd_timer mei processor_thermal_mbox drm_ttm_helper spi_intel i2c_smbus idma64 intel_soc_dts_iosf snd>
Jul 18 19:32:34 kernel: CR2: ffff9ceaf1bcaf40
Jul 18 19:32:34 kernel: ---[ end trace 0000000000000000 ]---
Jul 18 19:32:34 kernel: RIP: 0010:_nv012398rm+0xbd/0x130 [nvidia]
Jul 18 19:32:34 kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 ef 78 65 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Jul 18 19:32:34 kernel: RSP: 0018:ffffbe388084fce0 EFLAGS: 00010286
Jul 18 19:32:34 kernel: RAX: ffff9ceb8c9412d8 RBX: 0000000000000001 RCX: ffffbe3894fa9600
Jul 18 19:32:34 kernel: RDX: fffffffffffffff0 RSI: ffff9ceac2763008 RDI: ffff9ceac27638e8
Jul 18 19:32:34 kernel: RBP: ffff9ceae705abf0 R08: 0000000000000000 R09: 0000000000000020
Jul 18 19:32:34 kernel: R10: ffff9ceae705ac24 R11: ffffffffc0df3cd0 R12: ffff9ceb8c9412d8
Jul 18 19:32:34 kernel: R13: ffff9ceac27638e8 R14: ffff9ceac2763008 R15: 0000000000000000
Jul 18 19:32:34 kernel: FS:  0000000000000000(0000) GS:ffff9cf1fb000000(0000) knlGS:0000000000000000
Jul 18 19:32:34 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 18 19:32:34 kernel: CR2: ffff9ceaf1bcaf40 CR3: 00000002a0428002 CR4: 0000000000f70ef0
Jul 18 19:32:34 kernel: PKRU: 55555554
Jul 18 19:32:34 kernel: note: irq/145-nvidia[562] exited with irqs disabled
Jul 18 19:32:34 kernel: Fixing recursive fault but reboot is needed!
Jul 18 19:32:34 kernel: BUG: scheduling while atomic: irq/145-nvidia/562/0x00000000
Jul 18 19:32:34 kernel: Modules linked in: uinput snd_seq_dummy snd_hrtimer rfcomm xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_nat_tftp nft_redir nf_conntrack_tftp bridge stp llc snd_ctl_led snd_soc_skl_hda_dsp snd_soc_h>
Jul 18 19:32:34 kernel:  soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_soc_acpi_intel_match soundwire_generic_allocation snd_>
Jul 18 19:32:34 kernel:  processor_thermal_wt_req gpu_sched thunderbolt i2c_i801 platform_profile processor_thermal_power_floor snd_timer mei processor_thermal_mbox drm_ttm_helper spi_intel i2c_smbus idma64 intel_soc_dts_iosf snd>
Jul 18 19:32:34 kernel: CPU: 0 PID: 562 Comm: irq/145-nvidia Tainted: P      D    OE      6.9.9-200.fc40.x86_64 #1
Jul 18 19:32:34 kernel: Hardware name: LENOVO 20Y4S32J06/20Y4S32J06, BIOS N40ET46W (1.28 ) 05/07/2024
Jul 18 19:32:34 kernel: Call Trace:
Jul 18 19:32:34 kernel:  <TASK>
Jul 18 19:32:34 kernel:  dump_stack_lvl+0x5d/0x80
Jul 18 19:32:34 kernel:  __schedule_bug.cold+0x42/0x4e
Jul 18 19:32:34 kernel:  __schedule+0x10f2/0x1710
Jul 18 19:32:34 kernel:  ? __wake_up_klogd.part.0+0x3c/0x60
Jul 18 19:32:34 kernel:  ? vprintk_emit+0x176/0x2a0
Jul 18 19:32:34 kernel:  ? _printk+0x6c/0x87
Jul 18 19:32:34 kernel:  do_task_dead+0x42/0x50
Jul 18 19:32:34 kernel:  make_task_dead.cold+0xd9/0xe5
Jul 18 19:32:34 kernel:  rewind_stack_and_make_dead+0x16/0x20
Jul 18 19:32:34 kernel: RIP: 0000:0x0
Jul 18 19:32:34 kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Jul 18 19:32:34 kernel: RSP: 0000:0000000000000000 EFLAGS: 00000000 ORIG_RAX: 0000000000000000
Jul 18 19:32:34 kernel: RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000
Jul 18 19:32:34 kernel: RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
Jul 18 19:32:34 kernel: RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
Jul 18 19:32:34 kernel: R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000000
Jul 18 19:32:34 kernel: R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
Jul 18 19:32:34 kernel:  </TASK>
Jul 18 19:32:36 kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.

This is definitely a regession, I used to be able to suspend&resume that same machine for days.

nvidia please can you confirm the bug ?

Running into an issue where plasma will freeze once the panel is hidden and becomes active again while the panel (specifically the one on my secondary monitor) is revealed. The latter only sometimes happens, no clue why. Turning on/off GSP did not fix the issue. Also happens when any application goes fullscreen.

KDE Plasma 6.1.3
nvidia proprietary 555.58.02
Kernel 6.9.10-zen1-1-zen

EDIT: Seems to be the same as this: 555 release feedback & discussion - #78 by kodatarule