dell r320 and Broadcom 57810 DP CNA with bnx2x driver

ioo

Renowned Member
Oct 1, 2011
23
0
66
Hi!

I am using Proxmox v. 3.4 with Dell R320 hardware + 10g dual port adapter 'Broadcom 57810 DP 10Gb DA/SFP+ Converged Network Adapter'. Whole system including 10g adapter seems to work all right with 2.6 kernel i am worried about these messages i get during bootup

..
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.0: irq 89 for MSI/MSI-X
Apr 14 10:12:12 proxmox-node1 kernel: alloc irq_desc for 90 on node 0
Apr 14 10:12:12 proxmox-node1 kernel: alloc kstat_irqs on node 0
Apr 14 10:12:12 proxmox-node1 kernel: alloc irq_2_iommu on node 0
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.0: irq 90 for MSI/MSI-X
Apr 14 10:12:12 proxmox-node1 kernel: ------------[ cut here ]------------
Apr 14 10:12:12 proxmox-node1 kernel: WARNING: at net/core/dev.c:6447 register_netdevice+0x233/0x490() (Not tainted)
Apr 14 10:12:12 proxmox-node1 kernel: Hardware name: PowerEdge R320
Apr 14 10:12:12 proxmox-node1 kernel: Modules linked in: ahci(+) tg3 megaraid_sas(+) ptp pps_core bnx2x(+) mdio
Apr 14 10:12:12 proxmox-node1 kernel: Pid: 428, comm: work_for_cpu veid: 0 Not tainted 2.6.32-37-pve #1
Apr 14 10:12:12 proxmox-node1 kernel: Call Trace:
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff81079697>] ? warn_slowpath_common+0x87/0xe0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8107970a>] ? warn_slowpath_null+0x1a/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff814887a3>] ? register_netdevice+0x233/0x490
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff81488a3f>] ? register_netdev+0x3f/0x60
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffffa0019630>] ? bnx2x_set_int_mode+0x30/0x160 [bnx2x]
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffffa007d2f1>] ? bnx2x_init_one+0x2dc9/0x30cb [bnx2x]
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8109e360>] ? do_work_for_cpu+0x0/0x30
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff812b6997>] ? local_pci_probe+0x17/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8109e378>] ? do_work_for_cpu+0x18/0x30
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff810a5fc0>] ? kthread+0x90/0xb0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8100c3ca>] ? child_rip+0xa/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff810a5f30>] ? kthread+0x0/0xb0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20
Apr 14 10:12:12 proxmox-node1 kernel: ---[ end trace 1e4936c367d0f5d2 ]---
Apr 14 10:12:12 proxmox-node1 kernel: Tainting kernel with flag 0x9
Apr 14 10:12:12 proxmox-node1 kernel: Pid: 428, comm: work_for_cpu veid: 0 Not tainted 2.6.32-37-pve #1
Apr 14 10:12:12 proxmox-node1 kernel: Call Trace:
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff81079549>] ? add_taint+0x69/0x70
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff810796b9>] ? warn_slowpath_common+0xa9/0xe0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8107970a>] ? warn_slowpath_null+0x1a/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff814887a3>] ? register_netdevice+0x233/0x490
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff81488a3f>] ? register_netdev+0x3f/0x60
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffffa0019630>] ? bnx2x_set_int_mode+0x30/0x160 [bnx2x]
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffffa007d2f1>] ? bnx2x_init_one+0x2dc9/0x30cb [bnx2x]
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8109e360>] ? do_work_for_cpu+0x0/0x30
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff812b6997>] ? local_pci_probe+0x17/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8109e378>] ? do_work_for_cpu+0x18/0x30
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff810a5fc0>] ? kthread+0x90/0xb0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8100c3ca>] ? child_rip+0xa/0x20
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff810a5f30>] ? kthread+0x0/0xb0
Apr 14 10:12:12 proxmox-node1 kernel: [<ffffffff8100c3c0>] ? child_rip+0x0/0x20
Apr 14 10:12:12 proxmox-node1 kernel: scsi3 : ahci
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.1: msix capability found
Apr 14 10:12:12 proxmox-node1 kernel: alloc irq_desc for 52 on node 0
Apr 14 10:12:12 proxmox-node1 kernel: alloc kstat_irqs on node 0
Apr 14 10:12:12 proxmox-node1 kernel: alloc irq_2_iommu on node 0
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.1: PCI INT B -> GSI 52 (level, low) -> IRQ 52
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.1: setting latency timer to 64
Apr 14 10:12:12 proxmox-node1 kernel: bnx2x 0000:08:00.1: part number 0-0-0-0
...
(and same for 08:00.1 device)

And more or less the same when i say

# rmmod bnx2x
# modprobe bnx2x

I tested the same server with Proxmox v. 3.10 kernel and there are not such messages and also 10g adapter is working.

At the moment i need only 10g ethernet functionality from this CNA adapter, for doing DRBD traffic between servers. Could you advise me please about these messages, should i load bnx2x driver with some options, ignore these messages or i'd rather use Promox v. 3.4 with 3.10 Linux kernel?


Best regards,

Imre

root@proxmox-node1:~# lspci | grep -i ether
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5720 Gigabit Ethernet PCIe
08:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
08:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!