Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 61436

Summary: ifconfig's showing double info. when 11 NICs installed
Product: [Retired] Red Hat Linux Reporter: Danny Trinh <danny_trinh>
Component: net-toolsAssignee: Phil Knirsch <pknirsch>
Status: CLOSED CURRENTRELEASE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: afom_m, clay_cooper, dale_kaisner, danny_trinh, dean_oliver, gary_lerhaupt, john_hull, joshua_giles, katzj, matt_domsch, michael_e_brown, robert_hentosh, rvokal
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-05-16 23:02:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 61590    
Attachments:
Description Flags
ifconfig of 10 NICs and 11 NICs
none
ifconfig & /proc/vet/dev files of 10 NICs & 12NICs configurations. none

Description Danny Trinh 2002-03-19 17:19:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)

Description of problem:
When the system had 11 NICs installed, ifconfig shows double info. of eth1 - 
eth10. This doesn't happen if the system has only 10 NICs

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


How reproducible:
Always

Steps to Reproduce:
1.Hardware: PE4600 + 1 embedded eepro100 + 5 dual pro100 NICs
2.Install Hampton B2
3.run ifconfig, and check the output info
4.remove the line "alias eth10 ..." in /etc/modules.conf
5.remove /etc/sysconfig/network-scripts/ifcfg-eth10 file
6.reboot PE4600, press F2 for BIOS setup, then disable the embedded NIC.
7.reboot PE4600
8.run ifconfig again and check its output
	

Actual Results:  ifconfig shows double info.

Expected Results:  normal info as it used to be

Additional info:

Comment 1 Danny Trinh 2002-03-19 17:22:33 UTC
Created attachment 49004 [details]
ifconfig of 10 NICs and 11 NICs

Comment 2 Danny Trinh 2002-03-21 17:57:22 UTC
See this problem in beta 3 also.

Comment 3 Phil Knirsch 2002-03-26 09:28:57 UTC
I've had another bugreport with ISDN cards that showed exactly the same
symptoms. Problem is, i don't have the hardware here and therefore can't
reproduce the bug, so it's going to be fairly tricky to find a fix or even the
root of the bug.

Maybe i can fix it for the ISDN devices which should then hopefully result in a
fix for this bug as well.

FYI the ISDN bug is 56429.

Read ya, Phil

Comment 4 Phil Knirsch 2002-03-28 15:30:49 UTC
Could you append the output of

  cat /proc/net/dev

and

  ip addr

for 10 and 11 nics for that machine here as well? I suspect it's a parsing
problem somewhere (see the ISDN bug) as /proc/net/dev, ip and route all show the
correct number of devices, and i suspect the same to be true for this bug.

Thanks,

Read ya, Phil

Comment 5 Danny Trinh 2002-03-29 21:20:45 UTC
After we upgrade Jaguar's main board, the problem goes away. I have tested with 
BIOS version A02. Also, I run the tests on 2.4.18-0.12bigmem, smp, and up 
kernels. ifconfig sees correctly 12 NIC cards.

Comment 6 Danny Trinh 2002-04-05 21:54:00 UTC
I saw this on beta 4 again.

Comment 7 Phil Knirsch 2002-04-08 12:51:54 UTC
Still need the output of /proc/net/dev for 10 and 11 nics.

I don't have access to the hardware and therefore can't reproduce this bug
making it impossible to debug or even fix the problem.

Read ya, Phil

Comment 8 Danny Trinh 2002-04-08 15:50:54 UTC
Created attachment 52667 [details]
ifconfig & /proc/vet/dev files of 10 NICs & 12NICs configurations.

Comment 9 John A. Hull 2002-04-08 15:59:41 UTC
Phil, are you in Raleigh?? We sent Red Hat 6 Dual-Port Pro 100+ NICs last month 
that should help replicate the problem.

Comment 10 Phil Knirsch 2002-04-08 16:38:38 UTC
Unfortunately i am not located in Raleigh, therefore the hardware there doesn't
really help me a lot. I might ask on of the guys over there to put it in some
box, but this is very ineffective.

I'll try to get by with the /proc/net/dev output and see wether thats already
enough info to debug and create a fix.

Read ya, Phil

Comment 11 Jeremy Katz 2002-04-12 04:27:33 UTC
Ick, net-tools is ugly code.  Fixed in 1.60-4 and better.

Comment 12 Danny Trinh 2002-05-15 19:52:45 UTC
This bug appears in Pensacola gold version also.

Comment 13 Danny Trinh 2002-05-16 23:01:58 UTC
I reopen this bug because I saw this in Pensacola also.

Comment 14 Phil Knirsch 2002-08-20 13:12:31 UTC
Unfortunately this fix didn't make it into Pensacola final anymore.

You can use the 7.3 version of the net-tools, though if necessary. The only
difference is this small fix actually.

Read ya, Phil