Bug 1138951 - Network Interface failing to start
Summary: Network Interface failing to start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-06 17:06 UTC by Carlos Guidugli
Modified: 2014-09-06 20:49 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-06 20:49:57 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
journalctl -b -u NetworkManager & grep -e NetworkManager -e p3p1 -e igb -e firewalld /var/log/messages (480.00 KB, application/octet-stream)
2014-09-06 17:06 UTC, Carlos Guidugli 		no flags Details
View All

Description Carlos Guidugli 2014-09-06 17:06:28 UTC 
Created attachment 935041 [details]
journalctl -b -u NetworkManager & grep -e NetworkManager -e p3p1 -e igb -e firewalld /var/log/messages

Description of problem:

Whenever I do a fresh install of Fedora 20, both network cards works well. For some reason, using the latest packages, the interface p3p1 (Intel I211) fails sometimes. I did reinstall Fedora several times so far since I don't know how to fix the problem. 
Here I will describe one case that happened, although this problem also happened without those packages: once I installed xbmc and, after reboot, the p3p1 network stopped to work. When I did a yum history undo xx, the network worked again after reboot. So, I installed again xbmc, which made the problem reappear, and removed the dependencies one by one, to try to determine which package could be causing the problem. To my surprise, I removed them all and the problem persisted. Then, I installed again xbmc, rebooted, did a yum history undo, rebooted, then the network worked again.
After some time, the network stopped working for good. Had to reinstall fedora again.
In my latest install, the network was working fine but now, sometimes it boots fine, sometimes doesn't.
I am looking at the logs but I am not able to determine the problem.
Please help. I love Fedora and this is kind of a big problem for me.

Version-Release number of selected component (if applicable):


How reproducible: Hard to reproduce


Steps to Reproduce:
1. Install xbmc then reboot --> network stops working
2. yum history undo xx, then reboot -> network works again
3. After some time, the network does not work at all

Actual results:


Expected results:


Additional info:
[root@matrix ~]# lspci
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1c.4 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation Z87 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii PRO [Radeon R9 290]
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Device aac8
04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)
05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
06:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 01)

-------------------------------------------------------------------

[root@matrix ~]# lspci -n
00:00.0 0600: 8086:0c00 (rev 06)
00:01.0 0604: 8086:0c01 (rev 06)
00:02.0 0300: 8086:0412 (rev 06)
00:03.0 0403: 8086:0c0c (rev 06)
00:14.0 0c03: 8086:8c31 (rev 04)
00:16.0 0780: 8086:8c3a (rev 04)
00:19.0 0200: 8086:153b (rev 04)
00:1a.0 0c03: 8086:8c2d (rev 04)
00:1b.0 0403: 8086:8c20 (rev 04)
00:1c.0 0604: 8086:8c10 (rev d4)
00:1c.1 0604: 8086:8c12 (rev d4)
00:1c.2 0604: 8086:8c14 (rev d4)
00:1c.3 0604: 8086:8c16 (rev d4)
00:1c.4 0604: 8086:8c18 (rev d4)
00:1d.0 0c03: 8086:8c26 (rev 04)
00:1f.0 0601: 8086:8c44 (rev 04)
00:1f.2 0106: 8086:8c02 (rev 04)
00:1f.3 0c05: 8086:8c22 (rev 04)
01:00.0 0300: 1002:67b1
01:00.1 0403: 1002:aac8
04:00.0 0106: 1b21:0612 (rev 01)
05:00.0 0200: 8086:1539 (rev 03)
06:00.0 0106: 1b21:0612 (rev 01)

--------------------------------------------------------------------

[root@matrix ~]# cat /proc/cmdline 
BOOT_IMAGE=/vmlinuz-3.15.10-201.fc20.x86_64 root=/dev/mapper/fedora_matrix-root ro rd.luks.uuid=luks-3b74084d-7c63-47b4-ba1c-1397ff9ba72f vconsole.font=latarcyrheb-sun16 rd.lvm.lv=fedora_matrix/root rd.lvm.lv=fedora_matrix/swap rhgb quiet intel_iommu=on,igfx_off pci-stub.ids=1002:67b1,1002:aac8,8086:8c20,8086:8c2d,1b21:0612

----------------------------------------------------------------------

[root@matrix ~]# dmesg | grep -e 0000:00:19.0 -e e1000e -e igb -e 0000:05:00.0
[    0.178108] pci 0000:00:19.0: [8086:153b] type 00 class 0x020000
[    0.178122] pci 0000:00:19.0: reg 0x10: [mem 0xf1300000-0xf131ffff]
[    0.178128] pci 0000:00:19.0: reg 0x14: [mem 0xf133d000-0xf133dfff]
[    0.178135] pci 0000:00:19.0: reg 0x18: [io  0xf080-0xf09f]
[    0.178184] pci 0000:00:19.0: PME# supported from D0 D3hot D3cold
[    0.178213] pci 0000:00:19.0: System wakeup disabled by ACPI
[    0.183394] pci 0000:05:00.0: [8086:1539] type 00 class 0x020000
[    0.183412] pci 0000:05:00.0: reg 0x10: [mem 0xf1100000-0xf111ffff]
[    0.183433] pci 0000:05:00.0: reg 0x18: [io  0xc000-0xc01f]
[    0.183444] pci 0000:05:00.0: reg 0x1c: [mem 0xf1120000-0xf1123fff]
[    0.183588] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
[   17.618646] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k
[   17.618649] e1000e: Copyright(c) 1999 - 2014 Intel Corporation.
[   17.618771] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   17.618787] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
[   17.638703] igb: Intel(R) Gigabit Ethernet Network Driver - version 5.0.5-k
[   17.638705] igb: Copyright (c) 2007-2014 Intel Corporation.
[   17.638738] igb 0000:05:00.0: enabling device (0000 -> 0002)
[   17.639216] igb 0000:05:00.0: irq 48 for MSI/MSI-X
[   17.639222] igb 0000:05:00.0: irq 49 for MSI/MSI-X
[   17.639228] igb 0000:05:00.0: irq 50 for MSI/MSI-X
[   17.639233] igb 0000:05:00.0: irq 51 for MSI/MSI-X
[   17.639237] igb 0000:05:00.0: irq 52 for MSI/MSI-X
[   17.668505] igb 0000:05:00.0: added PHC on eth0
[   17.668508] igb 0000:05:00.0: Intel(R) Gigabit Ethernet Network Connection
[   17.668509] igb 0000:05:00.0: eth0: (PCIe:2.5Gb/s:Width x1) bc:5f:f4:c8:6f:a1
[   17.668511] igb 0000:05:00.0: eth0: PBA No: FFFFFF-0FF
[   17.668512] igb 0000:05:00.0: Using MSI-X interrupts. 2 rx queue(s), 2 tx queue(s)
[   17.794536] e1000e 0000:00:19.0 eth1: registered PHC clock
[   17.794541] e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) bc:5f:f4:c8:6f:d2
[   17.794542] e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection
[   17.794580] e1000e 0000:00:19.0 eth1: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[   28.639235] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
[   28.739413] e1000e 0000:00:19.0: irq 47 for MSI/MSI-X
[   31.674376] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

