[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250617160935.08f8652a@kernel.org>
Date: Tue, 17 Jun 2025 16:09:35 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Przemek Kitszel <przemyslaw.kitszel@...el.com>
Cc: "Kaplan, David" <David.Kaplan@....com>, "jedrzej.jagielski@...el.com"
<jedrzej.jagielski@...el.com>, "anthony.l.nguyen@...el.com"
<anthony.l.nguyen@...el.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>, Mateusz
Polchlopek <mateusz.polchlopek@...el.com>, Bharath R <bharath.r@...el.com>,
"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [REGRESSION] ixgbe broken after devlink support patch
On Tue, 17 Jun 2025 11:01:18 +0200 Przemek Kitszel wrote:
> > Normally, the device is given a name like enp194s0f0 and connects to the wired network.
>
> now the name is likely to be different, please see this thread:
> https://lkml.org/lkml/2025/4/24/1750
>
> Is it possible that your network setup script has some part of interface
> discovery hardcoded?
Hi Przemek, could you/someone on your side try the workaround
I suggested in the earlier thread? I'm not sure how actively
developed ixgbe is, if the work is not related to any new devices
with more complicated port topology breaking people's setups feels
pretty unnecessary.
Powered by blists - more mailing lists