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 18:16:39 +0100 [thread overview]
Message-ID: <7840f4be-c86b-c03f-04f9-ded06502ac3e@6wind.com> (raw)
In-Reply-To: <CACZ4nhu8yQi9mpimyYdkV_nZY7yLs7=BK8Whn8smUaPM6XawyQ@mail.gmail.com>
Hello Ajit
The card is not correctly probed by the kernel, and so the FW version is
not visible.
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
next prev parent reply other threads:[~2022-03-02 17:16 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 [this message]
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=7840f4be-c86b-c03f-04f9-ded06502ac3e@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).