From: David Howells <dhowells@redhat.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: dhowells@redhat.com,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Paulo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Is it possible to undo the ixgbe device name change?
Date: Fri, 25 Apr 2025 09:58:35 +0100 [thread overview]
Message-ID: <3531595.1745571515@warthog.procyon.org.uk> (raw)
In-Reply-To: <7b468f16-f648-4432-aa59-927d37a411a7@lunn.ch>
Andrew Lunn <andrew@lunn.ch> wrote:
> Are you sure this patch is directly responsible? Looking at the patch
I bisected it to that commit. Userspace didn't change.
> Notice the context, not the change. The interface is being called
> eth%d, which is normal. The kernel will replace the %d with a unique
> number. So the kernel will call it eth42 or something. You should see
> this in dmesg.
Something like this?
... systemd-udevd[2215]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
... kernel: ixgbe 0000:01:00.0 enp1s0: renamed from eth0
or:
... systemd-udevd[2568]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
... kernel: ixgbe 0000:01:00.0 enp1s0np0: renamed from eth0
I presume the kernel message saying that the renaming happened is triggered by
systemd-udevd?
David
next prev parent reply other threads:[~2025-04-25 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 18:06 Is it possible to undo the ixgbe device name change? David Howells
2025-04-24 21:32 ` Andrew Lunn
2025-04-24 23:10 ` Jakub Kicinski
2025-04-25 8:58 ` David Howells [this message]
2025-04-25 12:11 ` Andrew Lunn
2025-04-29 21:40 ` Jacob Keller
2025-04-25 9:46 ` David Howells
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=3531595.1745571515@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=jedrzej.jagielski@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).