kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #186743
[Bug 1578141] Re: Predictable interface names partially broken with igb driver
I recently ran into this while upgrading 76 systems. In my research I
have concluded that this bug is the result of bad information coming
from the BIOS 3.0b, 3.0c, and 3.2. This bug is not present with BIOS
3.00.
If you run biosdevname, you will see that the BIOS Device name is em1
for both of the intel i350 interfaces resulting (as mentioned above by
Dr. Jens Rosenboom (j-rosenboom-j) in dracut successfully naming the
first device to initialize as eno1. If you reboot the system and check
udevadm, you can see that the interfaces can alternate in which port is
initialized first resulting in eno1 moving from port1 to port2. This is
causing problems primarily with bonding our interfaces.
sudo biosdevname -d
BIOS device: em1
Kernel name: eno1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 2
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x8000090e
Bus Info: 0000:06:00.0
PCI name : 0000:06:00.0
PCI Slot : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label: Onboard Intel Ethernet 1
sysfs Index: 1
sysfs Label: Onboard Intel Ethernet 1
Embedded Index: 1
Duplicate: True
BIOS device: em1
Kernel name: eth1
Permanent MAC: 00:00:00:00:00:00
Assigned MAC : 00:00:00:00:00:00
ifIndex: 3
Driver: igb
Driver version: 5.2.15-k
Firmware version: 1.61, 0x8000090e
Bus Info: 0000:06:00.1
PCI name : 0000:06:00.1
PCI Slot : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label: Onboard Intel Ethernet 2
sysfs Index: 1
sysfs Label: Onboard Intel Ethernet 2
Embedded Index: 2
Duplicate: True
I have submitted my findings for all of my nodes to Supermicro seeking a
bug fix and releasing an update BIOS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1578141
Title:
Predictable interface names partially broken with igb driver
Status in linux package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
New
Bug description:
Note: I'm not sure whether this is really a kernel bug or something
within systemd/udev, please advise how to further debug.
On a system with two GE ports, instead of getting named eno1 and eno2,
I am getting eno1 and renameN. Where N starts at 3 and increases by 2
on every iteration of doing "rmmod igb;modprobe igb". The
corresponding lines in dmesg look like this:
[ 2.748429] igb 0000:07:00.0: added PHC on eth0
[ 2.748431] igb 0000:07:00.0: Intel(R) Gigabit Ethernet Network Connection
[ 2.748433] igb 0000:07:00.0: eth0: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8e
[ 2.748505] igb 0000:07:00.0: eth0: PBA No: 106100-000
[ 2.748506] igb 0000:07:00.0: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 2.802555] igb 0000:07:00.1: added PHC on eth1
[ 2.802557] igb 0000:07:00.1: Intel(R) Gigabit Ethernet Network Connection
[ 2.802559] igb 0000:07:00.1: eth1: (PCIe:5.0Gb/s:Width x4) 00:25:90:d7:60:8f
[ 2.802631] igb 0000:07:00.1: eth1: PBA No: 106100-000
[ 2.802632] igb 0000:07:00.1: Using MSI-X interrupts. 8 rx queue(s), 8 tx queue(s)
[ 2.803618] igb 0000:07:00.0 eno1: renamed from eth0
[ 2.833208] igb 0000:07:00.1 rename3: renamed from eth1
What is even worse: Sometimes the naming changes and the second
interface ends up as eno1 while the first interface is named renameN
with an even N. The bad thing about this version is that when it
happens while the installer is running, the installer will setup
"rename2" as the primary network interface, which works fine for the
installation itself, but after installation is finished and the first
boot of the installed system happens, that interface will be gone,
leaving the system without network connectivity.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-21-generic 4.4.0-21.37
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 May 4 09:48 seq
crw-rw---- 1 root audio 116, 33 May 4 09:48 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Wed May 4 10:00:39 2016
HibernationDevice: RESUME=/dev/mapper/compute--node37--vg-swap
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro X9DRT-HF+
PciMultimedia:
ProcEnviron:
LANGUAGE=en_US:
TERM=screen
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic root=/dev/mapper/compute--node37--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-21-generic N/A
linux-backports-modules-4.4.0-21-generic N/A
linux-firmware 1.157
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.0c
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X9DRT-HF+
dmi.board.vendor: Supermicro
dmi.board.version: 0123456789
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0c:bd05/21/2014:svnSupermicro:pnX9DRT-HF+:pvr0123456789:rvnSupermicro:rnX9DRT-HF+:rvr0123456789:cvnSupermicro:ct17:cvr0123456789:
dmi.product.name: X9DRT-HF+
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1578141/+subscriptions
References