Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #81772 > unrolled thread

Bug#1063151: igb: unpredictable interface names for four port nic

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1063151: igb: unpredictable interface names for four port nic Valentin <valentin@ominous.space> - 2024-02-06 16:10 +0100
    Bug#1063151: igb: unpredictable interface names for four port nic Václav Ovsík <vaclav.ovsik@i.cz> - 2024-02-06 16:50 +0100

#81772 — Bug#1063151: igb: unpredictable interface names for four port nic

[Multipart message — attachments visible in raw view] — view raw

I suspect the issue might be somewhere in your udev configuration.

You can get the evaluated udev rules by running 'udevadm test <device path>'

So running 'udevadm test /sys/class/net/ens6f2' and 'udevadm test /sys/class/
net/eth0' and comparing outputs should tell you/everyone else whats different 
for those devices and why they use different naming schemes.

The old ethX names depend on the order of initialization and is therefore 
unstable.
The new format (e.g. ens6f2) depends on pci device numbers and is stable.

Cheers,
Valentin

[toc] | [next] | [standalone]

#81773

[Multipart message — attachments visible in raw view] — view raw

Dear Valentin,

On Tue, Feb 06, 2024 at 03:58:45PM +0100, Valentin wrote:
> I suspect the issue might be somewhere in your udev configuration.
> 
> You can get the evaluated udev rules by running 'udevadm test <device path>'
> 
> So running 'udevadm test /sys/class/net/ens6f2' and 'udevadm test /sys/class/
> net/eth0' and comparing outputs should tell you/everyone else whats different 
> for those devices and why they use different naming schemes.

Output of both commands attached…

> The old ethX names depend on the order of initialization and is therefore 
> unstable.
> The new format (e.g. ens6f2) depends on pci device numbers and is stable.

Yes, unstable are old names, right

Some errors are reported for eth0 interface:

  eth0: Policy *slot* yields "ens6f0".
  eth0: Could not set AlternativeName= or apply AlternativeNamesPolicy=, ignoring: File exists
  eth0: /usr/lib/udev/rules.d/80-net-setup-link.rules:11 NAME 'ens6f0'
  eth0: /usr/lib/udev/rules.d/99-systemd.rules:68 RUN '/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/$name --prefix=/net/ipv4/neigh/$name --prefix=/net/ipv6/conf/$name --prefix=/net/ipv6/neigh/$name'
  eth0: sd-device: Created db file '/run/udev/data/n69' for '/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/eth0'
  ens6f0: Failed to rename network interface 69 from 'eth0' to 'ens6f0': File exists

The bug should be reassigned to udev.

Thank you very much for tip!
-- 
Zito

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web