Red Hat Bugzilla – Bug 847164
biosdevname assigns interface names inconsistently
Last modified: 2017-04-20 06:27:16 EDT
Description of problem:
On a specific machine, biosdevname usually assigns the name "em2" to the only ethernet interface. After rebooting recently, it instead assigned the name "em1" to this interface. If I run biosdevname manually, it reports that the name should be "em2":
# biosdevname -i em1
# biosdevname --policy physical -i em1
Running "ifconfig -a" reports that the only interfaces are "em1", "lo", "wlan0", and "virbr0".
Inconsistent interface names cause network configuration to fail at boot. This is a pretty serious, though unpredictable problem.
Version-Release number of selected component (if applicable):
So far just once. Usually the name is "em2" (and everything works), but this time it was "em1" (and network initialization fails).
Steps to Reproduce:
Ethernet interface is named "em1". Since there is a /etc/sysconfig/network-scripts/ifcfg-em2 file from the installer, but no ifcfg-em1 script, networking fails to start.
Ethernet interface should be named "em2" as usual.
For what it's worth, this has now happened three more times, and it seems to be coming up with the inconsistent name "em1" a bit more often than "em2".
Please attach the output from the following -
3. biosdevname -d
4. 'lspci -tv' and 'lspci -vvvxxx'
Created attachment 604990 [details]
Created attachment 604991 [details]
lspci -tv output
Created attachment 604992 [details]
Created attachment 604993 [details]
lspci -vvvxxx output
Created attachment 604994 [details]
biosdevname -d output
As you might notice from the biosdevname -d output, I turned off biosdevname on the kernel command line as a work around.
Hmm, this is an Atheros Wifi card. I thought biosdevname had blacklisted that card... looks like this is a different PCI Vendor/Device code than previous cards.
See RedHat bugzilla 801885, 789635, 781572
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '17'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 17's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 17 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged change the
'version' to a later Fedora version prior to Fedora 17's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.