Bug 49949 - command "ifup eth0" fails for some epro100 boards
Summary: command "ifup eth0" fails for some epro100 boards
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-25 16:04 UTC by Jay Turner
Modified: 2015-01-07 23:49 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-07-25 21:44:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Glen Foster 2001-07-25 16:04:31 UTC
Preamble: I'm filing this defect against initscripts at the advice of Matt
Wilson.

Description of Problem: With the beta-3 candidate tree, a network install
works to the point that it can exchange packets with the NFS/FTP/HTTP
server and complete the installation.  Upon reboot, there are some machines
in the test-lab that fail to bring up eth0 (an epro100)., such as the
Compaq Proliant 3000... there are other machines in the test-lab that
succeed with the same operation, such as the HP Eagle.

How Reproducible: 100% on the Compaq Proliant 3000 (in the test-lab).

Steps to Reproduce:
1. network-based install
2. reboot
3. watch ifconfig fail on eth0

Actual Results: (sorry, this was a German install)
# ifconfig
lo        Protokoll:Lokale Schleife  
          inet Adresse:127.0.0.1  Maske:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          Kollisionen:0 Sendewarteschlangenldnge:0 
          RX bytes:838 (838.0 b)  TX bytes:838 (838.0 b)

# ifup eth0
Determining IP information for eth0... failed; no link present.  Check
cable?
# rpm -q kernel
kernel-2.4.6-3.1
# uname -a
Linux test130.test.redhat.com 2.4.6-3.1 #1 Tue Jul 24 14:54:56 EDT 2001
i686 unknown
# 

Expected Results: I would expect the network interface to properly
configure itself since the install worked without (networking) error.

Additional Information: Matt Wilson claims this is an initscript problem,
due to the way that the mii-tool call is working.  SO, I've included some
"extra" diagnostics:

# cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 7
model name	: Pentium III (Katmai)
stepping	: 2
cpu MHz		: 498.867
cache size	: 512 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 2
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat
pse36 mmx fxsr sse
bogomips	: 996.14

# lspci
00:00.0 Host bridge: ServerWorks CNB20-LE CPU to PCI Bridge (rev 04)
00:00.1 Host bridge: ServerWorks: Unknown device 0005 (rev 02)
00:03.0 System peripheral: Compaq Computer Corporation Advanced System
Management Controller
00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC
[Mach64 GT IIC] (rev 7a)
00:0f.0 ISA bridge: ServerWorks OSB4 (rev 4d)
00:11.0 Host bridge: ServerWorks CNB20-LE CPU to PCI Bridge (rev 04)
00:11.1 Host bridge: ServerWorks: Unknown device 0005 (rev 02)
01:04.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875
(rev 14)
01:04.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875
(rev 14)
01:08.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 05)
# lspci -n
00:00.0 Class 0600: 1166:0007 (rev 04)
00:00.1 Class 0600: 1166:0005 (rev 02)
00:03.0 Class 0880: 0e11:a0f0
00:05.0 Class 0300: 1002:4756 (rev 7a)
00:0f.0 Class 0601: 1166:0200 (rev 4d)
00:11.0 Class 0600: 1166:0007 (rev 04)
00:11.1 Class 0600: 1166:0005 (rev 02)
01:04.0 Class 0100: 1000:000f (rev 14)
01:04.1 Class 0100: 1000:000f (rev 14)
01:08.0 Class 0200: 8086:1229 (rev 05)
# lspci -v
00:00.0 Host bridge: ServerWorks CNB20-LE CPU to PCI Bridge (rev 04)
	Flags: bus master, medium devsel, latency 64
	Memory at <unassigned> (32-bit, prefetchable)
	Memory at <unassigned> (32-bit, non-prefetchable) [size=4K]

00:00.1 Host bridge: ServerWorks: Unknown device 0005 (rev 02)
	Flags: bus master, medium devsel, latency 64

00:03.0 System peripheral: Compaq Computer Corporation Advanced System
Management Controller
	Subsystem: Compaq Computer Corporation: Unknown device b0f3
	Flags: medium devsel
	I/O ports at 1800 [size=256]
	Memory at c6cfff00 (32-bit, non-prefetchable) [size=256]

