Bug 190015 - tg3 network driver fail to come up
Summary: tg3 network driver fail to come up
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel
Version: 4.4
Hardware: All
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: John W. Linville
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-26 17:58 UTC by Steve Dickson
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-09 19:11:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Steve Dickson 2006-04-26 17:58:35 UTC
Description of problem:
Reboot my system the tg3 network drivers fail to come up. The
error messages are:
Setting network parameters:  [  OK  ]
Bringing up loopback interface:  ip_tables: (C) 2000-2002 Netfilter core team [
 OK  ]
Bringing up interface eth1:  Device eth1 has different MAC address than
expected, ignoring. [FAILED]
Bringing up interface eth2:  Device eth2 has different MAC address than
expected, ignoring. [FAILED]

Reboot the system a second time takes care of the problem


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

How reproducible:
90%

Steps to Reproduce:
1.reboot a system that uses tg3 network drivers
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Steve Dickson 2006-04-26 18:01:53 UTC
Here is my module.conf file

alias eth0 e100
alias eth1 tg3
alias eth2 tg3
alias scsi_hostadapter cciss
alias usb-controller ohci-hcd
options diskdump compress=1


Comment 2 John W. Linville 2006-05-02 15:21:05 UTC
What are the contents of /etc/sysconfig/network-scripts/ifcfg-eth*?  It sounds 
like you are specifying a MAC address that doesn't match what is on the tg3 
card(s)? 
 
You may want to include the output of dmesg as well...thanks! 

Comment 3 Steve Dickson 2006-05-30 07:40:01 UTC
cat /etc/sysconfig/network-scripts/ifcfg-eth*
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:D0:B7:5D:E3:02
ONBOOT=no
TYPE=Ethernet
USERCTL=no
PEERDNS=yes
IPV6INIT=no
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:0B:CD:0E:92:0D
ONBOOT=yes
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
IPV6INIT=no
DEVICE=eth2
BOOTPROTO=none
HWADDR=00:0B:CD:0E:92:0C
ONBOOT=yes
TYPE=Ethernet
USERCTL=yes
PEERDNS=yes
IPV6INIT=no
NETMASK=255.255.255.0
IPADDR=10.0.0.5



Comment 4 Dan Carpenter 2006-05-30 08:46:05 UTC
Eth2 has a lower mac address than eth1.  They probably should be the other way
around.

Did you load the system with acpi turned off or something?  That could make them
come up in reverse order.



Comment 5 John W. Linville 2006-05-30 18:20:56 UTC
Do you have a need to specify the HWADDR?  If not, the easiest thing is 
probably to remove those lines from ifcfg-eth*...does doing that straighten 
things out?

Comment 6 Steve Dickson 2006-06-30 11:55:52 UTC
Sorry for the delayed response on this... This got lost in the
the sea of other bugzilla emails..

wrt to Comment #4, I rebooted with a new kernel... and kudzu
ask if I wanted to remove a "network interface" . Mistakenly
I said yes... but then kudzu asked if I wanted to install a
network interface so I said yes...

wrt to Comment #5, I'll try that... 

Comment 7 John W. Linville 2006-07-10 14:59:00 UTC
Any word on results from comment 5?

Comment 8 John W. Linville 2006-08-09 19:11:14 UTC
I'm going to close this one as INSUFFICIENT_DATA in order to "clear the 
books"...if it continues to be a problem, please reopen...thanks!


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