Weird PCI/PCIe enumeration on PowerEdge 860s

[Thomas_Chenault at Dell.com]

It would be very surprising if tg3 decided to rename itself or one of
its interfaces. This type of device renaming is most likely initiated by
a network startup script in response to the contents of a configuration
file. I don't have the Ubuntu knowledge necessary to recommend which
files to check. 

If all else fails, try temporarily hiding the nameif utility. This is
likely to 1) prevent the renaming, and 2) cause the calling script to
report errors, thus revealing which script initiates the renaming.


Thomas


-----Original Message-----
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Chris Howells
Sent: Tuesday, February 13, 2007 4:50 AM
To: linux-poweredge-Lists
Subject: Weird PCI/PCIe enumeration on PowerEdge 860s

Hi,

I'm configring a new PowerEdge 860 server. It has two onboard Broadcom 
ethernet ports and I've put an Intel Pro/1000 PT Quad Port GigE card 
into one of the PCIe slots. The OS is Ubuntu 6.06.1.

Here's a snippet from dmesg:

[42949389.280000] e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network 
Connection
[42949389.500000] e1000: eth1: e1000_probe: Intel(R) PRO/1000 Network 
Connection
[42949389.740000] e1000: eth2: e1000_probe: Intel(R) PRO/1000 Network 
Connection
[42949389.960000] e1000: eth3: e1000_probe: Intel(R) PRO/1000 Network 
Connection
[42949389.960000] eth4: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] 
(PCI Express) 10/100/1000BaseT Ethernet 00:15:c5:fc:5c:28
[42949389.960000] eth4: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] 
Split[0] WireSpeed[1] TSOcap[1]
[42949389.960000] eth4: dma_rwctrl[76180000]
[42949389.970000] eth5: Tigon3 [partno(BCM95721) rev 4101 PHY(5750)] 
(PCI Express) 10/100/1000BaseT Ethernet 00:15:c5:fc:5c:29
[42949389.970000] eth5: RXcsums[1] LinkChgREG[1] MIirq[1] ASF[1] 
Split[0] WireSpeed[1] TSOcap[1]
[42949389.970000] eth5: dma_rwctrl[76180000]
[42949394.160000] tg3: eth1: Link is up at 1000 Mbps, full duplex.
[42949394.160000] tg3: eth1: Flow control is on for TX and on for RX.
[42949412.780000] eth1: no IPv6 routers present


So, everything was going OK until towards the end, when tg3 decided it 
wanted to be eth1, when e1000 already was. Linux problem, BIOS problem? 
Any insight would be useful.

-- 
Chris Howells <chris at transitive.com>
System Administrator - Transitive Ltd.
http://www.transitive.com

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq