Page 1 of 1

Broadcom BCM57711 is not working properly (bnx2x module issue)

Posted: 2017/09/06 11:57:09
by iff
Hello

Seems that BCM57711 (bnx2x) is not working on Centos 7 (multiple bugs/misbehavior)

dmesg logs:

Code: Select all

[1627599.678381] bnx2x 0000:15:00.0 enp21s0f0: Parity errors detected in blocks:
[1627599.679062] TSEMI [0x00000000]  [0x00000004]
[1627599.679145] bnx2x 0000:15:00.1 enp21s0f1: Parity errors detected in blocks:
[1627599.679744] TSEMI [0x00000000]  [0x00000004]

kernel: bnx2x: [bnx2x_dcbnl_set_dcbx:2383(enp21s0f1)]Requested DCBX mode 5 is beyond advertised capabilities
kernel: bnx2x: [bnx2x_dcbnl_set_dcbx:2383(enp21s0f1)]Requested DCBX mode 5 is beyond advertised capabilities
After any of these errors NIC goes down and up.

Disabling LLDP on switch (tx/rx) helps resolve DCBX issue
Disabling LRO(GRO) helps bring speed on nic from 1Kbit to 10G (module option disable_tpa=1)
But seems that vxlan activity cause "Parity errors" errors and we dont know what to do with it.
Ubuntu guys seems to have similar issue : https://bugs.launchpad.net/ubuntu/+sour ... ug/1643558


What we have :
Centos 7 (up to date)
Linux 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
15:00.0 Ethernet controller: Broadcom Limited NetXtreme II BCM57711 10-Gigabit PCIe
bnx2x driver 1.712.30-0

Any help would be appreciated!

Regards,
Aleksandr

Re: Broadcom BCM57711 is not working properly (bnx2x module issue)

Posted: 2018/10/11 14:36:38
by Jeffrey4l
has the same issue.

my env is:

centos7.5 + BCM57800,

i am using openshift + vxlan, when a vxlan packet is sent to the node, node is restarted automatically.

I also test the latest kernel (4.18.12), which still have the same issue.

i also tried to disable tso/gso/gro/tx-udp_tnl-segmentation/rx-udp_tunnel-port-offload/tx-udp_csum-segmentation, still do not work.

Re: Broadcom BCM57711 is not working properly (bnx2x module issue)

Posted: 2018/10/11 14:56:50
by TrevorH
If you tested the latest mainline kernel then it's likely you need to report the issue on the LKML. It might also be worth reporting it via bugzilla.redhat.com to get it fixed in the distro kernel but I think I'd do one thing at a time not both at once.