MantisBT - Issues

0000619: System Health Check

Thu, 09 Apr 2026 20:08:51 +0000

Automated verification report

0000618: [AlmaLinux][Mana][Backport] P0] Rx CQE coalescing Feature

Wed, 08 Apr 2026 00:29:03 +0000

Request backport of the following patches

kernel Space
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d01440e10a82cae2c4a28c76e46e6a8b94b27a84
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=c2fe3ff3d66d6f53ec5857c277fae5b3ff9881c1
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=dc3d720e12f602059490c1ab2bfee84a7465998f

UserSpace
https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?h=next&id=d35d87fbcda97fe31df79d62277743214641892a
https://git.kernel.org/pub/scm/network/ethtool/ethtool.git/commit/?h=next&id=bf023af442f63e16f1699128c7ce467eddc6d340

0000617: h5pfc script uses incorrect `includedir` for OpenMPI on AlmaLinux 10

Sat, 28 Mar 2026 20:00:12 +0000

After installing parallel HDF5 via `dnf install hdf5-openmpi`, the `h5pfc` compiler wrapper fails due to an incorrect include directory.

File affected:
`/usr/lib64/openmpi/bin/h5pfc`

The script defines an `includedir` that does not point to the correct location of OpenMPI Fortran modules, causing compilation failures for parallel HDF5 Fortran programs.

**System:**

* OS: AlmaLinux 10
* Architecture: x86_64

**Package Information:**
(Output of `rpm -qi hdf5-openmpi`)

```
Name : hdf5-openmpi
Version : 1.14.5
Release : 1.el10_0
Architecture: x86_64
Install Date: Thu 26 Mar 2026 12:10:19 PM EDT
Group : Unspecified
Size : 7476900
License : BSD-3-Clause
Signature :
RSA/SHA256, Thu 24 Oct 2024 11:50:21 AM EDT, Key ID 33d98517e37ed158
Source RPM : hdf5-1.14.5-1.el10_0.src.rpm
Build Date : Thu 24 Oct 2024 09:51:10 AM EDT
Build Host : buildvm-x86-09.iad2.fedoraproject.org
Packager : Fedora Project
Vendor : Fedora Project
URL : https://www.hdfgroup.org/solutions/hdf5/
Bug URL : https://bugz.fedoraproject.org/hdf5
Summary : HDF5 openmpi libraries
Description :
HDF5 parallel openmpi libraries
```

**mpifort configuration:**
(Output of `mpifort --showme`)

```
gfortran -I/usr/include/openmpi-x86_64 -I/usr/lib64/openmpi/lib -L/usr/lib64/openmpi/lib -Wl,-rpath -Wl,/usr/lib64/openmpi/lib -Wl,--enable-new-dtags -lmpi_usempif08 -lmpi_usempi_ignore_tkr -lmpi_mpifh -lmpi
```

**Problem:**
The `includedir` in `h5pfc` does not match the actual OpenMPI module include path used by the system compiler toolchain.

**Fix / Workaround:**
Manually editing the script resolves the issue:

```bash
sudo nano /usr/lib64/openmpi/bin/h5pfc
```

Change:

```bash
includedir="..."
```

To:

```bash
includedir="/usr/lib64/gfortran/modules/openmpi/"
```

After this change, `h5pfc` works correctly and parallel HDF5 Fortran programs compile successfully.

**Expected behavior:**
`h5pfc` should automatically use the correct OpenMPI Fortran module include path without requiring manual modification.

**Actual behavior:**
Compilation fails unless the script is manually edited.

**Additional notes:**
The correct include paths appear to be consistent with the output of `mpifort --showme`, suggesting a mismatch between the HDF5 wrapper configuration and the OpenMPI toolchain configuration.

0000579: Dependency for perl-DBD-MySQL-4.053-1.el9.x86_64 ignores MariaDB Installation

Fri, 27 Mar 2026 21:21:35 +0000

The package perl-DBD-MySQL-4.053-1.el9.x86_64 attempts to install the MySQL (Oracle) version of dependencies instead of relying upon the MariaDB common/libs
=============================================================================================================================================
Error: Transaction test error:
file /usr/share/mysql/charsets/Index.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/armscii8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/ascii.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp1250.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp1251.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp1256.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp1257.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp850.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp852.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/cp866.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/dec8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/geostd8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/greek.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/hebrew.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/hp8.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/keybcs2.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/koi8r.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/koi8u.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/latin1.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/latin2.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/latin5.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/latin7.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/macce.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/macroman.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64
file /usr/share/mysql/charsets/swe7.xml from install of mysql-common-8.0.43-1.el9_6.x86_64 conflicts with file from package MariaDB-common-10.11.15-1.el9.x86_64

