Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

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

5 views
Skip to first unread message

Valentin

unread,
Feb 6, 2024, 10:10:05 AM2/6/24
to

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

Václav Ovsík

unread,
Feb 6, 2024, 10:50:05 AM2/6/24
to
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
udevadm-test-ens6f2.txt
udevadm-test-eth0.txt

Valentin

unread,
Feb 6, 2024, 11:40:04 AM2/6/24
to

>   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


It looks like your BIOS is reporting the same PCIe Slot for both your igb and Broadcom network cards.
I assume one of your Broadcom network interfaces is already named ens6f0.

 

In fact., this might be a BIOS issue...
whats the output of `sudo dmidecode -t9`?


Best solution for you is probably to set all or some network interface names manually, see https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES

Cheers,
Valentin

Václav Ovsík

unread,
Feb 8, 2024, 4:40:05 AM2/8/24
to
Is it definitely a BIOS problem? If yes, we can close the bug of course.

I have a little bit of time to investigate the problem further:
(My knowledge is limited)

kory:/sys/bus/pci# for x in $(find . -name 'address' -print|sort); do echo -n "$x "; cat $x; done
./slots/0-1/address 0000:3a:00
./slots/0-2/address 0000:3a:02
./slots/0-3/address 0000:5d:02
./slots/0/address 0000:17:01
./slots/1/address 0000:5d:00
./slots/4/address 0000:ae:00
./slots/5/address 0000:17:00
./slots/6/address 0000:00:1c

kory:/sys/bus/pci# lspci -tvv|head -25
-+-[0000:00]-+-00.0 Intel Corporation Sky Lake-E DMI3 Registers
| +-05.0 Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers
| +-05.2 Intel Corporation Sky Lake-E RAS
| +-05.4 Intel Corporation Sky Lake-E IOAPIC
| +-08.0 Intel Corporation Sky Lake-E Ubox Registers
| +-08.1 Intel Corporation Sky Lake-E Ubox Registers
| +-08.2 Intel Corporation Sky Lake-E Ubox Registers
| +-11.0 Intel Corporation C620 Series Chipset Family MROM 0
| +-11.5 Intel Corporation C620 Series Chipset Family SSATA Controller [AHCI mode]
| +-14.0 Intel Corporation C620 Series Chipset Family USB 3.0 xHCI Controller
| +-14.2 Intel Corporation C620 Series Chipset Family Thermal Subsystem
| +-16.0 Intel Corporation C620 Series Chipset Family MEI Controller #1
| +-16.1 Intel Corporation C620 Series Chipset Family MEI Controller #2
| +-16.4 Intel Corporation C620 Series Chipset Family MEI Controller #3
| +-17.0 Intel Corporation C620 Series Chipset Family SATA Controller [AHCI mode]
| +-1c.0-[01]--+-00.0 Intel Corporation I350 Gigabit Network Connection
| | +-00.1 Intel Corporation I350 Gigabit Network Connection
| | +-00.2 Intel Corporation I350 Gigabit Network Connection
| | \-00.3 Intel Corporation I350 Gigabit Network Connection
| +-1c.4-[02-03]----00.0-[03]----00.0 Matrox Electronics Systems Ltd. Integrated Matrox G200eW3 Graphics Controller
| +-1c.5-[04]--+-00.0 Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
| | \-00.1 Broadcom Inc. and subsidiaries NetXtreme BCM5720 Gigabit Ethernet PCIe
| +-1f.0 Intel Corporation C621 Series Chipset LPC/eSPI Controller
| +-1f.2 Intel Corporation C620 Series Chipset Family Power Management Controller
| +-1f.4 Intel Corporation C620 Series Chipset Family SMBus


kory:/sys/bus/pci# lspci -nnv|sed -n '/^00:1c/,/^$/ p;' |grep -Pi '^0|devname|slot'
00:1c.0 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #1 [8086:a190] (rev f9) (prog-if 00 [Normal decode])
DeviceName: SLOT 6
Physical Slot: 6
Capabilities: [40] Express Root Port (Slot+), MSI 00
00:1c.4 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #5 [8086:a194] (rev f9) (prog-if 00 [Normal decode])
Physical Slot: 6
Capabilities: [40] Express Root Port (Slot+), MSI 00
00:1c.5 PCI bridge [0604]: Intel Corporation C620 Series Chipset Family PCI Express Root Port #6 [8086:a195] (rev f9) (prog-if 00 [Normal decode])
Physical Slot: 6
Capabilities: [40] Express Root Port (Slot-), MSI 00

Any idea what to gather next?
Thanks
--
Zito

Václav Ovsík

unread,
Feb 10, 2024, 4:30:05 PM2/10/24
to
I was curious today and tried to build latest systemd and it is fixed already!
I have done a git bisect and the commit fixing the problem is

https://github.com/systemd/systemd/commit/af7417ac7b07bc01232982bf46e9d72e69e7f820

Regards
--
Zito
0 new messages