# 580 release feedback & discussion

**URL:** <https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205>\
**Category:** Linux\
**Created:** [August 4, 2025, 2:15pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205 "2025-08-04T14:15:05Z")\
**Posts on this page:** 20\
**Page:** 39

<div class="post-metadata">

**Author:** ![n7v321](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@n7v321](https://forums.developer.nvidia.com/u/n7v321)\
**Post date:** [November 11, 2025, 1:08pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/790 "2025-11-11T13:08:52Z")

</div>

For my monitor resolution issue: Nvidia (Andy) asked me to enable ModeDebug in my /etc/X11/xorg.conf, restart and provide the /var/log/Xorg.0.log which I have done. The log shows that “Mode is rejected: PixelClock (185.6 MHz) too high for Display Device (Max: 165.0 MHz)”

But EDID shows that the the resolution is valid and that the max dotclock is 240 Mhz, so this 165 limit seems to be artificially imposed. This occurs for both of my monitors (HDMI-4 and DP-6).

---

<div class="post-metadata">

**Author:** ![gsrcrxsi](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@gsrcrxsi](https://forums.developer.nvidia.com/u/gsrcrxsi)\
**Post date:** [November 11, 2025, 1:37pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/791 "2025-11-11T13:37:26Z")

</div>

@vrachatte @amrits @aplattner

once again inquiring about internal bug #5497358.

it appears to be a bug in the JIT compiler. please comment.

---

<div class="post-metadata">

**Author:** ![Tekstryder](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/tekstryder/32/393374_2.png) [@Tekstryder](https://forums.developer.nvidia.com/u/Tekstryder)\
**Post date:** [November 11, 2025, 3:33pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/792 "2025-11-11T15:33:22Z")

</div>

> [@shelter](#):
>
> GTK4 got a pretty severe Vulkan bug that may cause apps to crash.

> [@shelter](#):
>
> The GTK devs are aware of it.

Please provide a link to this issue. I cannot find it on [GTK GitLab](https://gitlab.gnome.org/GNOME/gtk/-/issues?label_name%5B%5D=Vulkan%20Renderer).

---

<div class="post-metadata">

**Author:** ![amrits](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/amrits/32/14043_2.png) [@amrits](https://forums.developer.nvidia.com/u/amrits)\
**Post date:** [November 11, 2025, 6:02pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/793 "2025-11-11T18:02:11Z")

</div>

I am following up internally with the concerned team.

Thanks for being patient.

---

<div class="post-metadata">

**Author:** ![amrits](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/amrits/32/14043_2.png) [@amrits](https://forums.developer.nvidia.com/u/amrits)\
**Post date:** [November 11, 2025, 6:03pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/794 "2025-11-11T18:03:18Z")

</div>

Could you please share nvidia bug report from repro state.

---

<div class="post-metadata">

**Author:** ![amrits](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/amrits/32/14043_2.png) [@amrits](https://forums.developer.nvidia.com/u/amrits)\
**Post date:** [November 11, 2025, 6:08pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/795 "2025-11-11T18:08:30Z")

</div>

Hi All,

We have filed a bug 5651624 for issue “Monitor resolution limited to 1920x1080 with driver 580.105.08” and able to reproduce issue locally.

Engineering team is looking into it with high priority and shall share further updates very soon.

---

<div class="post-metadata">

**Author:** ![saschaheid](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@saschaheid](https://forums.developer.nvidia.com/u/saschaheid)\
**Post date:** [November 11, 2025, 6:11pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/796 "2025-11-11T18:11:08Z")

</div>

I am getting horizontal lines on kde wayland.  
These lines disappear or flicker when i move windows or when the mouse-cursor moves over certain ui elements.

They come and go but always return.  
They do not show up on screenshots or screen recordings.  
They temporarily disappear when i change the adaptive sync setting.

nvidia driver: 580.105.08, gpu 4070, kernel 6.17.7-2-MANJARO, display: 8K TV over hdmi

Is this something that is already known?  
I had these before but it’s gotten worse.

Thank you.

---

<div class="post-metadata">

**Author:** ![DanielCeregatti](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@DanielCeregatti](https://forums.developer.nvidia.com/u/DanielCeregatti)\
**Post date:** [November 11, 2025, 6:42pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/797 "2025-11-11T18:42:11Z")

</div>

I’m still getting the issue of desktop stuttering in Xorg that is accompanied by this output in `/var/log/Xorg.0.log`:

```auto
[288926.151] (--) NVIDIA(GPU-0): DFP-0: disconnected
[288926.152] (--) NVIDIA(GPU-0): DFP-0: Internal DisplayPort
[288926.152] (--) NVIDIA(GPU-0): DFP-0: 2670.0 MHz maximum pixel clock
[288926.152] (--) NVIDIA(GPU-0): 
[288926.153] (--) NVIDIA(GPU-0): DFP-1: disconnected
[288926.153] (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
[288926.153] (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
[288926.153] (--) NVIDIA(GPU-0): 
[288926.153] (--) NVIDIA(GPU-0): DFP-2: disconnected
[288926.153] (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
[288926.153] (--) NVIDIA(GPU-0): DFP-2: 2670.0 MHz maximum pixel clock
[288926.153] (--) NVIDIA(GPU-0): 
[288926.153] (--) NVIDIA(GPU-0): DFP-3: disconnected
[288926.153] (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
[288926.153] (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
[288926.153] (--) NVIDIA(GPU-0): 
[288926.197] (--) NVIDIA(GPU-0): LG Electronics LG TV SSCR2 (DFP-4): connected
[288926.197] (--) NVIDIA(GPU-0): LG Electronics LG TV SSCR2 (DFP-4): Internal TMDS
[288926.197] (--) NVIDIA(GPU-0): LG Electronics LG TV SSCR2 (DFP-4): 42666.7 MHz maximum pixel clock
[288926.197] (--) NVIDIA(GPU-0): 
[288926.197] (--) NVIDIA(GPU-0): DFP-5: disconnected
[288926.197] (--) NVIDIA(GPU-0): DFP-5: Internal DisplayPort
[288926.197] (--) NVIDIA(GPU-0): DFP-5: 2670.0 MHz maximum pixel clock

```

The output above will be appended to that log in rapid succession when the issue occurs. When it happens, the entire Xorg desktop freezes, some times for seconds at a time. I’m using KDE Plasma on Debian testing.

I last reported this here:

> [@575 release feedback & discussion](https://forums.developer.nvidia.com/t/575-release-feedback-discussion/330513/288):
>
> I have posted several times regarding stuttering and what I’ve found that triggers it. The stuttering is always accompanied by those log entries happening over and over: Yes, that’s 3 posts in a row to the same topic. Perhaps I shouldn’t have selected Rick Astley’s video for the example in the last post, but it’s a legit demonstration of the issue. @aplattner I also have no performance or overlay apps running. The one constant has been JetBrains toolbox and Intellij IDE (the former is a …

This issue prevents me from using Intellij to this day, as running it causes unacceptable UI stuttering since it triggers the issue so often as to make the desktop unusable.

My previous report includes links to other people’s reports, but there are many other reports. Search this forum for `notify-send` to find these reports.

Side note: when running `nvidia-bug-report.sh`, the output appeared 5 times in the log.

[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/fvwFceZccT36FMliKLBNnKc0jcX.gz) (2.1 MB)

I’d love to be able to run IntelliJ again some day…

---

<div class="post-metadata">

**Author:** ![forbyta](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@forbyta](https://forums.developer.nvidia.com/u/forbyta)\
**Post date:** [November 11, 2025, 7:11pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/798 "2025-11-11T19:11:58Z")

</div>

@amrits

Could you please add to bug 5651624 that it may not be limited to 1920x1080 and/or 580.105.08.

Maybe what I’ve encountered is a different bug, but as I outlined in [this post from Oct 27](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/674), it sounds very much like the same bug. For whatever reason, I’ve seen the bug with every version of 580 I’ve tested and the max resolution I get is 1366x768. Perhaps it’s because the actual max resolution for my external monitor is 1920x1080 - in other words, maybe the bug doesn’t limit to 1920x1080, but rather some resolution below the max of the monitor.

As previously stated, I’d be happy test any distro/driver version I’m able to and provide whatever logs are needed to track this down. As it stands right now, I can’t upgrade my current system because of this bug.

---

<div class="post-metadata">

**Author:** ![BlueGoliath](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@BlueGoliath](https://forums.developer.nvidia.com/u/BlueGoliath)\
**Post date:** [November 11, 2025, 7:42pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/799 "2025-11-11T19:42:26Z")

</div>

I think i’m using the OpenGL backend. I meant failed to start, not crash. Edited my comment.

---

<div class="post-metadata">

**Author:** ![mdawson2](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@mdawson2](https://forums.developer.nvidia.com/u/mdawson2)\
**Post date:** [November 11, 2025, 8:40pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/800 "2025-11-11T20:40:34Z")

</div>

I’ve had this too for weeks, seems to be 580 related

---

<div class="post-metadata">

**Author:** ![n7v321](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@n7v321](https://forums.developer.nvidia.com/u/n7v321)\
**Post date:** [November 12, 2025, 2:13pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/801 "2025-11-12T14:13:54Z")

</div>

@forbyta

If you’re seeing this then what i did was run the nvidia-bug-report script, and then they also had me turn on ModeDebug in /etc/X11/xorg.conf (can use `nvidia-xconfig --mode-debug`). restart x11 or your system and you’ll get a /var/log/Xorg.0.log. For me that log listed the different monitor modes and for my 2560x1080 resolution it gave the error i listed earlier: “Mode is rejected: PixelClock (185.6 MHz) too high for Display Device (Max: 165.0 MHz)". But from the EDID my logs showed the monitors did support that mode, and its max dotclock was 240 Mhz, not 165.

---

<div class="post-metadata">

**Author:** ![zebcom](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@zebcom](https://forums.developer.nvidia.com/u/zebcom)\
**Post date:** [November 12, 2025, 4:25pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/802 "2025-11-12T16:25:36Z")

</div>

Not critical, but Bladur’s Gate 3 with Vulkan renderer still requires the `__GL_13ebad=0x1` hack to perform correctly (RTX 5080, I get 144 fps vs 40 for the same scene!). I believe this is important for the users of the native version.

---

<div class="post-metadata">

**Author:** ![airlinese](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@airlinese](https://forums.developer.nvidia.com/u/airlinese)\
**Post date:** [November 13, 2025, 11:34am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/804 "2025-11-13T11:34:11Z")

</div>

Checked bug 5507242 with nvidia-open 580.105.08 and latest game update (8.9.0), I can reproduce on this driver version FYI.

---

<div class="post-metadata">

**Author:** ![james289](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@james289](https://forums.developer.nvidia.com/u/james289)\
**Post date:** [November 13, 2025, 1:35pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/805 "2025-11-13T13:35:53Z")

</div>

I get frequent crashes especially when playing youtube videos.

This bug has been around a while! Can someone please investigate it?

> [@Repeatable crash involving NvKmsKapiMemory when playing 4k60 videos on youtube](https://forums.developer.nvidia.com/t/repeatable-crash-involving-nvkmskapimemory-when-playing-4k60-videos-on-youtube/334286/1):
>
> bug report log [nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/eF4byITsvO2dvsjLBAh4j5G1bTl.gz) (435.0 KB) summary The GPU driver crashes easily when multiple 4k60 videos are open in youtube tabs in chromium. The result ranges from: all monitors are frozen all monitors turn white but can barely see some functioning UI underneath if lucky monitors do not freeze, only chromium, and you can still interact with the desktop The error tends to be one of the following: Failed to map NvKmsKapiMemory Failed to ioremap\_wc NvKmsKapiMemory In the attached…

> **[Reddit - The heart of the internet](https://www.reddit.com/r/linuxquestions/comments/1ikachf/system_crashes_because_of_nvidia_drivers_and/)**

> [@575 release feedback & discussion](https://forums.developer.nvidia.com/t/575-release-feedback-discussion/330513/296):
>
> I have seen a couple of crashes with nvidia 575.57.08, usually when playing youtube videos in google chrome. Logs: Jun 16 10:33:15 james-office-desktop kernel: NVRM: dmaAllocMapping\_GM107: can't alloc VA space for mapping. Jun 16 10:33:15 james-office-desktop kernel: NVRM: dmaAllocMapping\_GM107: can't alloc VA space for mapping. Jun 16 10:33:15 james-office-desktop kernel: NVRM: dmaAllocMapping\_GM107: can't alloc VA space for mapping. Jun 16 10:33:15 james-office-desktop kernel: NVRM: dmaAlloc…

```auto
Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:32 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:57:32 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from reusemappingdbMap(&pBar1VaInfo->reuseDb, pMappingType, mapRange, pMemArea, cachingFlags) @ kern_bus_gm107.c:3186

Nov 13 11:57:32 office-desktop kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000e00] Failed to map NvKmsKapiMemory 0x0000000000a80c73

Nov 13 11:57:32 office-desktop kernel: traps: ThreadPoolForeg[3524557] trap invalid opcode ip:55d797bc3d16 sp:7fa24cffb360 error:0 in chrome[a9f8d16,55d78ff1d000+c2eb000]

Nov 13 11:57:32 office-desktop systemd-coredump[3525462]: Process 3524555 (chrome) of user 1000 terminated abnormally with signal 4/ILL, processing...

Nov 13 11:57:32 office-desktop systemd[1]: Started Process Core Dump (PID 3525462/UID 0).

Nov 13 11:57:41 office-desktop NetworkManager[1653]: <info> [1763035061.4476] device (wlan0): set-hw-addr: set MAC address to 1E:EB:3F:03:04:E4 (scanning)

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:57:54 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:57:54 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from reusemappingdbMap(&pBar1VaInfo->reuseDb, pMappingType, mapRange, pMemArea, cachingFlags) @ kern_bus_gm107.c:3186

Nov 13 11:57:54 office-desktop kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000e00] Failed to map NvKmsKapiMemory 0x000000000cbd996c

Nov 13 11:57:54 office-desktop kernel: traps: ThreadPoolForeg[3525892] trap invalid opcode ip:55d797bc3d16 sp:7fa24cffb360 error:0 in chrome[a9f8d16,55d78ff1d000+c2eb000]

Nov 13 11:57:54 office-desktop systemd-coredump[3525950]: Process 3525890 (chrome) of user 1000 terminated abnormally with signal 4/ILL, processing...

Nov 13 11:57:54 office-desktop systemd[1]: Started Process Core Dump (PID 3525950/UID 0).

Nov 13 11:58:08 office-desktop systemd-coredump[3525463]: Process 3524555 (chrome) of user 1000 dumped core.

                                                                Stack trace of thread 3:

#0 0x000055d797bc3d16 n/a (n/a + 0x0)

                                                                ELF object binary architecture: AMD x86-64

Nov 13 11:58:09 office-desktop systemd[1]: systemd-coredump@12-2-3525462_3525463-0.service: Deactivated successfully.

Nov 13 11:58:09 office-desktop systemd[1]: systemd-coredump@12-2-3525462_3525463-0.service: Consumed 7.533s CPU time, 3.4G memory peak.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:58:12 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:58:12 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from reusemappingdbMap(&pBar1VaInfo->reuseDb, pMappingType, mapRange, pMemArea, cachingFlags) @ kern_bus_gm107.c:3186

Nov 13 11:58:12 office-desktop kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000e00] Failed to map NvKmsKapiMemory 0x00000000c0f9c480

Nov 13 11:58:12 office-desktop kernel: traps: ThreadPoolForeg[3526034] trap invalid opcode ip:55d797bc3d16 sp:7fa24cffb360 error:0 in chrome[a9f8d16,55d78ff1d000+c2eb000]

Nov 13 11:58:12 office-desktop systemd-coredump[3526093]: Process 3526032 (chrome) of user 1000 terminated abnormally with signal 4/ILL, processing...

Nov 13 11:58:12 office-desktop systemd[1]: Started Process Core Dump (PID 3526093/UID 0).

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from reusemappingdbMap(&pBar1VaInfo->reuseDb, pMappingType, mapRange, pMemArea, cachingFlags) @ kern_bus_gm107.c:3186

Nov 13 11:59:23 office-desktop kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000e00] Failed to map NvKmsKapiMemory 0x00000000cc210182

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: dmaAllocMapping_GM107: can't alloc VA space for mapping.

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from pReuseMappingDb->pMapCb(pReuseMappingDb->pGlobalCtx, pAllocCtx, range, cachingFlags, &token, _reusemappingdbAddMappingCallback) @ mapping_reuse.c:273

Nov 13 11:59:23 office-desktop kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Out of memory [NV_ERR_NO_MEMORY] (0x00000051) returned from reusemappingdbMap(&pBar1VaInfo->reuseDb, pMappingType, mapRange, pMemArea, cachingFlags) @ kern_bus_gm107.c:3186

Nov 13 11:59:23 office-desktop kernel: [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000e00] Failed to map NvKmsKapiMemory 0x00000000cbb6f5c0

Nov 13 11:59:23 office-desktop kernel: traps: ThreadPoolForeg[3526054] trap invalid opcode ip:55d797bc3d16 sp:7fa24cffb360 error:0

Nov 13 11:59:23 office-desktop kernel: traps: ThreadPoolForeg[3526055] trap invalid opcode ip:55d797bc3d16 sp:7fa24c7fa360 error:0

Nov 13 11:59:23 office-desktop kernel: in chrome[a9f8d16,55d78ff1d000+c2eb000]

Nov 13 11:59:23 office-desktop kernel: in chrome[a9f8d16,55d78ff1d000+c2eb000]

Nov 13 11:59:23 office-desktop kernel: 

Nov 13 11:59:23 office-desktop systemd-coredump[3527813]: Process 3526052 (chrome) of user 1000 terminated abnormally with signal 4/ILL, processing...

Nov 13 11:59:23 office-desktop systemd[1]: Started Process Core Dump (PID 3527813/UID 0).

Nov 13 11:59:32 office-desktop systemd-coredump[3525951]: Process 3525890 (chrome) of user 1000 dumped core.

```

---

<div class="post-metadata">

**Author:** ![kjetil.s](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@kjetil.s](https://forums.developer.nvidia.com/u/kjetil.s)\
**Post date:** [November 13, 2025, 8:01pm UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/806 "2025-11-13T20:01:04Z")

</div>

I have the same issue as stephematician [#641](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/641) and m.mucahidbenlioglu [#644](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/644) with games freezing on alt-tab. (Especially in Borderless Window mode)  
NVBug internally to track this issue - 5596412, according to [Downgrade 580 on Ubuntu? Wine freezes (any D3D) - #5 by abchauhan](https://forums.developer.nvidia.com/t/downgrade-580-on-ubuntu-wine-freezes-any-d3d/348115/5)

Attached nvidia-bug-report:

[nvidia-bug-report.log.gz](https://forums.developer.nvidia.com/uploads/short-url/e6Lb6WTi5kboO6hSXauqDMUI8GR.gz) (825.1 KB)

Games affected: Deep Rock Galactic and Space Engineers and Raft. Game freezes every time. Games not affected: Black Mesa.  
I tried launching Space Engineers game in “Borderless Window” mode with strace, which slowed everything down. Then alt-tab then worked 10 or so times before the game froze.  
Raft has no issues in Fullscreen (“Exclusive”) , but freezes when alt-tab’in in “Borderless”  
Deep Rock Galactic and Space Engineers can alt-tab a handfull of times in “Fullscreen” before freezing, but freezes every time when alt-tab’ing in “Borderless Window”  
Black Mesa can alt-tab without freezing in both “Fullscreen” and “Fullscreen Window” mode.

Operating System: Kubuntu 24.04  
KDE Plasma Version: 5.27.12  
KDE Frameworks Version: 5.115.0  
Qt Version: 5.15.13  
Kernel Version: 6.8.0-87-generic (64-bit)  
Graphics Platform: X11  
Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics  
Memory: 15,0 GiB of RAM  
Graphics Processor: AMD Radeon Graphics integrated + nVidia RTX3060 mobile  
Graphics Driver: nVidia 580.95.05 Proprietary (not -open)

---

<div class="post-metadata">

**Author:** ![MelanieB](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/melanieb/32/418478_2.png) [@MelanieB](https://forums.developer.nvidia.com/u/MelanieB)\
**Post date:** [November 14, 2025, 12:19am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/807 "2025-11-14T00:19:54Z")

</div>

Hey :)

Strange.  
For me the meshes look normal on **580.95.05**. After half an hour is still all okay.

And now - after 1 hour - still all looks fine.

```auto
Operating System: TUXEDO OS 24.04.3 LTS noble (based on Ubuntu)
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-115036-tuxedo (64-bit)
Graphics Platform: X11

Motherboard: ASUSTeK ROG STRIX X670E-A GAMING WIFI (Bios 3304)
CPU: AMD Ryzen 7 7800X3D 8-Core Processor
RAM: 64 GB ADATA XPG
GPU: Asus Rog Strix RTX 4090 OC

```

```auto
~$ inxi -GxxxZ
Graphics:
  Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: ASUSTeK driver: nvidia
    v: 580.95.05 arch: Lovelace pcie: speed: 16 GT/s lanes: 16 ports:
    active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, HDMI-A-2
    bus-ID: 01:00.0 chip-ID: 10de:2684 class-ID: 0300
  Display: x11 server: X_Org v: 21.1.11 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x333mm (23.70x13.11")
    s-diag: 688mm (27.09")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: MSI MAG 274QRFW
    serial: CC2HE74300349 res: N/A dpi: 108 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") modes: max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.95.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
  API: Vulkan v: 1.4.315 layers: 8 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2684 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
~$

```

 ![Snapshot_2025-11-14_011730_001](https://global.discourse-cdn.com/nvidia/original/4X/a/2/a/a2a4becf94ad2e8d1bfd7269d36480d968a92ea8.jpeg)

Location Landmark if someone want check:

> **[Second Life Maps | Mystic Harbor](https://maps.secondlife.com/secondlife/Mystic%20Harbor/50/193/2004)**

Viewer version:  
Firestorm 7.2.2 (79445) Nov 13 2025 04:23:33 (64bit / AVX2) (Firestorm-Nightlyx64)

---

<div class="post-metadata">

**Author:** ![MelanieB](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/melanieb/32/418478_2.png) [@MelanieB](https://forums.developer.nvidia.com/u/MelanieB)\
**Post date:** [November 14, 2025, 12:39am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/808 "2025-11-14T00:39:35Z")

</div>

Hi,

i am now on

```auto
Operating System: TUXEDO OS 24.04.3 LTS noble (based on Ubuntu)
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.17.0
Qt Version: 6.8.2
Kernel Version: 6.14.0-115036-tuxedo (64-bit)
Graphics Platform: X11

```

```auto
~$ inxi -GxxxZ
Graphics:
  Device-1: NVIDIA AD102 [GeForce RTX 4090] vendor: ASUSTeK driver: nvidia
    v: 580.95.05 arch: Lovelace pcie: speed: 16 GT/s lanes: 16 ports:
    active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, HDMI-A-2
    bus-ID: 01:00.0 chip-ID: 10de:2684 class-ID: 0300
  Display: x11 server: X_Org v: 21.1.11 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia,nvidia-nvswitch
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 108 s-size: 602x333mm (23.70x13.11")
    s-diag: 688mm (27.09")
  Monitor-1: HDMI-A-1 mapped: HDMI-0 note: disabled model: MSI MAG 274QRFW
    serial: CC2HE74300349 res: N/A dpi: 108 size: 597x336mm (23.5x13.23")
    diag: 685mm (27") modes: max: 2560x1440 min: 640x480
  API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
    drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia x11: drv: nvidia
    inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.95.05
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2
  API: Vulkan v: 1.4.315 layers: 8 surfaces: xcb,xlib device: 0
    type: discrete-gpu driver: nvidia device-ID: 10de:2684 device: 1 type: cpu
    driver: mesa llvmpipe device-ID: 10005:0000
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
~$

```

I still have problems with screen freezes and black screens with following system crash.

The problem is that when a crash occurs, I can’t always find entries in the logs with `journalctl` - for whatever reason. On next crash I will post the log if there are some entries in log the time it happens.

I repeatedly had uptimes of 40+ hours now before the next crash (after screen freeze or black screen) occurred.

My monitor also repeatedly fails to wake up when it automatically switches off after 10 minutes due to the energy settings. I have now disabled this feature because it was really annoying, as even when I switched off the monitor using the power button and switched it back on after a moment, the Screen did not always return.

---

<div class="post-metadata">

**Author:** ![luanv.oliveira](https://developer.download.nvidia.com/images/forums/profile-default-devtalk-84.png) [@luanv.oliveira](https://forums.developer.nvidia.com/u/luanv.oliveira)\
**Post date:** [November 14, 2025, 2:15am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/809 "2025-11-14T02:15:04Z")

</div>

if your system just appears to be frozen, you could try to do a emergency disk sync with `alt`+ `prtscn` + `s`, then reboot with `alt` + `prtscn` + `b`, this way you have a higher chance of having logs after the reboot

[more info on the shortcuts](https://en.wikipedia.org/wiki/Magic_SysRq_key)

---

<div class="post-metadata">

**Author:** ![vrachatte](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/vrachatte/32/382649_2.png) [@vrachatte](https://forums.developer.nvidia.com/u/vrachatte)\
**Post date:** [November 14, 2025, 6:11am UTC](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205/810 "2025-11-14T06:11:08Z")

</div>

Thank you for the update, can you please share latest bug report? I will give another try to replicate it.

[Previous page](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205.md?page=38)

[Next page](https://forums.developer.nvidia.com/t/580-release-feedback-discussion/341205.md?page=40)