0000616: Latest grub2-efi-aa64 update fails to boot the system

Wed, 25 Mar 2026 00:06:21 +0000

The latest grub2-efi-aa64 patch to address CVE-2025-61662 updates grubaa64.efi under /boot/efi/EFI/almalinux results in

Synchronous Exception at 0xXXXXXXXXX

during boot up.

Reproduced in my installation of Almalinux 10.x running inside UTM in a MacBook Pro M4.

0000615: Linux reports optimal_io_size of 16776704 causing LVM data alignment inconsistency

Thu, 19 Mar 2026 10:23:47 +0000

Hi,

I've been noticing LVM alignment inconsistencies and performance issues with SAS HDDs. I found out that sysfs is reporting 16776704 optimal_io_size even though the Disks' VPD does not report maximum transfer length.
LVM is using this value to set the first physical extent of the physical volume. This does not align with the sector size of the disks of 4096 KB. I had to disable data alignment detection of LVM as a workaround.

The SAS controller within the machine is "Broadcom / LSI Fusion-MPT 12GSAS/PCIe Secure SAS38xx [1000:00e6]" and kernel is 5.14.0-570.28.1.el9_6.x86_64.

Thank you.

0000610: [AlmaLinux][Mana][Backport] net: mana: Fix use-after-free in reset service rescan path & net: mana: Fix double destroy_workqueue

Tue, 17 Mar 2026 17:09:57 +0000

Hi,
Request backport of the following patches on all active kernel versions. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=9bf66036d686b9a67000ba22bd94be13a4ea79ac
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=3387a7ad478b46970ae8254049167d166e398aeb
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=f975a0955276579e2176a134366ed586071c7c6a

Regards,
Sriram.

0000614: Kickstart installation crashes on package usbguard-selinux

Mon, 16 Mar 2026 18:59:14 +0000

Hello, running kickstart installation with AlmaLinux 10.1 iso, fails at installing package 'usbguard-selinux'.

0000613: gnome-remote-desktop not working depending on networking configuration

Mon, 16 Mar 2026 17:59:44 +0000

Hello, I'm using gnome-remote-desktop in AlmaLinux 10.1 (gnome 47).
I've applied the following instructions: https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/administering_rhel_by_using_the_gnome_desktop_environment/remotely-accessing-the-desktop
I'm using the "headless multiuser" scenario. (chapter 1.5)

It probably works for majority of people, but I've found that it fails every time when using isolated network, static ip address, no default gateway.

0000612: kvdo.ko is not compatible with 9.7 kernels

Mon, 16 Mar 2026 16:43:12 +0000

# echo /lib/modules/5.14.0-611.5.1.el9_7.x86_64/extra/kmod-kvdo/vdo/kvdo.ko | weak-modules --dry-run --add-modules --verbose
Module kvdo.ko from kernel 5.14.0-611.5.1.el9_7.x86_64 is not compatible with kernel 5.14.0-611.34.1.el9_7.x86_64 in symbols: dm_noflush_suspending dm_put_device dm_device_name dm_unregister_target dm_set_target_max_io_len dm_disk dm_register_target dm_table_get_mode dm_table_get_md dm_get_device
Falling back weak-modules state for kernel 5.14.0-611.34.1.el9_7.x86_64
Module kvdo.ko from kernel 5.14.0-611.5.1.el9_7.x86_64 is not compatible with kernel 5.14.0-611.36.1.el9_7.x86_64 in symbols: dm_noflush_suspending dm_put_device dm_device_name dm_unregister_target dm_set_target_max_io_len dm_disk dm_register_target dm_table_get_mode dm_table_get_md dm_get_device
Falling back weak-modules state for kernel 5.14.0-611.36.1.el9_7.x86_64
Module kvdo.ko from kernel 5.14.0-611.5.1.el9_7.x86_64 is not compatible with kernel 5.14.0-611.38.1.el9_7.x86_64 in symbols: dm_noflush_suspending dm_put_device dm_device_name dm_unregister_target dm_set_target_max_io_len dm_disk dm_register_target dm_table_get_mode dm_table_get_md dm_get_device
Falling back weak-modules state for kernel 5.14.0-611.38.1.el9_7.x86_64
Skipping depmod for non-installed kernel 5.14.0-611.5.1.el9_7.x86_64

0000611: [AlmaLinux][Mana][Backport] net: mana: Trigger VF reset/recovery on health check failure due to HWC timeout

Thu, 12 Mar 2026 14:01:09 +0000

0000609: akmods rebuilds nvidia kmod on every boot on x86_64_v2 — weak-updates directory not RPM-owned

Mon, 09 Mar 2026 06:36:52 +0000

On AlmaLinux 10 x86_64_v2, akmods rebuilds the nvidia kmod from source on
every boot (0000017:0000020 seconds delay) despite the module being correctly installed
and functional.

Root cause: The check_kmod_up2date function in akmods uses:
rpm -qf "/lib/modules/${kernelver}/extra/${kmodname}/"
to verify the installed kmod package.

On x86_64_v2, the kmod RPM (kmod-nvidia-6.12.0-124.el10_1-580.95.05-1.el10.x86_64_v2)
only installs files into the kernel it was built for:
/lib/modules/6.12.0-124.13.1.el10_1.x86_64_v2/extra/nvidia/

For newer kernels, weak-modules creates symlinks in:
/lib/modules/6.12.0-124.38.1.el10_1.x86_64_v2/weak-updates/nvidia/

However the extra/nvidia/ directory for the newer kernel is NOT owned by
any RPM package — it is created by akmods itself during the rebuild.
Therefore rpm -qf returns "not owned by any package", version comparison
fails, and akmods triggers a full rebuild every boot.

The rebuild completes successfully but installs nothing new since the
package is already installed — confirmed by DNF output:
"Package already installed. Nothing to do."

This is a packaging bug specific to x86_64_v2 — the kmod RPM does not
include weak-updates entries or extra/ directories for kernels beyond
the one it was built against, and akmods does not check weak-updates
paths during its up-to-date verification.

Workaround applied:
sudo systemctl edit akmods.service

[Service]
ExecStart=
ExecStart=/bin/bash -c 'modinfo nvidia -k $(uname -r) -n 2>/dev/null | grep -q "nvidia.ko" && exit 0 || exec /usr/sbin/akmods --from-init'

This replaces the broken version check with a direct modinfo query,
skipping the rebuild when the module is already available for the
running kernel regardless of installation path.

0000608: Possible CC of "Compile bug: internal compiler error: Segmentation fault #20083"

Fri, 06 Mar 2026 13:59:10 +0000

Almalinux 10.1 on ppc64le (IBM Power 10) - Attempting to build llama.cpp fails with Internal Compiler Error.

May be similar to https://github.com/ggml-org/llama.cpp/issues/20083

0000606: Anaconda rejects x86_64_v2 ISO on x86_64-v3 systems - "Error setting up repositories"

Sat, 21 Feb 2026 22:45:51 +0000

When booting the AlmaLinux 10.1 x86_64_v2 DVD ISO on an x86_64 system, anaconda fails to set up the installation source with "Error setting up repositories".

Root cause: The .discinfo file on the ISO contains "x86_64_v2" as the architecture, but anaconda's is_valid_install_disk() function in pyanaconda/modules/payloads/source/utils.py performs a strict equality check against blivet.arch.get_arch() which returns "x86_64". The check fails, causing anaconda to reject the valid installation media.

The same issue affects _find_first_iso_image() in the same file.

x86_64_v2 is a microarchitecture level of x86_64, not a different architecture. Systems running x86_64_v2 code still report as x86_64 via uname.

0000607: [AlmaLinux][Mana_IB][RDMA][Backport] RDMA/mana_ib: Take CQ type from the device type P1

Mon, 02 Feb 2026 07:31:08 +0000

Hi,

Request backport of the following task. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git/commit/drivers/infiniband/hw/mana?id=f972bde7326e9cd3498c137a052f2034f975ebae

0000605: [AlmaLinux]{hv_netvsc][Backport] net: hv_netvsc: reject RSS hash key programming without RX indirection table

Thu, 29 Jan 2026 13:41:08 +0000

Request backport of the following patch..

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=d23564955811

0000604: [AlmaLinux][Mana][Backport] net: mana: Implement ndo_tx_timeout and serialize queue resets per port.

Thu, 29 Jan 2026 13:07:17 +0000

Hi,

Request backport of the following patch to all active kernel versions. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=3b194343c250

0000603: [AlmaLinux][MANA][Backport] [GB200] Backport patch for handling device slow probe on GB200

Thu, 29 Jan 2026 11:53:41 +0000

Request backport of the following patch.

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=9bf66036d686b9a67000ba22bd94be13a4ea79ac

0000602: [AlmaLinux][storvsc][Backport] Backport storvsc patch for handling MODE_SENSE_10

Tue, 27 Jan 2026 06:29:49 +0000

Hi,
Customer Reported issue. Need backport of the patch on priority for active alma versions. Thanks.

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/scsi/storvsc_drv.c?h=v6.19-rc7&id=9eacec5d18f98f89be520eeeef4b377acee3e4b8

This is a critical fix to storvsc. It fixes VM hung on starting up when the VM is initializing a disk and host may return unsupported results for MODE_SENSE_10.

0000594: Alma 10.1 rdp install broken

Wed, 21 Jan 2026 04:14:05 +0000

I tried to install alma 10.1 via pxe or boot.iso under legacy bios and uefi. I tried under kvm-vm and dell physical server.
boot.iso md5sum is "11d14e7e80f243e1e10d99a6c5bda92b"

rdp install parameter like “inst.rdp inst.rdp.username=userxxx inst.rdp.password=passxxx” failed.

rdp installation is important for EL10, because many Dell/HP/Lenovo server BMC with matrox g200 has no wayland support. so gui installation is not possible without rdp.

RHEL 10.1 rdp installation works fine.

tail /tmp/syslog I got the error message below:

ERR gnome-remote-desktop:[14:02:01:259] [3286:00000e4f] [WARN][com.freerdp.core.peer] - [peer_unexpected_client_message]: Unexpected client message in state CONNECTION_STATE_FINALIZATION_FONT_LIST, missing flag FINALIZE_CS_FONT_LIST_PDU [0x00000100]
14:02:01,301 NOTICE gnome-remote-de:[RDP.CLIPRDR] Client capabilities: long format names, stream file clip, file clip no file paths, can lock clip data, huge file support
14:02:01,308 WARNING gnome-remote-de:Failed to start screen cast stream: GDBus.Error:org.freedesktop.DBus.Error.Failed: Failed to start stream: Couldn't connect pipewire context
14:02:01,308 ERR gnome-remote-desktop:[14:02:01:294] [3286:00000cd6] [ERROR][com.freerdp.core.peer] - [rdp_set_error_info]: ERRINFO_RPC_INITIATED_DISCONNECT [0x00010001]

0000601: [AlmaLinux][hv_netvsc][Distros][Backport][GB200] hv_netvsc module reload fails for ARM64 SKUs

Fri, 16 Jan 2026 15:59:54 +0000

Request backport of the following patches for all current kernel versions.

bee35b7161aa RDMA/mana_ib: Handle net event for pointing to the current netdev
a8445cfec101 net: mana: Change the function signature of mana_get_primary_netdev_rcu

0000600: Set minor version in `kickstart` repo's `.treeinfo`

Fri, 16 Jan 2026 14:25:26 +0000

With the kickstart tree's content frozen on release, it would be helpful if the `.treeinfo` included the minor release in the version.

This would permit content republication tools (like katello/RedHat Satellite) to correctly identify installation trees for matching install media.

Folks doing less advanced caching would also benefit from the file containing a clear identification of the tree.

No change to the `os` .treeinfo should be made. That should still have no minor verision information.

I'd love to see this in both 9 and 10.

0000591: Golang is compiled for v3 instructions support / Almalinux 10 x86-64-v2

Fri, 09 Jan 2026 06:32:16 +0000

Golang package build on Almalinux 10 x86-64-v2 release is not able to execute:
"This program can only be run on AMD64 processors with v3 microarchitecture support."

Also reported here by a user: https://forums.almalinux.org/t/golang-x86-64-v2-requires-v3/6841

0000599: [nvidia] Have dashvariant also provide non-dash names.

Tue, 06 Jan 2026 18:38:04 +0000

The 64k stack kernel for aarch64 appears to be missing a provides on the non-dashvariant name. This blocks install of cuda.

0000598: rpm missing in initrd 10.1

Tue, 06 Jan 2026 08:38:02 +0000

When starting an anaconda kickstart install no "rpm" command is in iniitrd :

- rpm is missing

Why is this of high importance (for me):

I use rpm / dnf to install packages before kickstart runs.
For example:

- support better luks passwords / python3-xkcdpass and clevis-luks,