Bug 1798245

Summary: Network interface doesn't come up with kernel > kernel-5.4.12
Product: [Fedora] Fedora Reporter: Ldap Tester <ldap.tester>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 31CC: airlied, bskeggs, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, linville, masami256, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-25 22:30:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
journal requested in 7. none

Description Ldap Tester 2020-02-04 22:45:18 UTC 
Created attachment 1657685 [details]
journal requested in 7.

1. Please describe the problem:
Booting with kernels > 5.4.12, the network interface doesn't come up. Everything else works OK.

2. What is the Version-Release number of the kernel:
kernel-5.4.13-201.fc31.x86_64 and newer

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes. It worked with kernel-5.4.12-100.fc30.x86_64. It did not work with kernel-5.4.13-201.fc31.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes.  Just boot with a kernel newer than 5.4.12


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Unable. There was a problem with the keys.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
No. I disabled the virtualbox modules.  Made no difference.


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.
OK. Attached.


With kernels kernel-5.4.13-201.fc31.x86_64, kernel-5.4.14-100.fc30.x86_64 and kernel-5.4.15-200.fc31.x86_64, the network interface doesn't come up after reboot.



ifconfig -a

enp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        ether 00:25:90:24:bb:f2  txqueuelen 1000  (Ethernet)
        RX packets 328  bytes 38967 (38.0 KiB)
        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 interrupt 16  memory 0xfbce0000-fbd00000  

enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:25:90:24:bb:f3  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 interrupt 16  memory 0xfbde0000-fbe00000  

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 1000  (Local Loopback)
        RX packets 208  bytes 18904 (18.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 208  bytes 18904 (18.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0



cat /etc/sysconfig/network-scripts/ifcfg-p49p1

UUID="65c7e31b-2918-8730-4558-30d2920b8ef2"
NM_CONTROLLED=yes
BOOTPROTO=none
DEVICE=p49p1
ONBOOT=yes
TYPE=Ethernet
IPADDR0=199.104.150.223
PREFIX0=24
GATEWAY0=199.104.150.1
DNS1=199.104.150.50
DNS2=128.196.100.19
DNS3=128.196.11.233
DEFROUTE=yes
IPV6INIT=no
USERCTL=no
IPV4_FAILURE_FATAL=no
NAME="System p49p1"
HWADDR=00:25:90:24:BB:F2



nmcli device show

GENERAL.DEVICE:                         enp1s0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:24:BB:F2
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               on

GENERAL.DEVICE:                         enp2s0
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:24:BB:F3
GENERAL.MTU:                            1500
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               off

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ::1/128, nh = ::, mt = 256



nmcli connection show

NAME          UUID                                  TYPE      DEVICE 
System p49p1  65c7e31b-2918-8730-4558-30d2920b8ef2  ethernet  --     
System p50p1  94412918-5983-f0da-c943-865f06863d3b  ethernet  --     



nmcli connection up "System p49p1"

Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged).



nmcli device connect enp1s0

Error: Failed to add/activate new connection: Connection 'enp1s0' is not available on device enp1s0 because device is strictly unmanaged
ifup p49p1
WARN      : [ifup] You are using 'ifup' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifup] 'network-scripts' will be removed from distribution in near future.
WARN      : [ifup] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged).



ifup enp1s0

WARN      : [ifup] You are using 'ifup' script provided by 'network-scripts', which are now deprecated.
WARN      : [ifup] 'network-scripts' will be removed from distribution in near future.
WARN      : [ifup] It is advised to switch to 'NetworkManager' instead - it provides 'ifup/ifdown' scripts as well.
Error: Connection activation failed: No suitable device found for this connection (device lo not available because device is strictly unmanaged).



If I reboot with kernel kernel-5.4.12-100.fc30.x86_64, the network interface comes up after reboot as expected.



ifconfig -a

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 1000  (Local Loopback)
        RX packets 80  bytes 7288 (7.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 80  bytes 7288 (7.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p49p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 199.104.150.223  netmask 255.255.255.0  broadcast 199.104.150.255
        inet6 fe80::225:90ff:fe24:bbf2  prefixlen 64  scopeid 0x20<link>
        ether 00:25:90:24:bb:f2  txqueuelen 1000  (Ethernet)
        RX packets 2609  bytes 284001 (277.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 1203  bytes 182854 (178.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xfbce0000-fbd00000  

p50p1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:25:90:24:bb:f3  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 interrupt 16  memory 0xfbde0000-fbe00000  



nmcli device show

GENERAL.DEVICE:                         p49p1
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:24:BB:F2
GENERAL.MTU:                            1500
GENERAL.STATE:                          100 (connected)
GENERAL.CONNECTION:                     System p49p1
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/1
WIRED-PROPERTIES.CARRIER:               on
IP4.ADDRESS[1]:                         199.104.150.223/24
IP4.GATEWAY:                            199.104.150.1
IP4.ROUTE[1]:                           dst = 199.104.150.0/24, nh = 0.0.0.0, mt = 100
IP4.ROUTE[2]:                           dst = 0.0.0.0/0, nh = 199.104.150.1, mt = 100
IP4.DNS[1]:                             199.104.150.50
IP4.DNS[2]:                             128.196.100.19
IP4.DNS[3]:                             128.196.11.233
IP6.ADDRESS[1]:                         fe80::225:90ff:fe24:bbf2/64
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ff00::/8, nh = ::, mt = 256, table=255
IP6.ROUTE[2]:                           dst = fe80::/64, nh = ::, mt = 256

GENERAL.DEVICE:                         p50p1
GENERAL.TYPE:                           ethernet
GENERAL.HWADDR:                         00:25:90:24:BB:F3
GENERAL.MTU:                            1500
GENERAL.STATE:                          20 (unavailable)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
WIRED-PROPERTIES.CARRIER:               off

GENERAL.DEVICE:                         lo
GENERAL.TYPE:                           loopback
GENERAL.HWADDR:                         00:00:00:00:00:00
GENERAL.MTU:                            65536
GENERAL.STATE:                          10 (unmanaged)
GENERAL.CONNECTION:                     --
GENERAL.CON-PATH:                       --
IP4.ADDRESS[1]:                         127.0.0.1/8
IP4.GATEWAY:                            --
IP6.ADDRESS[1]:                         ::1/128
IP6.GATEWAY:                            --
IP6.ROUTE[1]:                           dst = ::1/128, nh = ::, mt = 256



nmcli connection show

NAME          UUID                                  TYPE      DEVICE 
System p49p1  65c7e31b-2918-8730-4558-30d2920b8ef2  ethernet  p49p1  
System p50p1  94412918-5983-f0da-c943-865f06863d3b  ethernet  --     



I tried booting with enforcing = 0, but it made no difference.
Strangely, I have another machine configured virtually identically (hardware and software) does not exhibit this behavior and has no problem with 5.4.13
Comment 1 Ldap Tester 2020-02-05 04:52:00 UTC 
I managed to get kernel-5.5.0-0.rc6.git3.1.fc32.x86_64 installed. The network interface still doesn't come up.
Comment 2 Justin M. Forbes 2020-03-03 16:22:14 UTC 
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 31 kernel bugs.

Fedora 31 has now been rebased to 5.5.7-200.fc31.  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 32, and are still experiencing this issue, please change the version to Fedora 32.

If you experience different issues, please open a new bug report for those.
Comment 3 Justin M. Forbes 2020-03-25 22:30:12 UTC 
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.
Comment 4 Ldap Tester 2020-07-15 18:28:06 UTC 
I worked around the problem by changing the interface name from p49p1 to enp1s0.