Bug 1378210 - Intel I210 NIC fails to initialise after upgrade
Summary: Intel I210 NIC fails to initialise after upgrade
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-21 20:23 UTC by 2owen.thomas
Modified: 2016-10-24 11:11 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-24 11:11:22 UTC
Type: ---


Attachments (Terms of Use)

Description 2owen.thomas 2016-09-21 20:23:04 UTC
User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:48.0) Gecko/20100101 Firefox/48.0
Build Identifier: 

I was previously running Fedora 23 and after upgrading to kernel 4.6 (previously working on 4.5.4 if I remember correctly) the Intel NICs fail to initialise their drivers and cannot be observed in dmesg. However an lspci shows they are visible to the OS. I have since upgraded to Fedora 24 (with the use of the 4.5 kernel) in the hopes that this bug had been fixed but to no avail. I have searched for similar bugs and couldn't find anything. lsmod shows the igb module has been loaded however nothing is using it. I am currently using a USB ethernet adapter as a work around in the interim.

Reproducible: Always

Steps to Reproduce:
1. Turn on computer
2. Log in
3. No network interfaces shown in Network Manager
4. No network interfaces shown in nmcli or ifconfig
Actual Results:  
No network interface card and thus no network connection

Expected Results:  
Functioning network connectivity

[owen@oz-srv ~]$ lspci | grep Network
04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03)
[owen@oz-srv ~]$ lsmod | grep igb
igb                   196608  0
ptp                    20480  1 igb
dca                    16384  1 igb
i2c_algo_bit           16384  1 igb

[owen@oz-srv ~]$ dmesg | grep thernet
[    1.819864] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.3.0-k
[    1.846028] usb 5-2: Product: Apple USB Ethernet Adapter
[    5.780734] asix 5-2:1.0 eth0: register 'asix' at usb-0000:08:00.0-2, ASIX AX88772 USB 2.0 Ethernet, f4:f9:51:f1:36:83

[owen@oz-srv ~]$ nmcli dev status
DEVICE    TYPE      STATE      CONNECTION 
enp8s0u2  ethernet  connected  enp6s0     
lo        loopback  unmanaged  --  

[owen@oz-srv ~]$ systemctl status network
● network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: inactive (dead)
     Docs: man:systemd-sysv-generator(8)

[owen@oz-srv ~]$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2016-09-21 20:52:06 BST; 12min ago
     Docs: man:NetworkManager(8)
 Main PID: 1019 (NetworkManager)
    Tasks: 4 (limit: 512)
   CGroup: /system.slice/NetworkManager.service
           ├─1019 /usr/sbin/NetworkManager --no-daemon
           └─1172 /sbin/dhclient -d -q -sf /usr/libexec/nm-dhcp-helper -pf /var/run/dhclient-enp8s0u2.pid -lf /var/lib/NetworkManager/dhclient-8f9baa70-1a1f-4311-818b-ec0c73846d8d-enp8s0u2.lea

Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0208] dhcp4 (enp8s0u2): state changed unknown -> bound
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0226] device (enp8s0u2): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0349] device (enp8s0u2): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0353] device (enp8s0u2): state change: secondaries -> activated (reason 'none') [90 100 0]
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0354] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0372] manager: NetworkManager state is now CONNECTED_SITE
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0373] policy: set 'enp6s0' (enp8s0u2) as default for IPv4 routing and DNS
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0386] device (enp8s0u2): Activation: successful, device activated.
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.0389] manager: startup complete
Sep 21 20:52:13 oz-srv.julien NetworkManager[1019]: <info>  [1474487533.2606] manager: NetworkManager state is now CONNECTED_GLOBAL

[owen@oz-srv network-scripts]$ sudo ifup enp4s0
Error: Connection activation failed: No suitable device found for this connection.
[owen@oz-srv network-scripts]$ sudo ifup enp5s0
Error: Connection activation failed: No suitable device found for this connection.

Comment 1 Laura Abbott 2016-09-23 19:16:48 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.
 
Fedora 24 has now been rebased to 4.7.4-200.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 25, and are still experiencing this issue, please change the version to Fedora 25.
 
If you experience different issues, please open a new bug report for those.

Comment 2 2owen.thomas 2016-10-23 11:23:03 UTC
Hi Laura,

I have finally gotten around to updating my system and the 4.7.4-200.fc24 kernel update has now fixed this issue for me.

Owen T


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