#52 igb 3.3.6 Link detected

closed
Todd Fujinaka
igb (31)
standalone_driver
5
2014-01-16
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 3 4 > >> (Page 2 of 4)
  • Todd Fujinaka
    Todd Fujinaka
    2013-10-07

    • assigned_to: Todd Fujinaka
     
  • Harald Dunkel
    Harald Dunkel
    2013-10-07

    Same result for 5.0.6. Attached is the output of dmesg. At the end of this file you see how eth2 becomes ready after a manual ifconfig-down-up cycle.

    Hope this helps.

     
    Attachments
  • Harald Dunkel
    Harald Dunkel
    2013-10-08

    PS: If you need the output of a customized kernel with some debug options enabled: This shouldn't be a problem. I would be glad to help.

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-10-08

    Do you have the latest BIOS for your system?

    Can you send:
    CPU information (model number and speed)
    Motherboard information (model number)
    Memory (how much, what speed, what size)

    ethtool -e ethX
    ethtool -i ethX
    cat /proc/interrupts
    cat /var/log/messages
    uname -a
    cat /etc/*release

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-10-08

    Also, it appears that this is a Dell motherboard. I think we need you to file a bug with them first.

     
  • Harald Dunkel
    Harald Dunkel
    2013-10-09

    It is an Intel mainboard S2600CP.

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-10-09

    Where is the data I asked for?

    There is something odd with your system as the lspci shows a string in the on-board i350 NVM that says, "Dell". I would like all the previous info I asked for before, including the EEPROM dump from both the onboard Ethernet adapter and from the NIC.

    I will try to find out locally if that string is really supposed to be in your EEPROM image.

     
  • Todd Fujinaka
    Todd Fujinaka
    2013-10-09

    I did find out that the string was inadvertently left in the EEPROM image. We'll still need the rest of the information.

    Thanks.

     
  • Harald Dunkel
    Harald Dunkel
    2013-10-15

    Sorry for the delay.

    Attached you can find the information you have asked for. CPU, BIOS version, memory, etc. can be found in the output of dmidecode. A BIOS upgrade to version 02.01.0002 is not an option, because it doesn't boot, if the 3ware RAID controller is plugged in (I tried).

     
    Attachments
  • Hi,

    It seems to me that I faced the same problem on Dell PowerEdge T420 server with latest firmware.

    $ modinfo igb | grep ^version
    version:        5.0.5
    $ lspci | grep I350
    02:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    02:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    $ 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 pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Speed: Unknown!
        Duplex: Unknown! (255)
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                       drv probe link
        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 pause frame use: Symmetric
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: off
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000007 (7)
                       drv probe link
        Link detected: yes
     
    Attachments
<< < 1 2 3 4 > >> (Page 2 of 4)