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 include the
firmware version?
On 09/27/2013 10:43 AM, Paul Boven wrote:
> 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.
>
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 include the
firmware version?
On 09/27/2013 10:43 AM, Paul Boven wrote:
> 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.
>
-- 07[skype]
Thanks and Regards,
Narinder Gupta (PMP) <email address hidden>
Technical Account Manager
Canonical, Ltd. narindergupta [irc.freenode.net]
+1.281.736.5150 narindergupta20
Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com