Hi,
I am currently running Fedora 28. I did a dnf upgrade this morning, and
it upgraded the kernel to 4.19.
Linux morgoth.localdomain 4.19.4-200.fc28.x86_64
After rebooting to the new kernel, I found I could not connect to
anything over ethernet. I rebooted to the previous kernel, which was 4.18.
Linux morgoth.localdomain 4.18.18-200.fc28.x86_64
My connection worked again. I went looking in the journal for entries
related to the ifname. Under the 4.19 kernel, I found the following
entries(sorry for the wrapping, I can't seem to turn it off).
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:05:16 EST. --
Nov 29 13:58:38 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 13:59:29 morgoth.localdomain NetworkManager[920]: <info>
[1543517969.1764] ifcfg-rh: new connection
/etc/sysconfig/network-scripts/ifcfg-enp6s0
(8719d767-2f8e-3fc1-a9e2-522bde03a5a7,"enp6s0")
Nov 29 13:59:30 morgoth.localdomain NetworkManager[920]: <info>
[1543517970.4361] manager: (enp6s0): new Ethernet device
(/org/freedesktop/NetworkManager/Devices/2)
Nov 29 13:59:30 morgoth.localdomain NetworkManager[920]: <info>
[1543517970.4371] device (enp6s0): state change: unmanaged ->
unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 13:59:30 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 13:59:30 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
For the 4.18 kernel, I get the following, plus many more lines after it
is connected.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:10:03 EST. --
Nov 29 14:08:04 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 14:08:59 morgoth.localdomain NetworkManager[930]: <info>
[1543518539.5379] ifcfg-rh: new connection
/etc/sysconfig/network-scripts/ifcfg-enp6s0
(8719d767-2f8e-3fc1-a9e2-522bde03a5a7,"enp6s0")
Nov 29 14:09:00 morgoth.localdomain NetworkManager[930]: <info>
[1543518540.6720] manager: (enp6s0): new Ethernet device
(/org/freedesktop/NetworkManager/Devices/2)
Nov 29 14:09:00 morgoth.localdomain NetworkManager[930]: <info>
[1543518540.6731] device (enp6s0): state change: unmanaged ->
unavailable (reason 'managed', sys-iface-state: 'external')
Nov 29 14:09:00 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 14:09:00 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link down
Nov 29 14:09:00 morgoth.localdomain kernel: IPv6: ADDRCONF(NETDEV_UP):
enp6s0: link is not ready
Nov 29 14:09:02 morgoth.localdomain NetworkManager[930]: <info>
[1543518542.3332] device (enp6s0): carrier: link connected
Nov 29 14:09:02 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link up
Nov 29 14:09:02 morgoth.localdomain kernel: IPv6:
ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Looking at these, I did a search for r8169. The 4.19 kernel gives the
following.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:46:52 EST. --
Nov 29 13:58:37 morgoth.localdomain kernel: libphy: r8169: probed
Nov 29 13:58:37 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
RTL8168c/8111c, a4:ba:db:f9:fa:9d, XID 3c4000c0, IRQ 33
Nov 29 13:58:37 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
jumbo features [frames: 6128 bytes, tx checksumming: ko]
Nov 29 13:58:38 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 13:59:30 morgoth.localdomain kernel: Generic PHY r8169-600:00:
attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-600:00,
irq=IGNORE)
The 4.18 kernel shows the following.
-- Logs begin at Thu 2018-05-10 18:16:12 EDT, end at Thu 2018-11-29
14:46:52 EST. --
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 Gigabit Ethernet
driver 2.3LK-NAPI loaded
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0: can't
disable ASPM; OS doesn't have ASPM control
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
RTL8168c/8111c, a4:ba:db:f9:fa:9d, XID 3c4000c0, IRQ 33
Nov 29 14:08:03 morgoth.localdomain kernel: r8169 0000:06:00.0 eth0:
jumbo features [frames: 6128 bytes, tx checksumming: ko]
Nov 29 14:08:04 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
renamed from eth0
Nov 29 14:09:00 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link down
Nov 29 14:09:02 morgoth.localdomain kernel: r8169 0000:06:00.0 enp6s0:
link up
Is there something obvious to do that will get the 4.19 kernel
connecting? Is there someother information that would help find the
problem? Thanks for any help.
--
Lester M Petrie
Show replies by date