Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: mstflint -d 04:00.0 q Segmentation fault (core dumped) mstflint -d 04:00.0 q Version-Release number of selected component (if applicable): mstflint --version mstflint, mstflint 4.32.0, Git SHA Hash: N/A How reproducible: 100% Steps to Reproduce: 1. install connectx-3 pro networkcard 2. run mstflint to query it 3. result Actual results: segfault Expected results: firmware version output Additional info: I dunno if 4.35 fixes things for me, i built it and installed in local but at least it didn't segfault - instead it gave me: stflint -d 04:00.0 q FATAL - crspace read (0xf0014) failed: Invalid argument FATAL - crspace read (0xf0014) failed: Invalid argument -E- Cannot open Device: 04:00.0. Invalid argument. MFE_GENERAL_ERROR (even with setenforce 0)
*** Bug 2445761 has been marked as a duplicate of this bug. ***
There's an upstream bug report about it: https://github.com/Mellanox/mstflint/issues/1157 I proposed this as a fix: https://github.com/Mellanox/mstflint/pull/1831 Nvidia considers the ConnectX-3 an end-of-life product, so they're unlikely to spend effort on fixing issues related to it.
I'm not waiting for upstream to respond. It's a small patch. We will carry it as a patch in the Fedora package for now.
FEDORA-2026-ab32330643 (mstflint-4.36.0-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-ab32330643
FEDORA-2026-ab32330643 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ab32330643` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ab32330643 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-ab32330643 (mstflint-4.36.0-2.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.