From: Thierry Herbelot <thierry.herbelot@6wind.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Somnath Kotur <somnath.kotur@broadcom.com>,
Kalesh Anakkur Purayil <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [DPDK/bnxt] Issues starting bnxt on an Arm server
Date: Wed, 2 Mar 2022 16:13:37 +0100 [thread overview]
Message-ID: <2f0b0ce7-c601-4f53-5d81-b1c45eadf8d0@6wind.com> (raw)
In-Reply-To: <CACZ4nhs_tGb8wjX+Rca39+Fg=CS3ktMBWTgBbWEvkca4vo1bzQ@mail.gmail.com>
Hello Ajit
Thanks for the quick response.
Please keep me posted when you check on your side.
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
next prev parent reply other threads:[~2022-03-02 15:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 14:51 [DPDK/bnxt] Issues starting bnxt on an Arm server Thierry Herbelot
2022-03-02 15:08 ` Ajit Khaparde
2022-03-02 15:13 ` Thierry Herbelot [this message]
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
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=2f0b0ce7-c601-4f53-5d81-b1c45eadf8d0@6wind.com \
--to=thierry.herbelot@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=somnath.kotur@broadcom.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).