Re: e1000e startup problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/30/2011 11:37 AM, Kevin H. Hobbs wrote:
> I have a fedora 14 server here who's ethernet interface seems to take
> just a bit too long to establish a link.
> 
> Whenever it starts it is inaccessible over the network, which is a real
> pain for a server. I have to go over with the monitor and keyboard,
> crawl under the desk...
> 
> When I try to restart the network interface with "service network
> restart" I get something that looks like :
> 
> Bringing up interface eth0:
> Determining IP information for eth0...[big number] ADDRCONF(NETDEV_UP):
> eth0: link is not ready.....
>                                                       [FAILED]
> [big number] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex...
> 
> Which sounds to me like a timeout was just a bit too short.
> 
> If I try a few times in a row suddenly it works.
> 
> [kevin@backup ~]$ uname -a
> Linux backup.hooperlab 2.6.35.14-96.fc14.x86_64 #1 SMP Thu Sep 1
> 11:59:56 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
> 
> [kevin@backup ~]$ lspci -nn | grep -i eth
> 04:00.0 Ethernet controller [0200]: Intel Corporation 82573E Gigabit
> Ethernet Controller (Copper) [8086:108c] (rev 03)
> 05:05.0 Ethernet controller [0200]: Intel Corporation 82541GI Gigabit
> Ethernet Controller [8086:1076] (rev 05)
> 
> [kevin@backup ~]$ dmesg | tail
> [ 1633.233297] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
> [ 1633.284094] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
> [ 1633.285079] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1642.265283] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
> [ 1642.316094] e1000e 0000:04:00.0: irq 73 for MSI/MSI-X
> [ 1642.317556] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [ 1647.280547] e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow
> Control: RX/TX
> [ 1647.285563] e1000e 0000:04:00.0: eth0: 10/100 speed: disabling TSO
> [ 1647.291153] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [ 1657.802008] eth0: no IPv6 routers present

Sounds like the switch it's connected to is having issues with the
autonegotiation for speed or duplex settings.  That's not that uncommon
with certain switches.

You might try adding the appropriate parameters to your
/etc/modprobe.d/dist.conf:

	options e1000 speed=100 duplex=full

to remove the autonegotiation from the mix.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, C2 Hosting          ricks@xxxxxxxx -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-              Careful!  Ugly strikes 9 out of 10 people!            -
----------------------------------------------------------------------
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux