From: Qian Cai <cai@lca.pw>
To: Moshe Shemesh <moshe@mellanox.com>
Cc: Vladyslav Tarasiuk <vladyslavt@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Parav Pandit <parav@mellanox.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: No networking due to "net/mlx5e: Add support for devlink-port in non-representors mode"
Date: Wed, 25 Mar 2020 16:25:17 -0400 [thread overview]
Message-ID: <483B11FF-4004-4909-B89A-06CA48E3BBBC@lca.pw> (raw)
In-Reply-To: <52874e86-a8ae-dcf0-a798-a10e8c97d09e@mellanox.com>
> On Mar 25, 2020, at 3:33 PM, Moshe Shemesh <moshe@mellanox.com> wrote:
>
>
> On 3/25/2020 6:01 AM, Qian Cai wrote:
>> Reverted the linux-next commit c6acd629ee (“net/mlx5e: Add support for devlink-port in non-representors mode”)
>> and its dependencies,
>>
>> 162add8cbae4 (“net/mlx5e: Use devlink virtual flavour for VF devlink port”)
>> 31e87b39ba9d (“net/mlx5e: Fix devlink port register sequence”)
>>
>> on the top of next-20200324 allowed NICs to obtain an IPv4 address from DHCP again.
>
>
> These patches should not interfere DHCP.
>
> You might have dependencies on interface name which was changed by this patch, please check.
Yes,
Before,
[ 238.225149][ T2021] mlx5_core 0000:0b:00.1 enp11s0f1: renamed from eth1
[ 238.511324][ T2035] mlx5_core 0000:0b:00.0 enp11s0f0: renamed from eth0
Now,
[ 234.448420][ T2013] mlx5_core 0000:0b:00.1 enp11s0f1np1: renamed from eth1
[ 234.664236][ T2042] mlx5_core 0000:0b:00.0 enp11s0f0np0: renamed from eth0
>
>> 0b:00.0 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
>> 0b:00.1 Ethernet controller: Mellanox Technologies MT27710 Family [ConnectX-4 Lx]
>>
>> [ 223.280777][ T13] mlx5_core 0000:0b:00.0: firmware version: 14.21.1000
>> [ 223.287753][ T13] mlx5_core 0000:0b:00.0: 63.008 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x8 link)
>> [ 226.292153][ C0] mlx5_core 0000:0b:00.0: Port module event: module 0, Cable plugged
>> [ 226.874100][ T2023] mlx5_core 0000:0b:00.1: Adding to iommu group 2
>> [ 227.343553][ T13] mlx5_core 0000:0b:00.1: firmware version: 14.21.1000
>> [ 227.350467][ T13] mlx5_core 0000:0b:00.1: 63.008 Gb/s available PCIe bandwidth (8.0 GT/s PCIe x8 link)
>> [ 230.026346][ C0] mlx5_core 0000:0b:00.1: Port module event: module 1, Cable unplugged
>> [ 230.522660][ T2023] mlx5_core 0000:0b:00.0: MLX5E: StrdRq(0) RqSz(1024) StrdSz(256) RxCqeCmprss(0)
>> [ 231.448493][ T2023] mlx5_core 0000:0b:00.1: MLX5E: StrdRq(0) RqSz(1024) StrdSz(256) RxCqeCmprss(0)
>> [ 232.436993][ T2007] mlx5_core 0000:0b:00.1 enp11s0f1np1: renamed from eth1
>> [ 232.690895][ T2013] mlx5_core 0000:0b:00.0 enp11s0f0np0: renamed from eth0
next prev parent reply other threads:[~2020-03-25 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 4:01 No networking due to "net/mlx5e: Add support for devlink-port in non-representors mode" Qian Cai
2020-03-25 19:33 ` Moshe Shemesh
2020-03-25 20:25 ` Qian Cai [this message]
2020-03-26 0:17 ` Saeed Mahameed
2020-03-26 3:18 ` Qian Cai
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=483B11FF-4004-4909-B89A-06CA48E3BBBC@lca.pw \
--to=cai@lca.pw \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moshe@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=vladyslavt@mellanox.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).