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.

Description of problem:

RHEL 6.2 seems to have a regression in the bnx2x driver, or perhaps the problem was never fixed. The problem I'm having is described here:

https://access.redhat.com/knowledge/ja/node/47669

I'm using the following hardware:

Broadcom Corporation NetXtreme II BCM57711 10-Gigabit PCIe

When I attempt to insmod the bnx2x driver I get this in dmesg:

===
bnx2x: [bnx2x_leader_reset:9755(eth2)]Something bad had happen on engine 0! Aii!
bnx2x: [bnx2x_open:12067(eth2)]Recovery flow hasn't been properly completed yet. Try again later.
If you still see this message after a few retries then power cycle is required.
===

Version-Release number of selected component (if applicable):

RHEL 6.2, x86_64

How to reproduce:

1. Build system running RHEL 6.2 with one of these adapters.

2. Download the latest netxtrem2 package. I've tried both of these, the first from Redhat, the second directly from Broadcom:

netxtreme2-7.0.36-1.x86_64.rpm
netxtreme2-7.2.20-1.x86_64.rpm

3. rmmod any existing bnx2x driver, insmod the new one.

4. Run dmesg, see the error above. Notice that the NIC is unusable. ethtool shows that there is no link, ifconfig doesn't list the device as "UP."

*** This bug has been marked as a duplicate of bug 836363 ***

I'm sorry, as a mere mortal I don't have access to this original bug 836363 - how can I get more details? 

two of my interfaces are failing like so on CentOS 6.x right now on a prod server in a faraway datacenter.. Can't even easily update linux/kernel as due to that I've lost internet connectivity because broadcom NIC doesn't initialize network. 

Interface works fine from Dell Lifecycle controller though.

How does one fix this? There is zero documentation on this, except for some ransomware answers.   What is the solution to this?

The driver and firmware changed a lot since this BZ was filed.
If you can reproduce it on a current release, file it as a new bug with relevant 
information attached (sosreport, steps to reproduce, output of dmesg with the issue reproduced).

I am having this issue on XenServer release 7.2.0 (xenenterprise), which I believe is based on RHEL 7.  Are there any known workarounds for this?