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 name p2p2 during boot anymore, and instead I have an unexpected interface name 'rename3' show up in my ifconfig. Which breaks things quite badly.
-- 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 Title: biosdevname gives name of device as rename7 in Quantal Status in “linux” package in Ubuntu: Confirmed Status in “udev” package in Ubuntu: Confirmed Status in “linux” source package in Quantal: Confirmed Status in “udev” source package in Quantal: Confirmed Status in “linux” source package in Raring: Confirmed Status in “udev” source package in Raring: Confirmed Bug description: In Quantal kernel biosdevname feature is not working as it suppose to be. On hardware we are seeing an issue where few of the network interface names are named as rename7 etc.. while biosdevname -d utility provides the correct biosname while kernel name have been messed up. There are total 16 network interfaces on the server which are ALOMs for Emulex card connected to system. It seems this issue is a race condition and will get fixed in Fedora 18. But having fix in Quantal will help also. https://bugzilla.redhat.com/show_bug.cgi?id=782145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
