DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: vikram T <vikramet@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] BraodCom BNXT driver - Sample program crash DPDK - 18.11
Date: Wed, 7 Aug 2019 22:38:22 -0700	[thread overview]
Message-ID: <CACZ4nhs4X5nbF+rUANNNgtW=0gygGDEL=bAo+E93Ufhiicmdeg@mail.gmail.com> (raw)
In-Reply-To: <CANxYRjywvyfvvNMLBnOgiuttwWNca9rGcni7sMMFs2QaR2rssQ@mail.gmail.com>

You seem to be having an older version of firmware on the card.
I will have someone contact you for the newer firmware.

Thanks
Ajit

On Wed, Aug 7, 2019 at 10:19 PM vikram T <vikramet@gmail.com> wrote:

> Hi,
> I am trying to run the sample program "hello_world" using the DPDK - 18.11
> version on Braodcom BNXT driver the crash is seen:
>
> [root@localhost build]# ./helloworld
> EAL: Detected 48 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Probing VFIO support...
> EAL: PCI device 0000:02:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:1533 net_e1000_igb
> EAL: PCI device 0000:18:00.0 on NUMA socket 0
> EAL:   probe driver: 14e4:16d9 net_bnxt
> bnxt_dev_init(): Broadcom NetXtreme driver bnxt
>
> bnxt_hwrm_ver_get(): 1.8.3:20.8.156
> bnxt_hwrm_ver_get(): Driver HWRM version: 1.9.2
> __bnxt_hwrm_func_qcaps(): PTP SUPPORTED
> bnxt_hwrm_func_resc_qcaps(): error 65535:0:00000000:0000
> bnxt_dev_init(): hwrm query capability failure rc: ffffffea
> Segmentation fault
>
> The same crash is also seen on DPDK-19.05 version.
> However with DPDK-17.05 version the sample program runs perfectly fine.
>
> Below is the output of dpdk-devbind.py -s
>
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:18:00.0 'BCM57417 NetXtreme-E 10GBASE-T RDMA Ethernet Controller 16d9'
> drv=igb_uio unused=
>
> Network devices using kernel driver
> ===================================
> 0000:02:00.0 'I210 Gigabit Network Connection 1533' if=eno1 drv=igb
> unused=igb_uio *Active*
> 0000:18:00.1 'BCM57417 NetXtreme-E 10GBASE-T RDMA Ethernet Controller 16d9'
> if=eno3d1 drv=bnxt_en unused=igb_uio
> 0000:3b:00.0 'Ethernet Controller X710/X557-AT 10GBASE-T 1589' if=enp59s0f0
> drv=i40e unused=igb_uio
> 0000:3b:00.1 'Ethernet Controller X710/X557-AT 10GBASE-T 1589' if=enp59s0f1
> drv=i40e unused=igb_uio
> 0000:3b:00.2 'Ethernet Controller X710/X557-AT 10GBASE-T 1589' if=enp59s0f2
> drv=i40e unused=igb_uio
> 0000:3b:00.3 'Ethernet Controller X710/X557-AT 10GBASE-T 1589' if=enp59s0f3
> drv=i40e unused=igb_uio
> 0000:af:00.0 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=enp175s0f0
> drv=i40e unused=igb_uio
> 0000:af:00.1 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=enp175s0f1
> drv=i40e unused=igb_uio
> 0000:af:00.2 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=enp175s0f2
> drv=i40e unused=igb_uio
> 0000:af:00.3 'Ethernet Controller XL710 for 40GbE QSFP+ 1583' if=enp175s0f3
> drv=i40e unused=igb_uio
>
> Can you help to find the reason for the crash.
>
> Regards,
> Vikram
>

      reply	other threads:[~2019-08-08  5:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  5:19 vikram T
2019-08-08  5:38 ` Ajit Khaparde [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CACZ4nhs4X5nbF+rUANNNgtW=0gygGDEL=bAo+E93Ufhiicmdeg@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=vikramet@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).