From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Ajit Khaparde (ajit.khaparde@broadcom.com)"
<ajit.khaparde@broadcom.com>,
Thierry Herbelot <thierry.herbelot@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>,
Ruifeng Wang <Ruifeng.Wang@arm.com>, nd <nd@arm.com>,
nd <nd@arm.com>
Subject: RE: [DPDK/bnxt] Issues starting bnxt on an Arm server
Date: Fri, 4 Mar 2022 00:56:38 +0000 [thread overview]
Message-ID: <AM8PR08MB5810B12E47DEB9186933DEE198059@AM8PR08MB5810.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CACZ4nhtiUa8V=dVn=avbrXCZDrH5_yCGG-SOuz+dxUCscyv8yg@mail.gmail.com>
+ Ruifeng
<snip>
>
> On Wed, Mar 2, 2022 at 9:28 AM Thierry Herbelot
> <thierry.herbelot@6wind.com> wrote:
> >
> > On 3/2/22 18:26, Ajit Khaparde wrote:
> > > On Wed, Mar 2, 2022 at 9:16 AM Thierry Herbelot
> > > <thierry.herbelot@6wind.com> wrote:
> > >>
> > >> Hello Ajit
> > >>
> > >> The card is not correctly probed by the kernel, and so the FW version is
> > >> not visible.
> > > Thanks Thierry.
> > > I thought it was just the PMD running into trouble.
> > >
> > > Can you give details of the ARM server?
> > > Make, Vendor, etc..?
> >
> > This a Huawei server:
> > TaiShan 200 Server (Model 2180) aarch64, 48 cores, 2.6GHz, 64GB RAM
>
> Ok. I tried this on a HUAWEI Kunpeng 920 running 4.18.0-
> 348.2.1.el8_5.aarch64.
> I can load the bnxt_en kernel driver and the DPDK PMD without issues.
> And I did load vfio with enable_unsafe_noiommu_mode=1 .
>
> While we are pursuing this further internally,
> I have added Honnappa to see if he can provide any insight.
There is not much information on the error.
Just wondering if it is possible to move the card to x86 machine and check the firmware version and upgrade the firmware version there.
>
> Ajit
>
> >
> > Thierry
> >
> > >
> > >
> > >>
> > >> I see this in the kernel dmesg:
> > >> bnxt_en 0000:03:00.0 (unnamed net_device) (uninitialized): Error
> > >> (timeout: 500015) msg {0x0 0x0} len:0
> > >> bnxt_en 0000:03:00.0 (unnamed net_device) (uninitialized): Firmware not
> > >> responding, status: 0x8ffff
> > >>
> > >> And then there are no bnxt_en netdevices.
> > >>
> > >> Best regards
> > >>
> > >> Thierry
> > >>
> > >>
> > >> On 3/2/22 18:13, Ajit Khaparde wrote:
> > >>> On Wed, Mar 2, 2022 at 7:13 AM Thierry Herbelot
> > >>> <thierry.herbelot@6wind.com> wrote:
> > >>>>
> > >>>> Hello Ajit
> > >>>>
> > >>>> Thanks for the quick response.
> > >>>>
> > >>>> Please keep me posted when you check on your side.
> > >>> Can you tell what is the firmware version on the card?
> > >>>
> > >>>>
> > >>>> Best regards
> > >>>>
> > >>>> Thierry
> > >>>>
> > >>>> On 3/2/22 16:08, Ajit Khaparde wrote:
> > >>>>>>
> > >>>>>> Is this a know issue ?
> > >>>>> No.
> > >>>>> We have tried the Broadcom PMD on ARM server(s) and have been
> > >>>>> able to use it without any issues.
> > >>>>> But we can try it again and get back to you.
> > >>>>>
> > >>>>>
> > >>>>>>
> > >>>>>> Thanks
> > >>>>>>
> > >>>>>> Thierry Herbelot
> > >>>>>>
> > >>>>>> PS: a similar error is seen for the Ethernet ports, when handled by the
> > >>>>>> kernel:
> > >>>>>> dmesg|grep bnxt
> > >>>>>> [ 57.823746] bnxt_en 0000:03:00.0 (unnamed net_device)
> > >>>>>> (uninitialized): Error (timeout: 500015) msg {0x0 0x0} len:0
> > >>>>>> [ 59.202255] bnxt_en: probe of 0000:03:00.0 failed with error -16
> > >>>>>> [ 60.641519] bnxt_en 0000:03:00.1 (unnamed net_device)
> > >>>>>> (uninitialized): Error (timeout: 500015) msg {0x0 0x0} len:0
> > >>>>>> [ 61.502237] bnxt_en: probe of 0000:03:00.1 failed with error -16
> > >>>>>>
> > >>>>>>
> > >>>>>> --
> > >>>>>> Thierry Herbelot
> > >>>>>> Senior Software Engineer
> > >>>>>> Tel: +33 1 39 30 92 61
> > >>>>>> http://www.6wind.com/
> > >>>>>>
> > >>>>>> Follow us:
> > >>>>>> https://www.linkedin.com/company/6wind/
> > >>>>>> https://twitter.com/6WINDsoftware
> > >>>>>> https://www.youtube.com/user/6windsoftware
> > >>>>
> > >>>> --
> > >>>> Thierry Herbelot
> > >>>> Senior Software Engineer
> > >>>> Tel: +33 1 39 30 92 61
> > >>>> http://www.6wind.com/
> > >>>>
> > >>>> Follow us:
> > >>>> https://www.linkedin.com/company/6wind/
> > >>>> https://twitter.com/6WINDsoftware
> > >>>> https://www.youtube.com/user/6windsoftware
> > >>
> > >> --
> > >> Thierry Herbelot
> > >> Senior Software Engineer
> > >> Tel: +33 1 39 30 92 61
> > >> http://www.6wind.com/
> > >>
> > >> Follow us:
> > >> https://www.linkedin.com/company/6wind/
> > >> https://twitter.com/6WINDsoftware
> > >> https://www.youtube.com/user/6windsoftware
> >
> > --
> > Thierry Herbelot
> > Senior Software Engineer
> > Tel: +33 1 39 30 92 61
> > http://www.6wind.com/
> >
> > Follow us:
> > https://www.linkedin.com/company/6wind/
> > https://twitter.com/6WINDsoftware
> > https://www.youtube.com/user/6windsoftware
next prev parent reply other threads:[~2022-03-04 0:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 14:51 Thierry Herbelot
2022-03-02 15:08 ` Ajit Khaparde
2022-03-02 15:13 ` Thierry Herbelot
2022-03-02 17:13 ` Ajit Khaparde
2022-03-02 17:16 ` Thierry Herbelot
2022-03-02 17:26 ` Ajit Khaparde
2022-03-02 17:28 ` Thierry Herbelot
2022-03-03 21:12 ` Ajit Khaparde
2022-03-04 0:56 ` Honnappa Nagarahalli [this message]
2022-03-08 8:19 ` Thierry Herbelot
2022-03-08 17:13 ` Ajit Khaparde
2022-03-02 15:16 ` David Marchand
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=AM8PR08MB5810B12E47DEB9186933DEE198059@AM8PR08MB5810.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=nd@arm.com \
--cc=somnath.kotur@broadcom.com \
--cc=thierry.herbelot@6wind.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).