00:05.0 VGA compatible controller: ATI Technologies Inc 3D Rage IIC 215IIC
[Mach64 GT IIC] (rev 7a) (prog-if 00 [VGA])
	Subsystem: ATI Technologies Inc 3D Rage IIC 215IIC [Mach64 GT IIC]
	Flags: bus master, stepping, medium devsel, latency 64
	Memory at c5000000 (32-bit, prefetchable) [size=16M]
	I/O ports at 2000 [size=256]
	Memory at c6cfe000 (32-bit, non-prefetchable) [size=4K]
	Expansion ROM at <unassigned> [disabled] [size=128K]
	Capabilities: [5c] Power Management version 1

00:0f.0 ISA bridge: ServerWorks OSB4 (rev 4d)
	Subsystem: ServerWorks OSB4
	Flags: bus master, medium devsel, latency 0

00:11.0 Host bridge: ServerWorks CNB20-LE CPU to PCI Bridge (rev 04)
	Flags: medium devsel
	Memory at <unassigned> (32-bit, prefetchable)

00:11.1 Host bridge: ServerWorks: Unknown device 0005 (rev 02)
	Flags: medium devsel

01:04.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875
(rev 14)
	Subsystem: Compaq Computer Corporation Embedded Ultra Wide SCSI Controller
	Flags: bus master, medium devsel, latency 255, IRQ 9
	I/O ports at 3000 [size=256]
	Memory at c6ffff00 (32-bit, non-prefetchable) [size=256]
	Memory at c6ffe000 (32-bit, non-prefetchable) [size=4K]

01:04.1 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c875
(rev 14)
	Subsystem: Compaq Computer Corporation Embedded Ultra Wide SCSI Controller
	Flags: bus master, medium devsel, latency 255, IRQ 10
	I/O ports at 3400 [size=256]
	Memory at c6ffdf00 (32-bit, non-prefetchable) [size=256]
	Memory at c6ffc000 (32-bit, non-prefetchable) [size=4K]

01:08.0 Ethernet controller: Intel Corporation 82557 [Ethernet Pro 100]
(rev 05)	Subsystem: Compaq Computer Corporation NC3120
	Flags: bus master, medium devsel, latency 64, IRQ 5
	Memory at c6dff000 (32-bit, prefetchable) [size=4K]
	I/O ports at 3800 [size=32]
	Memory at c6e00000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at <unassigned> [disabled] [size=1M]
	Capabilities: [dc] Power Management version 1

# cat /proc/modules
nls_iso8859-1           2880   1 (autoclean)
nls_cp437               4384   1 (autoclean)
vfat                    9456   1 (autoclean)
fat                    31552   0 (autoclean) [vfat]
autofs                 10816   1 (autoclean)
eepro100               17824   0 (unused)
ipchains               36960   0 (unused)
st                     26016   0 (unused)
ext3                   50656   5
jbd                    39376   5 [ext3]
sym53c8xx              57376   6
sd_mod                 11264   6
scsi_mod               93536   3 [st sym53c8xx sd_mod]
# /sbin/mii-tool
eth0: no link

Comment 1 Bill Nottingham 2001-07-25 18:01:16 UTC
waiting for the compaq box to become available. (currently being installed :) )

Comment 2 Pekka Savola 2001-07-25 21:44:06 UTC
the mii-tool link availability check might lead to some unpredictable results on rarer cards that don't support
MII properly, or mii interface doesn't work right.  I guess there are some eepro100's which do this.  I've noticed some
wackiness with older 3c59x's.

For debugging, the relevant bits are:

mii-tool -v
lspci -v 

(mii-tool is based on Donald Becker's mii-diag, available at ftp.scyld.com, which sometimes might give extra
debug information)


Comment 3 Bill Nottingham 2001-07-25 22:00:01 UTC
mii-tool requires the link to be up (ip link set up eth0) for it to work. This
change will be in initscripts-6.08-1.

(And yes, there are drivers with broken mii support. Those drivers should be
fixed. :) )



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