-------------------------------------------------------------

[root@matrix ~]# cat /etc/sysconfig/network-scripts/ifcfg-p3p1 
TYPE="Ethernet"
BOOTPROTO="dhcp"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="no"
IPV6INIT="yes"
IPV6_AUTOCONF="yes"
IPV6_DEFROUTE="yes"
IPV6_PEERDNS="yes"
IPV6_PEERROUTES="yes"
IPV6_FAILURE_FATAL="no"
NAME="p3p1"
UUID="16ad3601-52b9-4eee-80ee-d190332d015c"
ONBOOT="yes"
HWADDR="BC:5F:F4:C8:6F:A1"
PEERDNS="yes"
PEERROUTES="yes"

-----------------------------------------------------------------

[root@matrix ~]# yum info NetworkManager
Loaded plugins: langpacks, refresh-packagekit
Installed Packages
Name        : NetworkManager
Arch        : x86_64
Epoch       : 1
Version     : 0.9.9.0
Release     : 43.git20131003.fc20
Size        : 4.7 M
Repo        : installed
From repo   : updates
Summary     : Network connection manager and user applications
URL         : http://www.gnome.org/projects/NetworkManager/
Licence     : GPLv2+
Description : NetworkManager is a system network service that manages your network devices
            : and connections, attempting to keep active network connectivity when available.
            : It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE devices, and
            : provides VPN integration with a variety of different VPN services.

Available Packages
Name        : NetworkManager
Arch        : i686
Epoch       : 1
Version     : 0.9.9.0
Release     : 43.git20131003.fc20
Size        : 1.2 M
Repo        : updates/20/x86_64
Summary     : Network connection manager and user applications
URL         : http://www.gnome.org/projects/NetworkManager/
Licence     : GPLv2+
Description : NetworkManager is a system network service that manages your network devices
            : and connections, attempting to keep active network connectivity when available.
            : It manages ethernet, WiFi, mobile broadband (WWAN), and PPPoE devices, and
            : provides VPN integration with a variety of different VPN services.


-----------------------------------------------------------------------

[root@matrix ~]# ifconfig -a
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.100  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::be5f:f4ff:fec8:6fd2  prefixlen 64  scopeid 0x20<link>
        ether bc:5f:f4:c8:6f:d2  txqueuelen 1000  (Ethernet)
        RX packets 11048  bytes 8439511 (8.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 9119  bytes 1361726 (1.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xf1300000-f1320000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 10  bytes 940 (940.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 10  bytes 940 (940.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p3p1: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether bc:5f:f4:c8:6f:a1  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device memory 0xf1100000-f111ffff  

virbr0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
        ether 52:54:00:c7:92:f5  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.200.1  netmask 255.255.255.0  broadcast 192.168.200.255
        ether 52:54:00:35:78:b6  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr2: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.55.1  netmask 255.255.255.0  broadcast 192.168.55.255
        ether 52:54:00:65:32:8f  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr0-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:c7:92:f5  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr1-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:35:78:b6  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

virbr2-nic: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 52:54:00:65:32:8f  txqueuelen 500  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)

----------------------------------------------------------------------
[root@matrix ~]# ifup p3p1 
Error: Connection activation failed.

----------------------------------------------------------------------
Comment 1 Carlos Guidugli 2014-09-06 19:53:26 UTC 
After hours looking at logs and trying things I remembered that I once developed a script that do some power saving settings. There are two related to this ethernet port:

echo 'auto' > '/sys/bus/pci/devices/0000:05:00.0/power/control'
ethtool -s p3p1 wol d

After I disabled these options, the network started working again. It is very odd because the other network card works great. 

Anyway, will continue to perform more tests.
Comment 2 Carlos Guidugli 2014-09-06 20:42:39 UTC 
I think I understand what is happening. My script was set to run via systemd and waiting only syslogd. So, when the script runs before the network is up, it breaks the igb interface, although e1000 works fine. Since there isn't any dependency set, sometimes the script would run before and sometimes after. 
I did some tests setting the script to run before network is up, and the igb interface always failed. Then, I setup the script to run after the network is ready, and the igb network worked fine.
So, it would be helpful if the igb driver had the same resilience of e1000, but this is not a bug for network manager.
Note You need to log in before you can comment on or make changes to this bug.