From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "Kaplan, David" <David.Kaplan@amd.com>,
"jedrzej.jagielski@intel.com" <jedrzej.jagielski@intel.com>,
"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Bharath R <bharath.r@intel.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [REGRESSION] ixgbe broken after devlink support patch
Date: Tue, 17 Jun 2025 16:09:35 -0700 [thread overview]
Message-ID: <20250617160935.08f8652a@kernel.org> (raw)
In-Reply-To: <59faaf3b-d75d-4405-a7bb-a137918617e3@intel.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Przemek Kitszel <przemyslaw.kitszel@intel.com>
Cc: "Kaplan, David" <David.Kaplan@amd.com>,
"jedrzej.jagielski@intel.com" <jedrzej.jagielski@intel.com>,
"anthony.l.nguyen@intel.com" <anthony.l.nguyen@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
Bharath R <bharath.r@intel.com>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [REGRESSION] ixgbe broken after devlink support patch
Date: Tue, 17 Jun 2025 16:09:35 -0700 [thread overview]
Message-ID: <20250617160935.08f8652a@kernel.org> (raw)
In-Reply-To: <59faaf3b-d75d-4405-a7bb-a137918617e3@intel.com>
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.
next prev parent reply other threads:[~2025-06-17 23:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 19:42 [Intel-wired-lan] [REGRESSION] ixgbe broken after devlink support patch Kaplan, David
2025-06-16 19:42 ` Kaplan, David
2025-06-17 9:01 ` [Intel-wired-lan] " Przemek Kitszel
2025-06-17 9:01 ` Przemek Kitszel
2025-06-17 14:29 ` [Intel-wired-lan] " Kaplan, David
2025-06-17 14:29 ` Kaplan, David
2025-06-17 23:09 ` Jakub Kicinski [this message]
2025-06-17 23:09 ` Jakub Kicinski
2025-06-18 10:25 ` [Intel-wired-lan] " Przemek Kitszel
2025-06-18 10:25 ` Przemek Kitszel
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=20250617160935.08f8652a@kernel.org \
--to=kuba@kernel.org \
--cc=David.Kaplan@amd.com \
--cc=anthony.l.nguyen@intel.com \
--cc=bharath.r@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
--cc=przemyslaw.kitszel@intel.com \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.