https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c1 --- Comment #1 from Per Jessen 2011-03-01 18:58:50 UTC --- Created an attachment (id=416877) --> (http://bugzilla.novell.com/attachment.cgi?id=416877) output from biosdevname -d -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c3 --- Comment #3 from Per Jessen 2011-03-01 19:00:05 UTC --- Created an attachment (id=416879) --> (http://bugzilla.novell.com/attachment.cgi?id=416879) output from biosdecode -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c5 Narendra K - changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |narendra_k@dell.com --- Comment #5 from Narendra K - 2011-03-02 16:09:37 UTC --- I understand that biosdevname v0.3.7 is being used. Please confirm. Biosdevname uses SMBIOS type 41 to name onboard interfaces. It looks like the system does not have type 41 defined from looking at the dmidecode output attached. If type 41 is not available, it falls back to PCI IRQ routing table. The attached output looks like this - PCI Interrupt Routing 1.0 present. Router ID: 00:1f.0 Exclusive IRQs: None Compatible Router: 8086:122e Slot Entry 1: ID 00:00, on-board Slot Entry 2: ID 00:01, on-board Slot Entry 3: ID 01:00, slot number 4 Slot Entry 4: ID 00:02, on-board Slot Entry 5: ID 00:1b, on-board Slot Entry 6: ID 00:1c, on-board Slot Entry 7: ID 02:00, slot number 6 ------> note this. It seems to suggest that device 02:00.0 (Intel 82573E) is on slot 6. So biosdevname thinks it is on slot 6 and names it pci6p1. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c7 --- Comment #7 from Per Jessen 2011-03-10 16:01:35 UTC --- (In reply to comment #5)

I understand that biosdevname v0.3.7 is being used. Please confirm.

Confirmed.

Biosdevname uses SMBIOS type 41 to name onboard interfaces. It looks like the system does not have type 41 defined from looking at the dmidecode output attached. If type 41 is not available, it falls back to PCI IRQ routing table.

The attached output looks like this -

PCI Interrupt Routing 1.0 present. Router ID: 00:1f.0 Exclusive IRQs: None Compatible Router: 8086:122e Slot Entry 1: ID 00:00, on-board Slot Entry 2: ID 00:01, on-board Slot Entry 3: ID 01:00, slot number 4 Slot Entry 4: ID 00:02, on-board Slot Entry 5: ID 00:1b, on-board Slot Entry 6: ID 00:1c, on-board Slot Entry 7: ID 02:00, slot number 6 ------> note this.

It seems to suggest that device 02:00.0 (Intel 82573E) is on slot 6. So biosdevname thinks it is on slot 6 and names it pci6p1.

Yes, I understand that, I just wanted to point out that that interface IS embedded, but wasn't named as such. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c10 Torsten Duwe changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |per@opensuse.org Severity|Normal |Enhancement --- Comment #10 from Torsten Duwe 2011-07-27 09:52:08 UTC --- Can you elaborate whether this is a code issue or a BIOS problem? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c12 --- Comment #12 from Narendra K - 2011-08-02 12:39:01 UTC --- (In reply to comment #10)

Can you elaborate whether this is a code issue or a BIOS problem?

The incorrect name is due to wrong PIRQ table entry which says the device is add-in. This is a BIOS issue (as mentioned in comment #5) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=676025 https://bugzilla.novell.com/show_bug.cgi?id=676025#c14 --- Comment #14 from Per Jessen 2011-08-14 09:29:43 UTC --- FYI, the equipment here is a standard IBM office desktop, but I'm pretty certain I have seen a similar issue on HP Proliants. Using biosdevname in the current state, regardless of whether the issue is really a BIOS bug, could cause problems in future SLED/S. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.