*** This bug is a duplicate of bug 1324558 ***
https://bugs.launchpad.net/bugs/1324558
** This bug has been marked a duplicate of bug 1324558
[SRU] biosdevname returns identical names for two different devices.
--
You received this bug notification because you are a member of Kernel
I'm seeing the same behavior in 13.10 saucy with some Chelsio cards.
They consistently show up as rename3 and rename4.
Was there any resolution to your situation?
I can supply my logs as well if that would help.
--
You received this bug notification because you are a member of Kernel
Packages,
Server configuration:
SuperMicro X9DRi-F mainboard
On-board dual I350 (rev 01) Gigabit Ethernet controller [8086:1521], igb driver
PCI-E X540-AT2 (rev01) 10Gbase-T Ethernet card [8086:1528], ixgbe driver.
bios: Version 2.0a, 03/27/2013
The current situation causes two issues:
1.) The former
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu Raring)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Quantal)
Status: New = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: udev (Ubuntu)
Status: New = Confirmed
--
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/1090002
Same problem on two identical machines that have dual 1Gb/s ethernet cards on
the motherboard.
This apparently causes booting to stall for about a minute, see this snippet
from syslog after a boot. These timestamps are
while the machine is booting, and hasn't gotten to the point where it
Hi Narinder,
Well, that's exactly the problem - sometime during the boot, apparently
biosdev thought it was p2p1, and the OS tried to assign the name p2p1 to
it, which it had already given out. When I run biosdev now, it shows up
as being p2p2 allright - but the interface doesn't get assigned the
Yeah we ran this issue with biosdevname developer and after close
examination he told thats the issue with the BIOS firmware where SMBIOS
entry were not proper. When we tried to run this on later HP FW system
we do not see the bug anymore.
Will you please let me know you server configuraiton
Ugh, I also just noticed that this messes up the order of my interfaces
in SNMP - it's swapped the two ones, so now my graphs that used to show
the external interfaces, are showing the internal ones, and v.v.
--
You received this bug notification because you are a member of Kernel
Packages,
11 matches
Mail list logo