Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi Manish,
What version will the FW be? Any specific test needs to be done besides confirming the correct FW version is included in linux-firmware? Thanks.
Comment 3Manish Chopra (Marvell)
2019-11-11 11:26:05 UTC
Hi,
We need to take below FW commit from linux-firmware.git
commit 0acd93ea00e8b1b0411063f2391da0d4a52ebaf0
Author: Sudarsana Reddy Kalluru <skalluru>
Date: Tue Oct 22 07:01:54 2019 -0700
bnx2x: Add FW 7.13.15.0.
This patch adds new FW for bnx2x, which addresses the following issues:
- TCP packet with padding can open TPA aggregation in GRO mode.
- Tx Silent Drops could cause HW error when statistics is not enabled for client.
- Transmission of tunneled packets over tx-only clients (with cos>0 in this case) followed by load/unload with DCB update (for instance), resulted in a Tx path halt.
- FORWARD_SETUP ramrod yielded a FW assert (x_eth_fp_hsi_ver_invalid).
The FW also adds support for direct update of RSS indirection table entry.
Signed-off-by: Sudarsana Reddy Kalluru <skalluru>
Signed-off-by: Ameen Rahman <arahman>
Signed-off-by: Josh Boyer <jwboyer>
We will be posting corresponding driver changes to use this FW soon.
Thanks,
Manish
Comment 4Manish Chopra (Marvell)
2019-11-11 11:52:28 UTC
For some reason, I am not able to set depends on/blocked.
This BZ blocks BZ #1770797.
Thanks,
Manish
Comment 5Manish Chopra (Marvell)
2019-11-12 13:53:03 UTC
Note that patches has been posted for BZ #1770797
Phillip/Don,
Please make sure that above firmware gets pulled in on which bnx2x driver will have dependency (from BZ #1770797).
Thanks,
Manish
Comment 6Manish Chopra (Marvell)
2019-11-12 13:55:35 UTC
+ John
John, please check if this BZ requires any flags etc. to be set appropriately.
Thanks,
Manish
Hi Manish,
Just want to make sure, if the following info shows that the bnx2x NIC is using 7.13.15.0 firmware and the regression tests on the NIC is valid for verification.
$ ethtool -i ens3f0
driver: bnx2x
version: 1.713.36-0 storm 7.13.15.0
firmware-version: 5.0.12 bc 5.0.13 phy aa0.406
expansion-rom-version:
bus-info: 0000:5e:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
Regards,
Tianhao
There is no response from partner. The bnx2x is using 7.13.15.0 version of firmware through 'ethtool -i' result, from my perspective.
$ ethtool -i ens3f0
driver: bnx2x
version: 1.713.36-0 storm 7.13.15.0
firmware-version: 5.0.12 bc 5.0.13 phy aa0.406
expansion-rom-version:
bus-info: 0000:5e:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
I have finished the nic basic functional testing with kernel-4.18.0-167.el8 on bnx2x driver, details as below:
Test items include:
layered-protocol: pass
sanity_check(ip/mac/broadcast/multicast/almulti/mtu/promisc/selftest): pass
Card recognize: pass
basic traffic(ping and netperf): pass
statistics in /proc/net/dev: partly pass
ring buffer setting: pass
driver load and unload: pass
coalesce setting: pass
multiqueue: pass
pause: pass
offload: pass
scaling: pass
link_check: pass
vlan/tier1: pass
bridge/stp_test,sanity_check: pass
The bnx2x NIC is using 7.13.15.0 version on 167 kernel. No other regression has been found, set verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:1887