Bug 118960 - bad boot reporting for network interfaces config
Summary: bad boot reporting for network interfaces config
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts
Version: rawhide
Hardware: athlon
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-03-23 08:42 UTC by keith adamson
Modified: 2014-03-17 02:43 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-03-23 17:29:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description keith adamson 2004-03-23 08:42:22 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040312

Description of problem:
I have two network interfaces:

RealTek RTL8139
forcedeth.c

The interface numbering is unusual because of adding and removing
interfaces.  Presently there is no eth0:

# cat /etc/modprobe.conf
include /etc/modprobe.conf.dist
alias eth1 8139too
alias usb-controller ehci-hcd
alias usb-controller1 ohci-hcd
alias sound-slot-0 snd-intel8x0
install sound-slot-0 /sbin/modprobe --ignore-install sound-slot-0 &&
/bin/aumix-minimal -f /etc/.aumixrc -L >/dev/null 2>&1 || :
alias eth2 forcedeth

# find /etc/sysconfig/ -name ifcfg-eth\*
/etc/sysconfig/network-scripts/ifcfg-eth2
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/sysconfig/networking/devices/ifcfg-eth2
/etc/sysconfig/networking/devices/ifcfg-eth1
/etc/sysconfig/networking/profiles/default/ifcfg-eth2
/etc/sysconfig/networking/profiles/default/ifcfg-eth1

# cat /etc/sysconfig/network-scripts/ifcfg-eth1
# Realtek|RTL-8139/8139C/8139C+
DEVICE=eth1
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=00:30:BD:28:F0:07

# cat /etc/sysconfig/network-scripts/ifcfg-eth2
# nVidia Corporation|nForce2 Ethernet Controller
DEVICE=eth2
ONBOOT=yes
BOOTPROTO=static
IPADDR=192.168.3.1
NETMASK=255.255.255.0
HWADDR=00:30:1B:38:C0:8F

After boot the interface setups looks fine:

# /sbin/ifconfig
eth1      Link encap:Ethernet  HWaddr 00:30:BD:28:F0:07
          inet addr:192.168.0.190  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::230:bdff:fe28:f007/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:295 errors:0 dropped:0 overruns:0 frame:0
          TX packets:247 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:318360 (310.8 Kb)  TX bytes:58621 (57.2 Kb)
          Interrupt:11 Base address:0x9000
 
eth2      Link encap:Ethernet  HWaddr 00:30:1B:38:C0:8F
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::230:1bff:fe38:c08f/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:546 (546.0 b)
          Interrupt:5 Base address:0x1000
 
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:237 errors:0 dropped:0 overruns:0 frame:0
          TX packets:237 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:15811 (15.4 Kb)  TX bytes:15811 (15.4 Kb)

But the reporting during boot look bad:

# grep -e 'eth[012]' -e '8139' -e 'forcedeth'  /var/log/messages | cut
-c24-
kernel: 8139too Fast Ethernet driver 0.9.27
kernel: eth0: RealTek RTL8139 at 0x9000, 00:30:bd:28:f0:07, IRQ 11
kernel: forcedeth.c: Reverse Engineered nForce ethernet driver.
Version 0.25.
kernel: eth1: forcedeth.c: subsystem: 01297:0531 bound to 0000:00:04.0
kernel: 8139too Fast Ethernet driver 0.9.27
kernel: eth0: RealTek RTL8139 at 0x9000, 00:30:bd:28:f0:07, IRQ 11
kernel: eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
kernel: forcedeth.c: Reverse Engineered nForce ethernet driver.
Version 0.25.
kernel: eth0: forcedeth.c: subsystem: 01297:0531 bound to 0000:00:04.0
kernel: eth2: no link during initialization.
network: Bringing up interface eth2:  succeeded

# dmesg | grep -e 'eth[012]' -e '8139' -e 'forcedeth'
8139too Fast Ethernet driver 0.9.27
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0x9000, 00:30:bd:28:f0:07, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
divert: allocating divert_blk for eth1
eth1: forcedeth.c: subsystem: 01297:0531 bound to 0000:00:04.0
divert: freeing divert_blk for eth0
divert: freeing divert_blk for eth1
8139too Fast Ethernet driver 0.9.27
divert: allocating divert_blk for eth0
eth0: RealTek RTL8139 at 0x9000, 00:30:bd:28:f0:07, IRQ 11
eth0:  Identified 8139 chip type 'RTL-8100B/8139D'
eth1: link up, 100Mbps, full-duplex, lpa 0x41E1
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.25.
divert: allocating divert_blk for eth0
eth0: forcedeth.c: subsystem: 01297:0531 bound to 0000:00:04.0
eth2: no link during initialization.
eth1: no IPv6 routers present
eth2: no IPv6 routers present


Version-Release number of selected component (if applicable):
initscripts-7.48-1, kernel-2.6.4-1.279

How reproducible:
Always

Steps to Reproduce:
1.install FC2 test 1
2.add and remove some interfaces
3.boot
    

Actual Results:  wrong boot reports for interface setup

Expected Results:  correct boot reports for interface setup

Additional info:

Comment 1 Bill Nottingham 2004-03-23 17:29:40 UTC
This is not really solveable in the current framework; you can't
assign a name before the driver is loaded.


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