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

Re: Jessie: network link detection problems with Intel nics



On 08/12/2014 01:15 PM, Cyril Brulebois wrote:
Hi,

and thanks for your report (even if the best way is filing a proper bug
report in the BTS: https://www.debian.org/Bugs/).

Floris Bos <bos@je-eigen-domein.nl> (2014-08-12):
I'm having an odd problem on one of my servers in which the network
link is not detected (error getting DHCP, going to console and
entering "ip link" shows NO_CARRIER) on preseeded Jessie
installations.

Mainboard: http://www.supermicro.nl/products/motherboard/Xeon/C220/X10SLM_-LN4F.cfm
4x i210AT NIC on mainboard, cable connected to eth0

Problem always occurs on:

- Debian Jessie when doing automated installations
- Ubuntu 13.10 netinstall
- Ubuntu 14.04 netinstall

Problem does not occurs on:

- Debian Wheezy

Problem sometimes occurs on:

- Interactive installations on Debian Jessie. They work most of the
time, but not always.
A few things that come to mind:
  - what if there's an extra cable plugged on to a NIC that isn't the one
    you PXE-booted from? There might be something going on that could be
    related to the boot method, like a faulty initialization somewhere
    because there was already some traffic on that interface.

Hmm, that is strange as well.
With a second cable connected to one of the other ports it does work, even when PXE booting from eth0, and telling Debian to use eth0. Which doesn't work without the second cable.

It doesn't see the link on eth0 straight away, only after deactivating and activating.

==
Aug 12 14:49:43 netcfg[1663]: INFO: Activating interface eth0
Aug 12 14:49:44 netcfg[1663]: INFO: Waiting time set to 3
Aug 12 14:49:44 kernel: [ 12.793292] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 12 14:49:44 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:44 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:45 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:46 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:47 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:47 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:47 netcfg[1663]: INFO: Reached timeout for link detection on eth0
Aug 12 14:49:47 netcfg[1663]: INFO: found no link on interface eth0.
Aug 12 14:49:47 netcfg[1663]: INFO: eth0 is not a wireless interface. Continuing.
Aug 12 14:49:47 netcfg[1663]: INFO: Taking down interface eth0
Aug 12 14:49:47 netcfg[1663]: INFO: Taking down interface eth0
Aug 12 14:49:47 netcfg[1663]: INFO: Activating interface eth1
Aug 12 14:49:48 netcfg[1663]: INFO: Waiting time set to 3
Aug 12 14:49:48 kernel: [ 16.683201] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Aug 12 14:49:48 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:48 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:49 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:50 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:51 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:51 netcfg[1663]: INFO: ethtool-lite: eth1 is disconnected.
Aug 12 14:49:51 netcfg[1663]: INFO: Reached timeout for link detection on eth1
Aug 12 14:49:51 netcfg[1663]: INFO: found no link on interface eth1.
Aug 12 14:49:51 netcfg[1663]: INFO: eth1 is not a wireless interface. Continuing.
Aug 12 14:49:51 netcfg[1663]: INFO: Taking down interface eth1
Aug 12 14:49:51 netcfg[1663]: INFO: Taking down interface eth1
Aug 12 14:49:51 netcfg[1663]: INFO: Activating interface eth2
Aug 12 14:49:52 netcfg[1663]: INFO: Waiting time set to 3
Aug 12 14:49:52 kernel: [ 20.572957] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:52 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:53 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:54 netcfg[1663]: INFO: ethtool-lite: eth2 is disconnected.
Aug 12 14:49:54 kernel: [ 22.719490] igb: eth2 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Aug 12 14:49:54 kernel: [ 22.719967] IPv6: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
Aug 12 14:49:54 netcfg[1663]: INFO: ethtool-lite: eth2 is connected.
Aug 12 14:49:54 netcfg[1663]: INFO: Found link on eth2
Aug 12 14:49:54 netcfg[1663]: INFO: found link on interface eth2, making it the default. Aug 12 14:49:54 netcfg[1663]: INFO: Found interface eth0 with link-layer address 00:25:90:da:54:0a
Aug 12 14:49:54 netcfg[1663]: INFO: Taking down interface eth0
Aug 12 14:49:54 netcfg[1663]: INFO: Taking down interface eth1
Aug 12 14:49:54 netcfg[1663]: INFO: Taking down interface eth2
Aug 12 14:49:54 netcfg[1663]: INFO: Taking down interface eth3
Aug 12 14:49:54 netcfg[1663]: INFO: Taking down interface lo
Aug 12 14:49:54 netcfg[1663]: INFO: Activating interface eth0
Aug 12 14:49:55 netcfg[1663]: DEBUG: State is now 0
Aug 12 14:49:55 netcfg[1663]: DEBUG: Want link on eth0
Aug 12 14:49:55 netcfg[1663]: INFO: Waiting time set to 3
Aug 12 14:49:55 kernel: [ 23.718898] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 12 14:49:55 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:55 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:56 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:56 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:56 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:56 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:57 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:57 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:57 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:57 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:58 netcfg[1663]: INFO: ethtool-lite: eth0 is disconnected.
Aug 12 14:49:58 kernel: [ 26.657045] igb: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX Aug 12 14:49:58 kernel: [ 26.657502] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Aug 12 14:49:58 netcfg[1663]: INFO: ethtool-lite: eth0 is connected.
Aug 12 14:49:58 netcfg[1663]: INFO: Found link on eth0
Aug 12 14:49:58 netcfg[1663]: DEBUG: Commencing network autoconfiguration on eth0
==


  - what if you try to unload and reload the igb module? I've just
    checked that modprobe -r $foo and modprobe $foo work just fine
    from a console in the installer context.

This does not work ("ip link" shows NO_CARRIER): "modprobe -r igb ; modprobe igb ; ip link set up eth0" But with a delay of a couple seconds between loading the driver and activating the interface it does work most of the time, but not always either: "modprobe -r igb ; modprobe igb ; sleep 2 ; ip link set up eth0" So it seems that the module is not ready for action instantly, and there needs to be some kind of delay.

--
Yours sincerely,

Floris Bos



Reply to: