Bug 1958005
| Summary: | [RFE] Identify the i40e driver version to use with RHOSP16.1 and RHEL8.2 for SR-IOV | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Cristian Muresanu <cmuresan> |
| Component: | openstack-neutron | Assignee: | OSP Team <rhos-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Eran Kuris <ekuris> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16.1 (Train) | CC: | ccamposr, chrisw, cmayapka, cmuresan, eng-rhn, gurpsing, mtomaska, sassmann, scohen |
| Target Milestone: | --- | Keywords: | FutureFeature |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-26 17:40:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Cristian Muresanu
2021-05-07 01:22:48 UTC
Upstream linux no longer reports a i40e driver version. It is confusing an misleading because there is no relation between the upstream i40e version and Intels sourceforge driver version. They are 2 different drivers that cannot be compared easily.
in RHEL8.4 the driver version changed to report the UTS_RELEASE version instead.
Here's the corresponding upstream commit info.
commit 34a2a3b83e2caf18ab85627f9c6a78bc0a1d1520
Author: Jeff Kirsher <jeffrey.t.kirsher>
Date: Fri May 29 00:18:33 2020 -0700
net/intel: remove driver versions from Intel drivers
As with other networking drivers, remove the unnecessary driver version
from the Intel drivers. The ethtool driver information and module version
will then report the kernel version instead.
For ixgbe, i40e and ice drivers, the driver passes the driver version to
the firmware to confirm that we are up and running. So we now pass the
value of UTS_RELEASE to the firmware. This adminq call is required per
the HAS document. The Device then sends an indication to the BMC that the
PF driver is present. This is done using Host NC Driver Status Indication
in NC-SI Get Link command or via the Host Network Controller Driver Status
Change AEN.
What the BMC may do with this information is implementation-dependent, but
this is a standard NC-SI 1.1 command we honor per the HAS.
Hi Redhat Team, How to should I check i40e version for RHEL 9.0 and RHOPS 17.1. we are seeing VF driver issue when initializing the drivers, do we have any issues around this - Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: TX driver issue detected on VF 57 Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: Use PF Control I/F to re-enable the VF Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: TX driver issue detected on VF 57 Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: Use PF Control I/F to re-enable the VF This is also seen in RHEL 8.2 and RHOSP 16.1 Please let me know. (In reply to eng-rhn from comment #6) > Hi Redhat Team, > > > How to should I check i40e version for RHEL 9.0 and RHOPS 17.1. > we are seeing VF driver issue when initializing the drivers, do we have any > issues around this - > Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: TX driver issue > detected on VF 57 > Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: Use PF Control I/F to > re-enable the VF > Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: TX driver issue > detected on VF 57 > Sep 18 23:58:30 standalone kernel: i40e 0000:11:00.0: Use PF Control I/F to > re-enable the VF > > This is also seen in RHEL 8.2 and RHOSP 16.1 > Please let me know. Can you open a separate issue for the problem you are describing? Or maybe its similar to this one [1]? [1] https://bugzilla.redhat.com/show_bug.cgi?id=2224236 closing this RFE as low priority. Feel free to reopen if there is some current case behind it. The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |