On Sat, Feb 27, 2021, at 2:31 PM, Samuel Sieb wrote: > On 2/27/21 2:21 PM, Doug H. wrote: > > On Sat, Feb 27, 2021, at 2:12 PM, Samuel Sieb wrote: > >> On 2/27/21 9:50 AM, Doug H. wrote: > >>> I am having an odd problem with my ethernet port. I assume this came > >>> with a dnf update but that was some weeks ago so I can't help figure > >>> out what update might have done it. When first discovered I think I > >>> found that booting from an older kernel did not fix it. I assume that > >>> the physical interface is not the problem since a physical "bounce" > >>> always fixes it and it shows no other problems. To explain that... > >> > >> Given that an older kernel doesn't fix it, that suggests it might not > >> be > >> software. How does it get in this state? Is it random? Does it stop > >> working after a reboot or does it keep working after a reboot if it was > >> working before? What about a power cycle? > > > > It does not seem random and it does not stop working while the OS is running except that it does not work after boot/reboot until the first unclip/pull/push. Oh, and it does stay up/working on resume from suspend (should have noted that one, seems important). > > > > I did verify this morning that a cold boot does cause the problem. A reboot (warm) will also cause it. Note that the NIC lights do come on when the computer is turned on but then the lights go out at some point after the kernel is selected by grub. So it does seem that linux is doing it... > > Run "sudo journalctl -b" to see if there are any relevant logs. Also, > "sudo journalctl -fa" before replugging to see what happens. In reply to the question about wire corrosion: I have pulled/pushed the cable a *lot* in working with this and it works very well when it is working. The same cable works great with the alternate NIC. And I did boot to "sysrescue" and found the NIC with good carrier. On to answering the question from Samuel: I am not seeing much help in the "while bad" journal: # grep enp5s0 journalctl-b.while_not_working.txt Feb 27 14:52:58 wombat.wombatz.com kernel: r8169 0000:05:00.0 enp5s0: renamed from eth0 Feb 27 14:53:07 wombat.wombatz.com NetworkManager[1316]: <info> [1614466387.7201] manager: (enp5s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2) Feb 27 14:53:07 wombat.wombatz.com NetworkManager[1316]: <info> [1614466387.7216] device (enp5s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Feb 27 14:53:07 wombat.wombatz.com kernel: r8169 0000:05:00.0 enp5s0: Link is Down Here is what happened when I did the pull/push of the cable (I marked the spot where the pull and push happened... # journalctl -fa -- Logs begin at Thu 2020-10-01 08:01:38 PDT. -- Feb 27 14:53:55 wombat.wombatz.com systemd[1]: dnfdaemon.service: Consumed 4.964s CPU time. Feb 27 14:53:58 wombat.wombatz.com chronyd[1331]: Selected source 212.26.18.43 (2.fedora.pool.ntp.org) Feb 27 14:53:58 wombat.wombatz.com chronyd[1331]: System clock TAI offset set to 37 seconds Feb 27 14:53:59 wombat.wombatz.com chronyd[1331]: Selected source 217.198.219.102 (2.fedora.pool.ntp.org) Feb 27 14:54:05 wombat.wombatz.com systemd[1]: NetworkManager-dispatcher.service: Succeeded. Feb 27 14:54:05 wombat.wombatz.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 27 14:54:10 wombat.wombatz.com systemd[1]: pcscd.service: Succeeded. Feb 27 14:54:10 wombat.wombatz.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=pcscd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 27 14:55:03 wombat.wombatz.com chronyd[1331]: Source 84.16.73.33 replaced with 2607:5300:201:3100::345c (2.fedora.pool.ntp.org) Feb 27 14:55:03 wombat.wombatz.com chronyd[1331]: Selected source 184.105.182.7 (2.fedora.pool.ntp.org) Feb 27 14:56:12 wombat.wombatz.com systemd[1636]: Starting Mark boot as successful... Feb 27 14:56:12 wombat.wombatz.com systemd[1636]: grub-boot-success.service: Succeeded. Feb 27 14:56:12 wombat.wombatz.com systemd[1636]: Finished Mark boot as successful. Here is the wire pull/push: Feb 27 14:56:28 wombat.wombatz.com kernel: r8169 0000:05:00.0 enp5s0: Link is Up - 100Mbps/Full - flow control off Feb 27 14:56:28 wombat.wombatz.com kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp5s0: link becomes ready Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5430] device (enp5s0): carrier: link connected Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5436] device (enp5s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5451] policy: auto-activating connection 'Ether link to Pi' (837b199c-531d-3727-a66f-12a8096b570d) Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5460] device (enp5s0): Activation: starting connection 'Ether link to Pi' (837b199c-531d-3727-a66f-12a8096b570d) Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5463] device (enp5s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5482] device (enp5s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5493] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com avahi-daemon[1321]: Joining mDNS multicast group on interface enp5s0.IPv4 with address 192.168.11.4. Feb 27 14:56:28 wombat.wombatz.com avahi-daemon[1321]: New relevant interface enp5s0.IPv4 for mDNS. Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5519] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com avahi-daemon[1321]: Registering new address record for 192.168.11.4 on enp5s0.IPv4. Feb 27 14:56:28 wombat.wombatz.com systemd[1]: Starting Network Manager Script Dispatcher Service... Feb 27 14:56:28 wombat.wombatz.com systemd[1]: Started Network Manager Script Dispatcher Service. Feb 27 14:56:28 wombat.wombatz.com audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5799] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5803] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') Feb 27 14:56:28 wombat.wombatz.com NetworkManager[1316]: <info> [1614466588.5823] device (enp5s0): Activation: successful, device activated. Feb 27 14:56:28 wombat.wombatz.com systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive. Feb 27 14:56:28 wombat.wombatz.com systemd[1]: squid.service: Unit cannot be reloaded because it is inactive. Feb 27 14:56:30 wombat.wombatz.com avahi-daemon[1321]: Joining mDNS multicast group on interface enp5s0.IPv6 with address fe80::226:18ff:fe3a:2a1b. Feb 27 14:56:30 wombat.wombatz.com avahi-daemon[1321]: New relevant interface enp5s0.IPv6 for mDNS. Feb 27 14:56:30 wombat.wombatz.com avahi-daemon[1321]: Registering new address record for fe80::226:18ff:fe3a:2a1b on enp5s0.*. Feb 27 14:56:39 wombat.wombatz.com systemd[1]: NetworkManager-dispatcher.service: Succeeded. Feb 27 14:56:39 wombat.wombatz.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' -- Doug Herr fedoraproject.org@xxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
