I am seeing the same issue on some of my OpenStack compute nodes,
interestingly those which seem to have a newer CPU than others.
Affected CPU: Intel(R) Xeon(R) CPU E5-1650 v3 @ 3.50GHz
Mapped in guest to: Intel Core i7 9xx (Nehalem Class Core i7)
Unaffected Host CPU: Intel(R) Xeon(R) CPU E5-2660
Public bug reported:
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 i
We have seen the issue only when deploying Xenial, installations running
Precise or Trusty do not seem to be affected.
Running with 4.6.0-040600rc6-generic has shown the same behaviour.
After doing the rmmod/modprobe cycle, I have now found the attached set
of messages in the output of "journalct
Looking further, it seems that the BIOS is providing broken information,
see this snippet from dmidecode output:
Handle 0x007E, DMI type 41, 11 bytes
Onboard Device
Reference Designation: Onboard Intel Ethernet 1
Type: Ethernet
Status: Enabled
Type Instance: 1
@Martin: Fixing the installed system is easy, the bad case happens when
the installer sets up the system with "rename2" as the first interface,
making access via console necessary in order to recover.
root@compute-node37:~# SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_id
/sys/class/net/eno1
c
@Andy: So 3.16.0-34 is the kernel with the fix? Any chance that it will
also be backported to the 3.13 series?
--
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/1413540
Title:
Trusty soft l
6 matches
Mail list logo
