hi, I used the GDB the l2fwd for debug, and found the errors like this:
DPDK log error is :
MD: bnx2x_link_report(): NIC Link is Up, 10000 Mbps full duplex, Flow control:
ON - receive & transmit
PMD: bnx2x_interrupt_action(): Interrupt handled
PMD: bnx2x_attn_int_deasserted2(): PXP2_REG_PXP2_INT_STS_CLR_0 0x00000080
PMD: bnx2x_attn_int_deasserted2(): PXP2_WR_PGLUE_EOP_ERROR
PMD: bnx2x_attn_int_deasserted2(): FATAL HW block attention set2 0x20
PANIC in bnx2x_attn_int_deasserted2():
and the bt :
(gdb) bt
#0 0x00007ffff6f111d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x00007ffff6f128c8 in __GI_abort () at abort.c:90
#2 0x00000000004a4c58 in __rte_panic (funcname=0x93ef30 <__func__.18256>
"bnx2x_attn_int_deasserted2", format=0x93c1f7 "HW block attention set2%.0s")
at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_debug.c:90
#3 0x00000000005082bd in bnx2x_attn_int_deasserted2 (sc=0x7ffd73dc89c0,
attn=32) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:3978
#4 0x0000000000508753 in bnx2x_attn_int_deasserted (sc=0x7ffd73dc89c0,
deasserted=1) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4097
#5 0x00000000005089cc in bnx2x_attn_int (sc=0x7ffd73dc89c0) at
/home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4167
#6 0x0000000000509360 in bnx2x_handle_sp_tq (sc=0x7ffd73dc89c0) at
/home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4462
#7 0x00000000005095f4 in bnx2x_intr_legacy (sc=0x7ffd73dc89c0, scan_fp=0) at
/home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x.c:4556
#8 0x000000000053579d in bnx2x_interrupt_action (dev=0xc7e100
<rte_eth_devices>) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x_ethdev.c:111
#9 0x0000000000535854 in bnx2x_interrupt_handler (param=0xc7e100
<rte_eth_devices>) at /home/dpdk-17.05.2/drivers/net/bnx2x/bnx2x_ethdev.c:128
#10 0x00000000004a6469 in eal_intr_process_interrupts (events=0x7ffff66d9cf0,
nfds=1) at /home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:747
#11 0x00000000004a65de in eal_intr_handle_interrupts (pfd=16, totalfds=2) at
/home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:794
#12 0x00000000004a675a in eal_intr_thread_main (arg=0x0) at
/home/dpdk-17.05.2/lib/librte_eal/linuxapp/eal/eal_interrupts.c:864
#13 0x00007ffff72a4dc5 in start_thread (arg=0x7ffff66da700) at
pthread_create.c:308
#14 0x00007ffff6fd373d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:113
Does this mean ,the is the NIC driver's problem?
在 2017-11-09 20:46:37，"Flavio Leitner" <[email protected]> 写道：
>On Thu, 9 Nov 2017 18:07:05 +0800 (CST)
>王嵘 <[email protected]> wrote:
>
>> hi,
>> I rpmbuild the ovs-dpdk by myself, and the "config/common_base" :
>> CONFIG_RTE_LIBRTE_BNX2X_PMD=y
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG=y
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_INIT=y
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_RX=y
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_TX=y
>> CONFIG_RTE_LIBRTE_BNX2X_MF_SUPPORT=y
>> CONFIG_RTE_LIBRTE_BNX2X_DEBUG_PERIODIC=y
>>
>> then ,I build the rpm of dpdk/dpdk-devel，and installed the 2 rpms to
>> rpmbuild the ovs-dpdk。
>> when I used the ovs-dpdk with the bcm-NIC, there comes the error：
>>
>> here is the error in "/var/log/openvswitch/ovs-vswitchd.log"
>> 2017-11-09T09:28:30.038Z|16773336|dpdk|INFO|EAL: PCI device 0000:20:00.1 on
>> NUMA socket 0
>> 2017-11-09T09:28:30.038Z|16773337|dpdk|INFO|EAL: probe driver: 14e4:168e
>> net_bnx2x
>> 2017-11-09T09:28:30.038Z|16773338|dpdk|WARN|EAL: Requested device
>> 0000:20:00.1 cannot be used
>> 2017-11-09T09:28:30.038Z|16773339|dpdk|ERR|EAL: Driver cannot attach the
>> device (0000:20:00.1)
>> 2017-11-09T09:28:30.038Z|16773340|netdev_dpdk|WARN|Error attaching device
>> '0000:20:00.1' to DPDK
>> 2017-11-09T09:28:30.038Z|16773341|netdev|WARN|dpdk-eth2: could not set
>> configuration (Invalid argument)
>
>
>Looks like DPDK has the pmd enabled and has identified the device.
>Did you bind the NIC to the VFIO driver before start OVS?
>
>
>> And, my NIC firmware is :
>> [root@node-4 ~]# ethtool -i eth2
>> driver: bnx2x
>> version: 1.712.30-0
>> firmware-version: bc 7.0.49
>> expansion-rom-version:
>> bus-info: 0000:20:00.1
>> supports-statistics: yes
>> supports-test: yes
>> supports-eeprom-access: yes
>> supports-register-dump: yes
>> supports-priv-flags: yes
>>
>>
>> Does the fm version not satisfies ? or some other reasons ?
>
>I don't know about FW versions.
>fbl
>
>
>>
>>
>>
>>
>>
>>
>> 在 2017-11-08 21:28:01，"Flavio Leitner" <[email protected]> 写道：
>> >On Wed, 8 Nov 2017 11:15:00 +0800 (CST)
>> >王嵘 <[email protected]> wrote:
>> >
>> >> For now, I 'm using the "NetXtreme II BCM57810 10 Gigabit Ethernet 168e".
>> >> Another question, I found ovs-dpdk can't bind this NIC. But I find
>> >> there is the support code for 57810 in the DPDK Bnx2x.
>> >> I'm puzzled.
>> >> Can you tell me whether ovs-dpdk support this NIC?
>> >>
>> >> Thanks very much!
>> >
>> >You need to check that with your software provider. If you compiled
>> >manually, then you need to check the options/config used to build DPDK.
>> >
>> >fbl
>> >
>> >
>> >> 在 2017-11-08 09:11:25，"Ben Pfaff" <[email protected]> 写道：
>> >> >On Tue, Nov 07, 2017 at 03:49:06PM +0800, 王嵘 wrote:
>> >> >> Hi,
>> >> >> I'm using ovs-dpdk（ovs2.8/dpdk17.05.2), and I want to use the offload
>> >> >> feature. But I dont know how to enable it?
>> >> >> As is represented in the release note 2.8:
>> >> >>
>> >> >> - Addexperimental support for hardware offloading
>> >> >> * HW offloading is disabled by default.
>> >> >>
>> >> >> * HW offloading is done through the TC interface.
>> >> >
>> >> >Do you have a supported NIC? This feature is currently for a particular
>> >> >model of Mellanox NICs.
>> >
>> >
>> >
>> >--
>> >Flavio
>> >
>
>
>
>--
>Flavio
>
_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
