[Bug 297298] x11/nvidia-kmod-580, x11/nvidia-driver-580, x11/linux-nvidia-libs-580, graphics/nvidia-drm-*-kmod-580: Update to 580.178.04

[email protected] Thu, 06 Aug 2026 07:46:01 +0000
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297298

--- Comment #2 from [email protected] ---
A commit in branch main references this bug:

URL:
https://cgit.FreeBSD.org/ports/commit/?id=5b5cb97ca80e3255c15c6bf7bcb300ad707216f4

commit 5b5cb97ca80e3255c15c6bf7bcb300ad707216f4
Author:     Tomoaki AOKI <[email protected]>
AuthorDate: 2026-08-06 07:43:57 +0000
Commit:     Kevin Bowling <[email protected]>
CommitDate: 2026-08-06 07:45:16 +0000

    x11/nvidia-kmod-580, x11/nvidia-driver-580, x11/linux-nvidia-libs-580,
graphics/nvidia-drm-*-kmod-580: Update to 580.178.04

    Update Legacy version 580 series of drivers to 580.178.04.

    In document below:

   
https://docs.nvidia.com/datacenter/tesla/pdf/NVIDIA_Data_Center_GPU_Driver_Release_Notes_580_v12.0.pdf

    1.2. Fixed Issues
      * When FM deletes a partition, it doesn’t release MC teams, as a result
MC Team
      resources (i.e., MLIDs are leaked). We now delete all outstanding MC
teams
      associated with a partition while de-activating it.
      * Multibank failures have been identified in HBM3E fleet and the current
driver is
      better optimized to handle these failures by triggering channel repair
upon the 2nd
      uncorrectable error in a pseudochannel.
      * On self-hosted systems, the WPR region is mapped in RM reserved memory,
while
      the CPU never explicitly accesses the mapping. The existence of the
mapping could
      lead to CPU speculative access and kernel panic. The fix removes WPR from
reserved
      region mapping and avoids CPU speculative access.
      * GSP unload path is changed to use fast unload instead of full teardown
sequence,
      skipping channel stop/teardown code which may result in a GSP hang/crash.
      * Fixed a bug that could cause Xid 32 errors and application crashes when
scaling via
      CUDA_SCALE_LAUNCH_QUEUES (2x or 4x) with CUDA graphs that have a large
number of
      chained kernel nodes.

    PR:             297298
    Differential Revision:  https://reviews.freebsd.org/D58674

 graphics/nvidia-drm-515-kmod-580/Makefile    | 2 +-
 graphics/nvidia-drm-515-kmod-580/distinfo    | 6 +++---
 graphics/nvidia-drm-61-kmod-580/Makefile     | 2 +-
 graphics/nvidia-drm-61-kmod-580/distinfo     | 6 +++---
 graphics/nvidia-drm-612-kmod-580/Makefile    | 2 +-
 graphics/nvidia-drm-612-kmod-580/distinfo    | 6 +++---
 graphics/nvidia-drm-66-kmod-580/Makefile     | 2 +-
 graphics/nvidia-drm-66-kmod-580/distinfo     | 6 +++---
 graphics/nvidia-drm-kmod-580/Makefile        | 2 +-
 graphics/nvidia-drm-latest-kmod-580/Makefile | 2 +-
 graphics/nvidia-drm-latest-kmod-580/distinfo | 6 +++---
 x11/linux-nvidia-libs-580/Makefile           | 2 +-
 x11/linux-nvidia-libs-580/distinfo           | 6 +++---
 x11/nvidia-driver-580/Makefile               | 2 +-
 x11/nvidia-driver-580/distinfo               | 6 +++---
 x11/nvidia-kmod-580/Makefile                 | 2 +-
 16 files changed, 30 insertions(+), 30 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.