Bug 133133 - Sun v60x NIC Interface Imporper Detection
Summary: Sun v60x NIC Interface Imporper Detection
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 3.0
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: John W. Linville
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-21 20:11 UTC by Ryan Shultz
Modified: 2007-11-30 22:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-27 17:37:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ryan Shultz 2004-09-21 20:11:05 UTC
Description of problem:
I have new v60x hardware from Sun that detects the interfaces 
incorrectly when configuring the networking in RedHat.  The hardware 
I believe is all Intel hardware.  This is an onboard dual NIC setup.  
It detects the port labeled 1 as eth1 and port 2 as eth0.  When 
installing Fedora Core 2, it detects properly.

Version-Release number of selected component (if applicable):

How reproducible:
Install RH Enterprise LInux 3 on a v60x server.  A kernel upgrade 
does not fix the issue when using up2date.

Steps to Reproduce:
1. Install Enterprise Linux 3 on v60x hardware
Actual results:

Expected results:

Additional info:
A kernel upgrade does not resolve the issue.

Comment 1 John W. Linville 2004-09-27 17:37:22 UTC
After consulting my wise elders, I offer the following explanation:

<dledford> linville: If I recall correctly, the issue is that
basically in 2.4, a standard driver loads, it searches the PCI device
list for possible device matches and grabs the ones it wants.  As a
result, devices are usually found in PCI device list order.
<dledford> linville: For 2.6, pretty much all the drivers are switched
over to using the PCI regristration mechanism that enables hotplug. 
But, that means the driver doesn't search for devices any more, it
registers a table with the PCI layer and the PCI layer then calls it
when a device matching an entry in the table shows up.
<dledford> linville: Probably for purely no reason other than "it made
sense to sort things this way", the PCI layer may be looping over the
PCI device list, checking for one entry in the table at a time or
something like that, which could result in the detection order
changing between 2.4 and 2.6.

The ordering is fundamentally cosmetic.  If it truly bothers you, you
can change it like this:

   cd /etc/sysconfig/network-scripts
   mv ifcfg-eth0 $$
   mv ifcfg-eth1 ifcfg-eth0
   mv $$ ifcfg-eth1
   vi ifcfg-eth[01] # change DEVICE= lines to match new filenames

Then, reboot (or `service network restart` might work)...

Note You need to log in before you can comment on or make changes to this bug.