From: nirmoy das <nirmoy.aiemd@gmail.com>
To: Nirmoy Das <ndas@suse.de>
Cc: "Patil, Harish" <Harish.Patil@cavium.com>,
"Mody, Rasesh" <Rasesh.Mody@cavium.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] bnx2x_init failed
Date: Thu, 25 Jan 2018 14:30:10 +0100 [thread overview]
Message-ID: <CAN6iQk+n=yVyU6mSD7hXyX7nwuQOKhScijpUMiFGz8_vKt=C7A@mail.gmail.com> (raw)
In-Reply-To: <5c32a66f-9605-7d1b-dedf-dddab94435b6@suse.de>
Hi Harish,
Do you need any other logs/info for this?
Regards,
Nirmoy
On Jan 17, 2018 11:18 AM, "Nirmoy Das" <ndas@suse.de> wrote:
> Hi Harish,
>
> kni example application.
>
> here's the command that fails.
> dpdk_example_kni -- -P -p 1 --config="(0,1,2,3)"
>
>
>
> Adding more details
>
> PCI devices for eth0 and eth1 remain bound to bnx2x driver
>
> 0000.04:00.0 eth0
> 0000.04:00.1 eth1
>
> The rest are bound to igb_uio driver
>
> 0000.04:00.2
> [...]
> 0000.04:00.7
>
> ###########################################
> dpdk_example_kni -- -P -p 1 --config="(0,1,2,3)"
> Fails, Cause: Could not start port0 (-1)
> ###########################################
> dpdk_example_kni -- -P -p 2 --config="(1,4,5,6)"
> Works
> pci device 04:00.03
> Lcore 4 is reading from port1
> Lcore 5 is writing to port1
> ###########################################
> dpdk_example_kni -- -P -p 4 --config="(2,1,2,3)"
> Fails, Cause: Could not start port2 (-1)
> They are still trying to use Lcore 1&2
>
>
>
> Environment:
> ============
> SLES 12 SP3
> Kernel 4.4.73-5-default x86_64
> dpdk-tools-16.11.1-6.50.x86_64
> dpdk-kmp-default-16.11.1_k4.4.73_5-6.50.x86_64
> dpdk-16.11.1-6.50.x86_64
>
> Hardware:
> =========
> # /usr/sbin/hwinfo --netcard
> 87: PCI 400.0: 0200 Ethernet controller
> [Created at pci.378]
> Unique ID: rBUF.sL+v+HVDdA2
> Parent ID: _Znp.dXj21w8z979
> SysFS ID: /devices/pci0000:00/0000:00:02.0/0000:04:00.0
> SysFS BusID: 0000:04:00.0
> Hardware Class: network
> Device Name: "NIC Port 1"
> Model: "Hewlett-Packard Company Flex-10 10Gb 2-port 530FLB Adapter
> [Meru]"
> Vendor: pci 0x14e4 "Broadcom"
> Device: pci 0x168e "NetXtreme II BCM57810 10 Gigabit Ethernet"
> SubVendor: pci 0x103c "Hewlett-Packard Company"
> SubDevice: pci 0x1798 "Flex-10 10Gb 2-port 530FLB Adapter [Meru]"
> Revision: 0x11
> Driver: "bnx2x"
> Driver Modules: "bnx2x"
> Device File: eth0
> Features: FCoEOffload = off, iSCSIOffload = off, StorageOnly = off
> Memory Range: 0xf6000000-0xf67fffff (ro,non-prefetchable)
> Memory Range: 0xf5800000-0xf5ffffff (ro,non-prefetchable)
> Memory Range: 0xf57f0000-0xf57fffff (ro,non-prefetchable)
> Memory Range: 0xf0000000-0xf007ffff (ro,non-prefetchable,disabled)
> IRQ: 81 (no events)
> HW Address: 74:46:a0:f5:03:80
> Permanent HW Address: 74:46:a0:f5:03:80
> Link detected: no
> Module Alias: "pci:v000014E4d0000168Esv0000103Csd00001798bc02sc00i00"
> Driver Info #0:
> Driver Status: bnx2x is active
> Driver Activation Cmd: "modprobe bnx2x"
> Config Status: cfg=no, avail=yes, need=no, active=unknown
> Attached to: #56 (PCI bridge)
>
>
> # /sbin/ethtool -i eth0
> driver: bnx2x
> version: 1.712.30-0
> firmware-version: bc 7.14.62
> expansion-rom-version:
> bus-info: 0000:04:00.0
> supports-statistics: yes
> supports-test: yes
> supports-eeprom-access: yes
> supports-register-dump: yes
> supports-priv-flags: yes
>
> On 01/16/2018 06:58 PM, Patil, Harish wrote:
> >
> >
> > -----Original Message-----
> > From: Nirmoy Das <ndas@suse.de>
> > Date: Tuesday, January 16, 2018 at 8:39 AM
> > To: Harish Patil <Harish.Patil@cavium.com>
> > Cc: "Mody, Rasesh" <Rasesh.Mody@cavium.com>, "users@dpdk.org"
> > <users@dpdk.org>
> > Subject: bnx2x_init failed
> >
> >> Hi Harish/Rasesh,
> >>
> >> I am getting following error on NetXtreme II BCM57810 10 Gigabit
> >> Ethernet while running dpdk KNI/testpmd application
> >>
> >> PMD: bnx2x_reg_write32(): offset=0x0000a3c8 val=0x00000800
> >> PMD: bnx2x_init(): Initialization failed, stack notified driver is NOT
> >> running!
> >> PMD: bnx2x_dev_start(): bnx2x_init failed (-6)
> >> EAL: Error - exiting with code: 1
> >> Cause: Could not start port0 (-1)
> >>
> >> I can't figure out why, its running on 4.4.103-6.38-default and have the
> >> required firmware. Do you have any suggestion why we are facing this
> issue
> >>
> >> Regards,
> >> Nirmoy
> >> --
> >> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB
> >> 21284 (AG Nürnberg) Maxfeldstr. 5
> >> D-90409 Nürnberg / Phone: +49-911-740 18-4
> >
> >
> > Hi Nirmoy,
> > Is it testpmd or KNI or both which is not working?
> > Pls provide the exact cmdline you used to launch the applications?
> >
> > Thanks.
> >>
> >
>
> Nirmoy
> --
> SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB
> 21284 (AG Nürnberg) Maxfeldstr. 5
> D-90409 Nürnberg / Phone: +49-911-740 18-4
>
next prev parent reply other threads:[~2018-01-25 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 16:39 Nirmoy Das
2018-01-16 17:58 ` Patil, Harish
2018-01-17 10:18 ` Nirmoy Das
2018-01-25 13:30 ` nirmoy das [this message]
2018-01-31 20:05 ` Patil, Harish
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='CAN6iQk+n=yVyU6mSD7hXyX7nwuQOKhScijpUMiFGz8_vKt=C7A@mail.gmail.com' \
--to=nirmoy.aiemd@gmail.com \
--cc=Harish.Patil@cavium.com \
--cc=Rasesh.Mody@cavium.com \
--cc=ndas@suse.de \
--cc=users@dpdk.org \
/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).