NIC - kernel messages flooding kern.log

[pdan]

Hello forum,

we are using 10Gb NICs from Allied Telesis model AT-VNC10S based on Broadcom BCM57711 chipset (bnx2x kernel module).
We are experiencing in these days an abnormal growth of kern.log with the following sequence repeated more or less the same every cicle:

Oct 27 08:38:55 c00 kernel: Call Trace:
Oct 27 08:38:55 c00 kernel: <IRQ>  [<ffffffff81073229>] ? add_taint+0x69/0x70
Oct 27 08:38:55 c00 kernel: [<ffffffff81073399>] ? warn_slowpath_common+0xa9/0xe0
Oct 27 08:38:55 c00 kernel: [<ffffffff81073486>] ? warn_slowpath_fmt+0x46/0x50
Oct 27 08:38:55 c00 kernel: [<ffffffff81559126>] ? skb_warn_bad_offload+0xbd/0xdd
Oct 27 08:38:55 c00 kernel: [<ffffffff8147ef01>] ? __skb_gso_segment+0x71/0xc0
Oct 27 08:38:55 c00 kernel: [<ffffffff8147ef63>] ? skb_gso_segment+0x13/0x20
Oct 27 08:38:55 c00 kernel: [<ffffffff8147f001>] ? dev_hard_start_xmit+0x91/0x5f0
Oct 27 08:38:55 c00 kernel: [<ffffffffa038290c>] ? bond_dev_queue_xmit+0x2c/0x50 [bonding]
Oct 27 08:38:55 c00 kernel: [<ffffffff8149dd7a>] ? sch_direct_xmit+0x16a/0x1d0
Oct 27 08:38:55 c00 kernel: [<ffffffff8147f848>] ? dev_queue_xmit+0x208/0x300
Oct 27 08:38:55 c00 kernel: [<ffffffff8151f130>] ? __br_forward+0x0/0xd0
Oct 27 08:38:55 c00 kernel: [<ffffffff8151ee3b>] ? br_dev_queue_push_xmit+0x7b/0xc0
Oct 27 08:38:55 c00 kernel: [<ffffffff8151eed8>] ? br_forward_finish+0x58/0x60
Oct 27 08:38:55 c00 kernel: [<ffffffff8151f130>] ? __br_forward+0x0/0xd0
Oct 27 08:38:55 c00 kernel: [<ffffffff8151f1db>] ? __br_forward+0xab/0xd0
Oct 27 08:38:55 c00 kernel: [<ffffffff8151f119>] ? br_flood+0xc9/0xe0
Oct 27 08:38:55 c00 kernel: [<ffffffff8151f47c>] ? br_flood_forward+0x1c/0x20
Oct 27 08:38:55 c00 kernel: [<ffffffff81520600>] ? br_handle_frame_finish+0x320/0x340
Oct 27 08:38:55 c00 kernel: [<ffffffff815207ca>] ? br_handle_frame+0x1aa/0x250
Oct 27 08:38:55 c00 kernel: [<ffffffff8147fc4f>] ? __netif_receive_skb+0x24f/0x770
Oct 27 08:38:55 c00 kernel: [<ffffffff814802b8>] ? netif_receive_skb+0x58/0x60
Oct 27 08:38:55 c00 kernel: [<ffffffff81185ce4>] ? alloc_pages_current+0xa4/0x110
Oct 27 08:38:55 c00 kernel: [<ffffffff814803d0>] ? napi_skb_finish+0x50/0x70
Oct 27 08:38:55 c00 kernel: [<ffffffff8152f10c>] ? vlan_gro_receive+0x8c/0xa0
Oct 27 08:38:55 c00 kernel: [<ffffffffa00ab70c>] ? bnx2x_rx_int+0xdcc/0x1520 [bnx2x]
Oct 27 08:38:55 c00 kernel: [<ffffffff8147192a>] ? consume_skb+0x3a/0x80
Oct 27 08:38:55 c00 kernel: [<ffffffff81290001>] ? pointer.isra.10+0x5b1/0xaa0
Oct 27 08:38:55 c00 kernel: [<ffffffffa00abf04>] ? bnx2x_poll+0xa4/0x2d0 [bnx2x]
Oct 27 08:38:55 c00 kernel: [<ffffffff810676a3>] ? try_to_wake_up+0xb3/0x490
Oct 27 08:38:55 c00 kernel: [<ffffffff81480d21>] ? net_rx_action+0x1a1/0x3b0
Oct 27 08:38:55 c00 kernel: [<ffffffff8107d23b>] ? __do_softirq+0x11b/0x260
Oct 27 08:38:55 c00 kernel: [<ffffffff8100c4cc>] ? call_softirq+0x1c/0x30
Oct 27 08:38:55 c00 kernel: [<ffffffff81010235>] ? do_softirq+0x75/0xb0
Oct 27 08:38:55 c00 kernel: [<ffffffff8107d515>] ? irq_exit+0xc5/0xd0
Oct 27 08:38:55 c00 kernel: [<ffffffff81563882>] ? do_IRQ+0x72/0xe0
Oct 27 08:38:55 c00 kernel: [<ffffffff8100bb13>] ? ret_from_intr+0x0/0x11
Oct 27 08:38:55 c00 kernel: <EOI>  [<ffffffff812e8e4b>] ? intel_idle+0xdb/0x160
Oct 27 08:38:55 c00 kernel: [<ffffffff812e8e29>] ? intel_idle+0xb9/0x160
Oct 27 08:38:55 c00 kernel: [<ffffffff81446614>] ? cpuidle_idle_call+0x94/0x130
Oct 27 08:38:55 c00 kernel: [<ffffffff81009219>] ? cpu_idle+0xa9/0x100
Oct 27 08:38:55 c00 kernel: [<ffffffff81535881>] ? rest_init+0x85/0x94
Oct 27 08:38:55 c00 kernel: [<ffffffff81c34ce1>] ? start_kernel+0x3ff/0x40b
Oct 27 08:38:55 c00 kernel: [<ffffffff81c3433b>] ? x86_64_start_reservations+0x126/0x12a
Oct 27 08:38:55 c00 kernel: [<ffffffff81c3444d>] ? x86_64_start_kernel+0x10e/0x11d

pveversion and lspci output follows:

root@c00:/var/log# lspci | grep -i ethernet
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
04:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
root@c00:/var/log# pveversion -v
proxmox-ve-2.6.32: 3.2-132 (running kernel: 2.6.32-31-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-15
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-19
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-23
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1
root@c00:/var/log#

Googling around leds to possible NIC module bug but I haven't found any workaround for now.
Had anyone experienced/solved similar issues?

Pasquale