#52 igb 3.3.6 Link detected

closed
igb (33)
standalone_driver
5
2014-12-04
2012-01-06
liu dalin
No

I use igb 3.3.6 driver, run ifconfig ethX up time, link detected is no, you must run the ifconfig ethX down, ifconfig ethX up, in order to detect the line connection. Why is this?

dmesg | grep "version 3.3.6"

[ 3.581351] Intel(R) Gigabit Ethernet Network Driver - version 3.3.6

ifconfig eth2 up

ethtool eth2

Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 6
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: no

ifconfig eth2 down

ifconfig eth2 up

ethtool eth2

Settings for eth2:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 6
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes

Discussion

<< < 1 2 (Page 2 of 2)
  • Oleksandr Samoylyk

    But if you look at my output of dmesg you will find that link is UP after system boot:

    [   57.733896] igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX

    some time later it goes down:
    [ 2748.723902] igb: eth2 NIC Link is Down

    It's dual-port Intel I350 network adapter: eth2 is interconnected using Cat5e crossover cable (Auto-MDIX should be supported though) to the other Dell PowerEdge T420 server which has the same hardware and software configuration - it's a two-node HA cluster.

    I've tried to connect the second port of Intel I350 network adapter (eth3) to the switch, but I couldn't reproduce the problem.

    So, it seems to be a problem just within interlink of two Intel I350 Ethernet adapters.

    I've another IBM System x3650 M4 two-node cluster with the same setup, which has builtin Intel I350's:

    06:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    06:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    06:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    06:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)

    The problem isn't reproducible there at all.

    As a workaround I've downgraded the igb driver to 4.1.2 from Dell Software Repository, which did a trick:
    http://linux.dell.com/repo/hardware/latest/pet420/suse11_64/repoview/intel-igb.html

    You can find two outputs of lspci -vvv for I350 done on DELL and IBM servers in attachments.

     
    Last edit: Oleksandr Samoylyk 2013-10-17
  • Todd Fujinaka

    Todd Fujinaka - 2013-10-17

    Can you send an ethregs dump of both sides of the link? Ideally it would be good to get that before and after the failure.

    Thanks.

     
  • Todd Fujinaka

    Todd Fujinaka - 2013-10-23

    I'm still not convinced it's not the OS or perhaps your bridging configuration. Are there any indications in /var/log/messages as to what is happening?

    Bridging is handled by a completley different driver and we have no control over it.

     
  • Harald Dunkel

    Harald Dunkel - 2013-10-24

    I can reproduce this problem without a bridge configured.

    Have you considered trying to reproduce the problem, e.g. by using 2(!) I350 controllers? My servers with just a single I350 controller work fine (all using the same kernel and igb driver, of course).

     
  • Todd Fujinaka

    Todd Fujinaka - 2013-10-24

    Harald,
    We haven't seen the issue in our testing. Unfortunately, we don't support Debian. We test on the latest RHEL5 and RHEL6 as well as the latest SLES10 and SLES11. Have you reproduced the problem on any other distro than Debian?

    Thanks.

     
  • Todd Fujinaka

    Todd Fujinaka - 2013-10-24

    I should add that we also test the net and net-next kernels, but I'm thinking this is an OS configuration issue, so just replacing the kernel probably wouldn't change things.

     
  • Harald Dunkel

    Harald Dunkel - 2013-10-26

    I don't have Redhat or Suse. We are talking about problems with the most recently released version of the igb driver, which is not included in RedHat's or Suse's distro, anyway. Maybe we could agree upon trying igb 5.0.6 together with the most recent kernel released on http://kernel.org/ (i.e. 3.11.6)?

     
  • Todd Fujinaka

    Todd Fujinaka - 2013-12-02

    We don't see anything that shows this is a driver problem in your dmesg. We can't reproduce this issue.

    We also think this is an issue with your configuration and userland. Because of this, we don't think just changing the kernel will change anything.

    I am closing this issue.

     
  • Todd Fujinaka

    Todd Fujinaka - 2013-12-02
    • status: open --> closed
     
<< < 1 2 (Page 2 of 2)

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks