DPDK CI discussions
 help / color / mirror / Atom feed
From: Brandon Lo <blo@iol.unh.edu>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: ci@dpdk.org, dpdklab <dpdklab@iol.unh.edu>
Subject: Re: [dpdk-ci] New 100G Broadcom NIC Ubuntu
Date: Tue, 28 Jul 2020 15:41:10 -0400	[thread overview]
Message-ID: <CAOeXdvYQ-Krd2FKo_gQkAP32+KyQAoM+DFRy4OftyiocTJKhNA@mail.gmail.com> (raw)
In-Reply-To: <CACZ4nhv7o9OOMnB_1wdo3YQvWEXPbF+ScOQJExXydcZCFGnzog@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3443 bytes --]

Hi Ajit,

Yes, I believe we can use this current version as the driver.
I'll let you know if I run into any issues with this.

Thank you for your help,
Brandon

On Tue, Jul 28, 2020 at 3:19 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:

> Hi Brandon,
> I copied over a more recent code for the NIC.
> And it loads fine on the two systems.
> The code is currently in /home/ajitkhaparde/bnxt_en-1.10.1-216.1.142.0
> Till I find a release version of the driver for Ubuntu, we could use this?
> We can copy the bnxt_en.ko over to
> /lib/modules/4.15.0-112-generic/kernel/drivers/net/ethernet/broa
> dcom/bnxt/bnxt_en.ko
>
> Please let me know.
>
> Thanks
> Ajit
>
> On Tue, Jul 28, 2020 at 10:33 AM Brandon Lo <blo@iol.unh.edu> wrote:
>
>> Hi Ajit,
>>
>> That issue occurs sometimes on my end as well. There's no clear solution
>> other than to try again later.
>> I will look into the issue and try to make a permanent fix.
>>
>> Thanks,
>> Brandon
>>
>> On Tue, Jul 28, 2020 at 1:22 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
>> wrote:
>>
>>> Brandon,
>>> I have sent them a reminder. I will keep you posted.
>>> But I tried to login into the system to peek around and the VPN seems to
>>> continuously negotiate/authenticate. For some reason the connection
>>> is getting reset.
>>> Any idea on what might be causing this?
>>>
>>> Thanks
>>> Ajit
>>>
>>> On Tue, Jul 28, 2020 at 9:48 AM Brandon Lo <blo@iol.unh.edu> wrote:
>>>
>>>> Hi Ajit,
>>>>
>>>> Have you gotten a response yet?
>>>> I've tried the firmware from the official website but it's supported on
>>>> Fedora/Redhat instead of Ubuntu.
>>>>
>>>> Thanks,
>>>> Brandon
>>>>
>>>> On Tue, Jul 21, 2020 at 5:28 PM Ajit Khaparde <
>>>> ajit.khaparde@broadcom.com> wrote:
>>>>
>>>>> Hi Brandon,
>>>>> Maybe I might have to update it to a newer firmware.
>>>>> Let me check internally and get back.
>>>>>
>>>>> Thanks
>>>>> Ajit
>>>>>
>>>>>
>>>>> On Tue, Jul 21, 2020 at 1:23 PM Brandon Lo <blo@iol.unh.edu> wrote:
>>>>>
>>>>>> Hi Ajit,
>>>>>>
>>>>>> We've received the Broadcom 100G NIC and installed it onto the
>>>>>> machine. However, the drivers don't seem to support Ubuntu, information
>>>>>> from
>>>>>> https://www.broadcom.com/products/ethernet-connectivity/network-adapters/100gb-nic-ocp/p2100g
>>>>>> .
>>>>>>
>>>>>> I've also updated the kernel to the latest version. The card appears
>>>>>> with the correct name in lspci and lshw, but it has no available MAC
>>>>>> address, so I can't use it in setting up the nic single core performance
>>>>>> testing.
>>>>>>
>>>>>> Do you know what could be causing this issue?
>>>>>>
>>>>>> Thanks,
>>>>>> Brandon
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Brandon Lo
>>>>>>
>>>>>> UNH InterOperability Laboratory
>>>>>>
>>>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>>>>> <https://www.google.com/maps/search/21+Madbury+Rd,+Suite+100,+Durham,+NH+03824?entry=gmail&source=g>
>>>>>>
>>>>>> blo@iol.unh.edu
>>>>>>
>>>>>> www.iol.unh.edu
>>>>>>
>>>>>
>>>>
>>>> --
>>>>
>>>> Brandon Lo
>>>>
>>>> UNH InterOperability Laboratory
>>>>
>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>>>
>>>> blo@iol.unh.edu
>>>>
>>>> www.iol.unh.edu
>>>>
>>>
>>
>> --
>>
>> Brandon Lo
>>
>> UNH InterOperability Laboratory
>>
>> 21 Madbury Rd, Suite 100, Durham, NH 03824
>>
>> blo@iol.unh.edu
>>
>> www.iol.unh.edu
>>
>

-- 

Brandon Lo

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

blo@iol.unh.edu

www.iol.unh.edu

[-- Attachment #2: Type: text/html, Size: 12396 bytes --]

  reply	other threads:[~2020-07-28 19:41 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21 20:22 Brandon Lo
2020-07-21 21:27 ` Ajit Khaparde
2020-07-28 16:47   ` Brandon Lo
2020-07-28 17:22     ` Ajit Khaparde
2020-07-28 17:32       ` Brandon Lo
2020-07-28 19:19         ` Ajit Khaparde
2020-07-28 19:41           ` Brandon Lo [this message]
2020-08-04 16:16             ` Brandon Lo
2020-08-04 16:37               ` Ajit Khaparde
2020-08-04 17:42                 ` Brandon Lo
2020-08-11 17:45                   ` Brandon Lo
2020-08-11 17:47                     ` Ajit Khaparde
2020-08-20  4:29                       ` Ajit Khaparde
2020-08-20 15:39                         ` Brandon Lo
2020-08-20 21:07                           ` Ajit Khaparde
2020-08-25 20:13                             ` Brandon Lo
2020-08-26 19:57                               ` Ajit Khaparde
2020-09-01 18:09                                 ` Brandon Lo
2020-09-01 18:11                                   ` Ajit Khaparde
2020-10-22 19:03                                     ` Brandon Lo
2020-10-22 19:27                                       ` Ajit Khaparde
2020-12-03 16:48                                         ` [dpdk-ci] [dpdklab] " Brandon Lo

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=CAOeXdvYQ-Krd2FKo_gQkAP32+KyQAoM+DFRy4OftyiocTJKhNA@mail.gmail.com \
    --to=blo@iol.unh.edu \
    --cc=ajit.khaparde@broadcom.com \
    --cc=ci@dpdk.org \
    --cc=dpdklab@iol.unh.edu \
    /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).