Network stops working after system being turned off for a few hours

Bedna · 2025-11-14 14:35:55

I think this is hardware or kernel related, because `systemctl soft-reboot` does not solve the issue, but a "hard" reboot does. And I have to do that every time I start up my computer after it being turned off during the night.

Possibly related: For more than a year I had a "bug" where my boot process froze for about a minute, turned out it was my wifi card on my mobo and in extension the usb ports it was connected to never actually shut down. After removing all power to my computer for about 10 minutes, the issue was fixed. I mention this because they are both network related.
Oddly I found the solution on ubuntu forums, I just provide this as reference to my old issue: https://askubuntu.com/questions/1538921 … em-startup
My wifi works perfectly, now my enp is not working properly, but this issue did not start immediately after I fixed the wifi, so probably not related but wanted to include it here anyway "just in case".

The issue:

This issue ONLY shows up each time the computer has been turned of for a longer period of time. Letting it be turned off for 10 minutes (with or without power connected to it, ie the solution to my wifi problem) does not trigger this issue, I experience this every time I start my computer after it being shutdown during the night.
At first, the network functions normally, but after 30s to one minute, it suddenly stops working. I can not even ping my router, my network is completely dead.
The strange thing, with my limited knowledge I can not find anything in logs or dmesg that point me to a solution.

I have ipv6 disabled as kernel parameter, and it has been since I installed arch so that is probably not related, but does warn me in logs but that has always been the case and has not caused any issues in the past.

Logs I think is relevant

I copied these logs a few days ago, but nothing have changed other than dates, so I copy paste from the notes I made earlier.

Lets start with lspci, this does not change from working to broken condition.

# filtered out only network cards, there will be enough text as is in these logs.
lspci

0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)  
0f:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter


sudo lspci -vvvs 0e:00.0

0e:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)  
       Subsystem: Gigabyte Technology Co., Ltd Device e000  
       Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+  
       Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-  
       Latency: 0, Cache Line Size: 64 bytes  
       Interrupt: pin A routed to IRQ 37  
       IOMMU group: 20  
       Region 0: I/O ports at e000 [size=256]  
       Region 2: Memory at f6600000 (64-bit, non-prefetchable) [size=64K]  
       Region 4: Memory at f6610000 (64-bit, non-prefetchable) [size=16K]  
       Capabilities: [40] Power Management version 3  
               Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)  
               Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-  
       Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+  
               Address: 0000000000000000  Data: 0000  
               Masking: 00000000  Pending: 00000000  
       Capabilities: [70] Express (v2) Endpoint, IntMsgNum 1  
               DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us  
                       ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 26W TEE-IO-  
               DevCtl: CorrErr+ NonFatalErr+ FatalErr+ UnsupReq+  
                       RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-  
                       MaxPayload 128 bytes, MaxReadReq 4096 bytes  
               DevSta: CorrErr+ NonFatalErr+ FatalErr- UnsupReq- AuxPwr+ TransPend-  
               LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s unlimited, L1 <64us  
                       ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+  
               LnkCtl: ASPM Disabled; RCB 64 bytes, LnkDisable- CommClk+  
                       ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- FltModeDis-  
               LnkSta: Speed 5GT/s, Width x1  
                       TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-  
               DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+  
                        10BitTagComp- 10BitTagReq- OBFF Via message/WAKE#, ExtFmt- EETLPPrefix-  
                        EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-  
                        FRS- TPHComp+ ExtTPHComp-  
                        AtomicOpsCap: 32bit- 64bit- 128bitCAS-  
               DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-  
                        AtomicOpsCtl: ReqEn-  
                        IDOReq- IDOCompl- LTR+ EmergencyPowerReductionReq-  
                        10BitTagReq- OBFF Disabled, EETLPPrefixBlk-  
               LnkCap2: Supported Link Speeds: 2.5-5GT/s, Crosslink- Retimer- 2Retimers- DRS-  
               LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-  
                        Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-  
                        Compliance Preset/De-emphasis: -6dB de-emphasis, 0dB preshoot  
               LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- EqualizationPhase1-  
                        EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-  
                        Retimer- 2Retimers- CrosslinkRes: unsupported, FltMode-  
       Capabilities: [b0] MSI-X: Enable+ Count=32 Masked-  
               Vector table: BAR=4 offset=00000000  
               PBA: BAR=4 offset=00000800  
       Capabilities: [d0] Vital Product Data  
pcilib: sysfs_read_vpd: read failed: No such device  
               Not readable  
       Capabilities: [100 v2] Advanced Error Reporting  
               UESta:  DLP- SDES- TLP- FCP- CmpltTO+ CmpltAbrt- UnxCmplt- RxOF- MalfTLP-  
                       ECRC- UnsupReq- ACSViol- UncorrIntErr- BlockedTLP- AtomicOpBlocked- TLPBlockedErr-  
                       PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-  
               UEMsk:  DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP-  
                       ECRC- UnsupReq- ACSViol- UncorrIntErr+ BlockedTLP- AtomicOpBlocked- TLPBlockedErr-  
                       PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-  
               UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+  
                       ECRC- UnsupReq- ACSViol- UncorrIntErr+ BlockedTLP- AtomicOpBlocked- TLPBlockedErr-  
                       PoisonTLPBlocked- DMWrReqBlocked- IDECheck- MisIDETLP- PCRC_CHECK- TLPXlatBlocked-  
               CESta:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CorrIntErr- HeaderOF-  
               CEMsk:  RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ CorrIntErr+ HeaderOF+  
               AERCap: First Error Pointer: 0e, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ ECRCChkEn-  
                       MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-  
               HeaderLog: 00000000 00000000 00000000 00000000  
       Capabilities: [148 v1] Virtual Channel  
               Caps:   LPEVC=0 RefClk=100ns PATEntryBits=1  
               Arb:    Fixed- WRR32- WRR64- WRR128-  
               Ctrl:   ArbSelect=Fixed  
               Status: InProgress-  
               VC0:    Caps:   PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-  
                       Arb:    Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-  
                       Ctrl:   Enable+ ID=0 ArbSelect=Fixed TC/VC=ff  
                       Status: NegoPending- InProgress-  
       Capabilities: [168 v1] Device Serial Number 01-00-00-00-68-4c-e0-00  
       Capabilities: [178 v1] Transaction Processing Hints  
               No steering table available  
       Capabilities: [204 v1] Latency Tolerance Reporting  
               Max snoop latency: 0ns  
               Max no snoop latency: 0ns  
       Capabilities: [20c v1] L1 PM Substates  
               L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+  
                         PortCommonModeRestoreTime=150us PortTPowerOnTime=150us  
               L1SubCtl1: PCI-PM_L1.2- PCI-PM_L1.1- ASPM_L1.2- ASPM_L1.1-  
                          T_CommonMode=0us LTR1.2_Threshold=306176ns  
               L1SubCtl2: T_PwrOn=150us  
       Capabilities: [21c v1] Vendor Specific Information: ID=0002 Rev=4 Len=100 <?>  
       Kernel driver in use: r8169  
       Kernel modules: r8169

Using ethtool also does not change weather the network is broken or not, but I include it for clarity:

sudo ethtool enp14s0

Settings for enp14s0:  
       Supported ports: [ TP    MII ]  
       Supported link modes:   10baseT/Half 10baseT/Full  
                               100baseT/Half 100baseT/Full  
                               1000baseT/Full  
                               2500baseT/Full  
       Supported pause frame use: Symmetric Receive-only  
       Supports auto-negotiation: Yes  
       Supported FEC modes: Not reported  
       Advertised link modes:  10baseT/Half 10baseT/Full  
                               100baseT/Half 100baseT/Full  
                               1000baseT/Full  
                               2500baseT/Full  
       Advertised pause frame use: Symmetric Receive-only  
       Advertised auto-negotiation: Yes  
       Advertised FEC modes: Not reported  
       Link partner advertised link modes:  10baseT/Half 10baseT/Full  
                                            100baseT/Half 100baseT/Full  
                                            1000baseT/Full  
       Link partner advertised pause frame use: No  
       Link partner advertised auto-negotiation: Yes  
       Link partner advertised FEC modes: Not reported  
       Speed: 1000Mb/s  
       Duplex: Full  
       Auto-negotiation: on  
       master-slave cfg: preferred slave  
       master-slave status: slave  
       Port: Twisted Pair  
       PHYAD: 0  
       Transceiver: internal  
       MDI-X: Unknown  
       Supports Wake-on: pumbg  
       Wake-on: g  
       Link detected: yes

dmesg sometimes shows this after network stops working, but not every time, could be related?

r8169 0000:0e:00.0 enp14s0: NETDEV WATCHDOG: CPU: 17: transmit queue 0 timed out 5120 ms
r8169 0000:0e:00.0 enp14s0: ASPM disabled on Tx timeout

Journalctl only shows the errors I normally have, nothing changes after network dies. (ipv6 disabled as kernel parameter in grub)

sudo journalctl -b0 -p3

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.  
Nov 07 10:58:12 archlinux kernel: hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)  
Nov 07 10:58:12 archlinux kernel:    
Nov 07 10:58:21 bednaArch rpcbind[1094]: cannot create socket for udp6  
Nov 07 10:58:21 bednaArch rpcbind[1094]: cannot create socket for tcp6  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:21 bednaArch rpc.mountd[1090]: Could not make a socket: (97) Address family not supported by protocol  
Nov 07 10:58:24 bednaArch rpc.statd[1125]: Failed to create listener xprt (statd, 1, udp6)  
Nov 07 10:58:24 bednaArch rpc.statd[1125]: Failed to create listener xprt (statd, 1, tcp6)

NetworkManager.service:
After failure:

sudo journalctl -u NetworkManager.service -e --no-pager

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.  
Nov 07 10:58:18 bednaArch systemd[1]: Starting Network Manager...  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6387] NetworkManager (version 1.54.1-1) is starting... (boot:ac5a6938-be26-4c33-a54e-9993e4beec14)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6388] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/20-connectivity.conf  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6421] manager[0x5655489505a0]: monitoring kernel firmware directory '/lib/firmware'.  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6744] hostname: hostname: using hostnamed  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6744] hostname: static hostname changed from (none) to "bednaArch"  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6746] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6762] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:07.0/0000:0f:  
00.0/ieee80211/phy0/rfkill1) (driver mt7921e)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6765] manager[0x5655489505a0]: rfkill: Wi-Fi hardware radio set disabled  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6765] manager[0x5655489505a0]: rfkill: WWAN hardware radio set enabled  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6779] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-adsl.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6803] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-bluetooth.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6812] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-ovs.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6870] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-team.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6876] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wifi.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6878] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wwan.so)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6879] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6880] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6880] manager: Networking is enabled by state file  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6883] settings: Loaded settings plugin: keyfile (internal)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6895] dhcp: init: Using DHCP client 'internal'  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6896] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6899] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6900] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6902] device (lo): Activation: starting connection 'lo' (c1cde8a8-1c5e-4d5a-bb92-37cdb2f896eb)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6907] manager: (enp14s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.6908] device (enp14s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8833] device (wlan0): driver supports Access Point (AP) mode  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8836] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8837] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8839] device (wlan0): set-hw-addr: set MAC address to D6:7F:96:0C:D7:69 (scanning)  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8842] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"  
Nov 07 10:58:18 bednaArch systemd[1]: Started Network Manager.  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8845] ovsdb: disconnected from ovsdb  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8846] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8847] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8847] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8849] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8855] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8856] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')  
Nov 07 10:58:18 bednaArch NetworkManager[811]: <info>  [1762509498.8858] device (lo): Activation: successful, device activated.  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5662] device (enp14s0): carrier: link connected  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5664] device (enp14s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5665] policy: auto-activating connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5666] device (enp14s0): Activation: starting connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5667] device (enp14s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5667] manager: NetworkManager state is now CONNECTING  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5667] device (enp14s0): state change: prepare -> config (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5670] device (enp14s0): state change: config -> ip-config (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5671] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.5801] dhcp4 (enp14s0): state changed new lease, address=192.168.99.10, acd pending  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.7653] dhcp4 (enp14s0): state changed new lease, address=192.168.99.10  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.7656] policy: set 'Wired connection 1' (enp14s0) as default for IPv4 routing and DNS  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.7994] device (enp14s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.7999] device (enp14s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.8000] device (enp14s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.8001] manager: NetworkManager state is now CONNECTED_SITE  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.8002] device (enp14s0): Activation: successful, device activated.  
Nov 07 10:58:21 bednaArch NetworkManager[811]: <info>  [1762509501.8005] manager: startup complete  
Nov 07 10:58:22 bednaArch NetworkManager[811]: <info>  [1762509502.0604] manager: NetworkManager state is now CONNECTED_GLOBAL  
Nov 07 10:58:41 bednaArch NetworkManager[811]: <info>  [1762509521.9034] agent-manager: agent[97d01eb657a3adfc,:1.31/org.kde.plasma.networkmanagement/1000]: agent registered  
Nov 07 11:03:51 bednaArch NetworkManager[811]: <info>  [1762509831.9628] manager: NetworkManager state is now CONNECTED_SITE

After a restart of NetworkManager.service (only new lines after restarting the service)

Nov 07 11:27:54 bednaArch systemd[1]: Stopping Network Manager...  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3443] caught SIGTERM, shutting down normally.  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3446] dhcp4 (enp14s0): canceled DHCP transaction  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3446] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3446] dhcp4 (enp14s0): state changed no lease  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3447] device (wlan0): state change: unavailable -> unmanaged (reason 'unmanaged-quitting', managed-type: 'full')  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3449] device (wlan0): set-hw-addr: reset MAC address to AC:50:DE:9E:A0:4D (unmanage)  
Nov 07 11:27:54 bednaArch NetworkManager[811]: <info>  [1762511274.3918] exiting (success)  
Nov 07 11:27:54 bednaArch systemd[1]: NetworkManager.service: Deactivated successfully.  
Nov 07 11:27:54 bednaArch systemd[1]: Stopped Network Manager.  
Nov 07 11:27:54 bednaArch systemd[1]: Starting Network Manager...  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.4565] NetworkManager (version 1.54.1-1) is starting... (after a restart, boot:ac5a6938-be26-4c33-a54e-9993e4beec14)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.4566] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/20-connectivity.conf  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.4597] manager[0x559d2e3ef550]: monitoring kernel firmware directory '/lib/firmware'.  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5061] hostname: hostname: using hostnamed  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5061] hostname: static hostname changed from (none) to "bednaArch"  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5062] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5079] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:07.0/0000:0  
f:00.0/ieee80211/phy0/rfkill1) (driver mt7921e)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5082] manager[0x559d2e3ef550]: rfkill: Wi-Fi hardware radio set disabled  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5082] manager[0x559d2e3ef550]: rfkill: WWAN hardware radio set enabled  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5089] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-adsl.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5095] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-bluetooth.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5097] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-ovs.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5139] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-team.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5140] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wifi.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5141] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wwan.so)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5142] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5142] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5142] manager: Networking is enabled by state file  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5143] settings: Loaded settings plugin: keyfile (internal)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5152] dhcp: init: Using DHCP client 'internal'  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5152] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5154] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5154] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5156] device (lo): Activation: starting connection 'lo' (c1cde8a8-1c5e-4d5a-bb92-37cdb2f896eb)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5158] device (enp14s0): carrier: link connected  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5162] manager: (enp14s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5163] manager: (enp14s0): assume: will attempt to assume matching connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7) (indic  
ated)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5163] device (enp14s0): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'assume')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5165] device (enp14s0): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'assume')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5167] device (enp14s0): Activation: starting connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5168] device (wlan0): driver supports Access Point (AP) mode  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5170] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5171] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5172] device (wlan0): set-hw-addr: set MAC address to CA:FF:26:A1:40:36 (scanning)  
Nov 07 11:27:54 bednaArch systemd[1]: Started Network Manager.  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5175] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5179] ovsdb: disconnected from ovsdb  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5180] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5180] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5181] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5182] device (enp14s0): state change: disconnected -> prepare (reason 'none', managed-type: 'assume')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5183] device (enp14s0): state change: prepare -> config (reason 'none', managed-type: 'assume')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5184] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5185] device (enp14s0): state change: config -> ip-config (reason 'none', managed-type: 'assume')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5186] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5188] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5188] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5190] device (lo): Activation: successful, device activated.  
Nov 07 11:27:54 bednaArch NetworkManager[11434]: <info>  [1762511274.5287] agent-manager: agent[a1e0ce0286bbecab,:1.31/org.kde.plasma.networkmanagement/1000]: agent registered  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5491] device (enp14s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'assume')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5786] device (enp14s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'assume')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5787] device (enp14s0): state change: secondaries -> activated (reason 'none', managed-type: 'assume')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5788] manager: NetworkManager state is now CONNECTED_LOCAL  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5789] device (enp14s0): Activation: successful, device activated.  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5790] manager: startup complete  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5791] device (enp14s0): state change: activated -> failed (reason 'ip-config-unavailable', managed-type: 'full')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5792] manager: NetworkManager state is now DISCONNECTED  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <warn>  [1762511319.5793] device (enp14s0): Activation: failed for connection 'Wired connection 1'  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5795] device (enp14s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5863] dhcp4 (enp14s0): canceled DHCP transaction  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5863] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5863] dhcp4 (enp14s0): state changed no lease  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5869] policy: auto-activating connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5871] device (enp14s0): Activation: starting connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5872] device (enp14s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5873] manager: NetworkManager state is now CONNECTING  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5873] device (enp14s0): state change: prepare -> config (reason 'none', managed-type: 'full')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5877] device (enp14s0): state change: config -> ip-config (reason 'none', managed-type: 'full')  
Nov 07 11:28:39 bednaArch NetworkManager[11434]: <info>  [1762511319.5878] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5588] device (enp14s0): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5589] manager: NetworkManager state is now DISCONNECTED  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <warn>  [1762511364.5589] device (enp14s0): Activation: failed for connection 'Wired connection 1'  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5590] device (enp14s0): state change: failed -> disconnected (reason 'none', managed-type: 'full')  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5723] dhcp4 (enp14s0): canceled DHCP transaction  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5723] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5723] dhcp4 (enp14s0): state changed no lease  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5727] policy: auto-activating connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5728] device (enp14s0): Activation: starting connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5728] device (enp14s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5729] manager: NetworkManager state is now CONNECTING  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5729] device (enp14s0): state change: prepare -> config (reason 'none', managed-type: 'full')  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5731] device (enp14s0): state change: config -> ip-config (reason 'none', managed-type: 'full')  
Nov 07 11:29:24 bednaArch NetworkManager[11434]: <info>  [1762511364.5732] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)

After hard rebooting my system, eg the network works after the reboot:

sudo journalctl -u NetworkManager.service -e --no-pager

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.  
Nov 07 11:37:33 bednaArch systemd[1]: Starting Network Manager...  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.1774] NetworkManager (version 1.54.1-1) is starting... (boot:0467c534-fe59-4538-8353-f44e96997fc0)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.1774] Read config: /etc/NetworkManager/NetworkManager.conf, /usr/lib/NetworkManager/conf.d/20-connectivity.conf  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.1805] manager[0x55e5a4debef0]: monitoring kernel firmware directory '/lib/firmware'.  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2104] hostname: hostname: using hostnamed  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2104] hostname: static hostname changed from (none) to "bednaArch"  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2105] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2121] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.1/0000:03:00.0/0000:04:08.0/0000:0a:00.0/0000:0b:07.0/0000:0f:  
00.0/ieee80211/phy0/rfkill1) (driver mt7921e)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2123] manager[0x55e5a4debef0]: rfkill: Wi-Fi hardware radio set disabled  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2123] manager[0x55e5a4debef0]: rfkill: WWAN hardware radio set enabled  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2136] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-adsl.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2160] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-bluetooth.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2169] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-ovs.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2295] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-team.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2302] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wifi.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2304] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.54.1-1/libnm-device-plugin-wwan.so)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2305] manager: rfkill: Wi-Fi disabled by radio killswitch; disabled by state file  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2305] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2305] manager: Networking is enabled by state file  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2307] settings: Loaded settings plugin: keyfile (internal)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2320] dhcp: init: Using DHCP client 'internal'  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2321] manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2324] device (lo): state change: unmanaged -> unavailable (reason 'connection-assumed', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2324] device (lo): state change: unavailable -> disconnected (reason 'connection-assumed', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2326] device (lo): Activation: starting connection 'lo' (1eb3b4cf-7320-4f23-8505-a2b10e3d5276)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2332] manager: (enp14s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.2333] device (enp14s0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4118] device (wlan0): driver supports Access Point (AP) mode  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4121] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4122] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4124] device (wlan0): set-hw-addr: set MAC address to 32:D1:80:5B:DC:C2 (scanning)  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4127] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"  
Nov 07 11:37:33 bednaArch systemd[1]: Started Network Manager.  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4130] ovsdb: disconnected from ovsdb  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4131] device (lo): state change: disconnected -> prepare (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4132] device (lo): state change: prepare -> config (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4132] device (lo): state change: config -> ip-config (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4135] device (lo): state change: ip-config -> ip-check (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4141] device (lo): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4141] device (lo): state change: secondaries -> activated (reason 'none', managed-type: 'external')  
Nov 07 11:37:33 bednaArch NetworkManager[803]: <info>  [1762511853.4143] device (lo): Activation: successful, device activated.  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3435] device (enp14s0): carrier: link connected  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3436] device (enp14s0): state change: unavailable -> disconnected (reason 'carrier-changed', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3437] policy: auto-activating connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3439] device (enp14s0): Activation: starting connection 'Wired connection 1' (7c6940c4-fcf6-322c-9a0c-07af39b45ae7)  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3439] device (enp14s0): state change: disconnected -> prepare (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3439] manager: NetworkManager state is now CONNECTING  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3440] device (enp14s0): state change: prepare -> config (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3442] device (enp14s0): state change: config -> ip-config (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3443] dhcp4 (enp14s0): activation: beginning transaction (timeout in 45 seconds)  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.3559] dhcp4 (enp14s0): state changed new lease, address=192.168.99.10, acd pending  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5249] dhcp4 (enp14s0): state changed new lease, address=192.168.99.10  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5253] policy: set 'Wired connection 1' (enp14s0) as default for IPv4 routing and DNS  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5590] device (enp14s0): state change: ip-config -> ip-check (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5596] device (enp14s0): state change: ip-check -> secondaries (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5596] device (enp14s0): state change: secondaries -> activated (reason 'none', managed-type: 'full')  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5597] manager: NetworkManager state is now CONNECTED_SITE  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5598] device (enp14s0): Activation: successful, device activated.  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.5599] manager: startup complete  
Nov 07 11:37:36 bednaArch NetworkManager[803]: <info>  [1762511856.6564] manager: NetworkManager state is now CONNECTED_GLOBAL  
Nov 07 11:37:45 bednaArch NetworkManager[803]: <info>  [1762511865.1375] agent-manager: agent[668224e2f71a4c68,:1.31/org.kde.plasma.networkmanagement/1000]: agent registered

Computer information:

inxi -Fazy

System:
  Kernel: 6.17.7-arch1-2 arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux
    root=UUID=78235068-f1ca-4363-99b1-474175fb3438 rw rootflags=subvol=@
    rootfstype=btrfs sysrq_always_enabled=1 ipv6.disable=1 modeset=1 fbdev=1
    nvidia-drm.modeset=1 loglevel=3 amd-pstate=guided udev.log-priority=info
    rd.udev.log_level=3
  Desktop: KDE Plasma v: 6.5.2 tk: Qt v: N/A info: frameworks v: 6.19.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: X670 AORUS ELITE AX v: x.x
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: F36 date: 07/31/2025
CPU:
  Info: model: AMD Ryzen 9 7900X bits: 64 type: MT MCP arch: Zen 4 gen: 4
    level: v4 note: check built: 2022+ process: TSMC n5 (5nm) family: 0x19 (25)
    model-id: 0x61 (97) stepping: 2 microcode: 0xA60120C
  Topology: cpus: 1x dies: 2 clusters: 2x1 cores: 12 threads: 24 tpc: 2
    smt: enabled cache: L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 12 MiB
    desc: 12x1024 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3042 min/max: 415/5738 boost: enabled scaling:
    driver: amd-pstate governor: schedutil cores: 1: 3042 2: 3042 3: 3042 4: 3042
    5: 3042 6: 3042 7: 3042 8: 3042 9: 3042 10: 3042 11: 3042 12: 3042 13: 3042
    14: 3042 15: 3042 16: 3042 17: 3042 18: 3042 19: 3042 20: 3042 21: 3042
    22: 3042 23: 3042 24: 3042 bogomips: 225170
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3
    svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: old_microcode status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    STIBP: always-on; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsa mitigation: Clear CPU buffers
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: NVIDIA GA102 [GeForce RTX 3090] vendor: EVGA driver: nvidia
    v: 580.105.08 alternate: nouveau,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-08; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 4 speed: 16 GT/s ports: active: none empty: DP-1,
    DP-2, DP-3, HDMI-A-1 bus-ID: 01:00.0 chip-ID: 10de:2204 class-ID: 0300
  Device-2: Advanced Micro Devices [AMD/ATI] Raphael vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-2 empty: DP-4, DP-5, DP-6, Writeback-1 bus-ID: 15:00.0
    chip-ID: 1002:164e class-ID: 0300 temp: 53.0 C
  Display: wayland server: X.org v: 1.21.1.20 with: Xwayland v: 24.1.9
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    alternate: fbdev,nouveau,nv,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: HDMI-A-2 model: Asus VX279 serial: <filter> built: 2015 res:
    mode: 1920x1080 hz: 60 scale: 100% (1) dpi: 81 gamma: 1.2
    size: 621x341mm (24.45x13.43") diag: 690mm (27.2") ratio: 16:9 modes:
    max: 1920x1080 min: 720x400
  API: EGL v: 1.5 hw: drv: nvidia drv: amd radeonsi platforms: device: 0
    drv: nvidia device: 1 drv: radeonsi device: 3 drv: swrast gbm:
    drv: kms_swrast surfaceless: drv: nvidia wayland: drv: radeonsi x11:
    drv: radeonsi inactive: device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 25.2.7-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Ryzen 9 7900X 12-Core Processor
    (radeonsi raphael_mendocino LLVM 21.1.5 DRM 3.64 6.17.7-arch1-2)
    device-ID: 1002:164e memory: 500 MiB unified: no display-ID: :1.0
  API: Vulkan v: 1.4.328 layers: 8 device: 0 type: discrete-gpu
    name: NVIDIA GeForce RTX 3090 driver: nvidia v: 580.105.08
    device-ID: 10de:2204 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA102 High Definition Audio vendor: EVGA
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:1aef class-ID: 0403
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    [Rembrandt/Strix] driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 15:00.1 chip-ID: 1002:1640 class-ID: 0403
  Device-3: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 15:00.6 chip-ID: 1022:15e3 class-ID: 0403
  API: ALSA v: k6.17.7-arch1-2 status: kernel-api tools: N/A
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.9 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Gigabyte driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 0e:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp14s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Device-2: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 0f:00.0
    chip-ID: 14c3:0616 class-ID: 0280
  IF: wlan0 state: down mac: <filter>
  Info: services: NetworkManager, nfsd, sshd, systemd-timesyncd
Bluetooth:
  Device-1: MediaTek Wireless_Device driver: btusb v: 0.8 type: USB rev: 2.1
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-7:3 chip-ID: 0e8d:0616
    class-ID: e001 serial: <filter>
  Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: disabled
    rfk-block: hardware: no software: yes address: see --recommends
Drives:
  Local Storage: total: 6.08 TiB used: 3.17 TiB (52.1%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Samsung model: SSD 980 PRO 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 5B2QGXA7 temp: 45.9 C
    scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 0B2QJXG7 temp: 41.9 C
    scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 4B6Q scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Intel model: SSDSC2BF180A4H
    size: 167.68 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: LH6i scheme: GPT
  ID-5: /dev/sdc maj-min: 8:32 vendor: Western Digital
    model: WD30EFRX-68EUZN0 size: 2.73 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
    fw-rev: 0A80 scheme: GPT
Partition:
  ID-1: / raw-size: 99.5 GiB size: 99.5 GiB (100.00%) used: 76.93 GiB (77.3%)
    fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
  ID-2: /boot/efi raw-size: 1024 MiB size: 1022 MiB (99.80%)
    used: 320 KiB (0.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:4
  ID-3: /home raw-size: 783.01 GiB size: 783.01 GiB (100.00%)
    used: 685.75 GiB (87.6%) fs: btrfs dev: /dev/nvme0n1p3 maj-min: 259:6
  ID-4: /var/log raw-size: 99.5 GiB size: 99.5 GiB (100.00%)
    used: 76.93 GiB (77.3%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:5
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 48 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/nvme0n1p4 maj-min: 259:7
  ID-2: swap-2 type: partition size: 167.68 GiB used: 0 KiB (0.0%)
    priority: 10 dev: /dev/sdb1 maj-min: 8:17
Sensors:
  System Temperatures: cpu: 60.6 C mobo: 44.0 C gpu: amdgpu temp: 42.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.46 GiB used: 4.68 GiB (15.4%)
  Processes: 532 Power: uptime: 1h 51m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.11 GiB services: org_kde_powerdevil,upowerd
    Init: systemd v: 258 default: graphical tool: systemctl
  Packages: 1486 pm: pacman pkgs: 1464 libs: 397 tools: yay pm: flatpak
    pkgs: 22 Compilers: clang: 21.1.5 gcc: 15.2.1 Shell: Zsh v: 5.9 default: Bash
    v: 5.3.3 running-in: yakuake inxi: 3.3.39

I have no idea what to do and searching forums does not provide anyting usefull.
I am not going to do like I did with my wifi and wait almost a year thinking "this bug will be fixed" this time, therefore I am asking for help here.
Maybe I'm blind and there is something obvious my dyslexia hides for me...

Thank you in advance.

Bedna · 2025-11-18 07:05:50

I'm a little shocked nobody wanted to even try to help out with this issue.

Removing systemd hook seems to be the solution even though I have no idea why that would cause this behavior without any traces of it in any logs.

Also, no idea why this is happening:

○ systemd-resolved.service - Network Name Resolution
     Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; disabled; preset: enabled)
     Active: inactive (dead)
TriggeredBy: ○ systemd-resolved-monitor.socket
             ○ systemd-resolved-varlink.socket
       Docs: man:systemd-resolved.service(8)
             man:org.freedesktop.resolve1(5)
             https://systemd.io/WRITING_NETWORK_CONFIGURATION_MANAGERS
             https://systemd.io/WRITING_RESOLVER_CLIENTS

sudo journalctl -u NetworkManager.service -e --no-pager | grep systemd-resolved

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.
Nov 18 07:20:26 bednaArch NetworkManager[861]: <info>  [1763446826.9712] dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink

sudo journalctl -u systemd-resolved.service -b-1

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.
-- No entries --

sudo journalctl -u systemd-resolved.service -b-0

Journal file /var/log/journal/64eb58becfd64371be99c8cb8029cfff/system@0006425d326a0971-e17c88b46e548974.journal~ is truncated, ignoring file.
-- No entries --

systemd-resolved does not seem to be the issue though, because it still seems to run via networkmanager even though disabled, and even though I did not show those logs here, I did investigate it and my local dns WAS pointed to correctly even when the network dropped but was obv not reachable due to network not functioning.
So now my network works as before and there is no longer any need to reboot once when starting the computer the first time each day.

Edit.
Should maybe also add that sd-vconsole gives error if systemd hook is not present:

  -> Running build hook: [sd-vconsole]
/usr/lib/initcpio/install/sd-vconsole: line 9: add_systemd_unit: command not found

End edit.

Last edited by Bedna (2025-11-18 07:43:34)

seth · 2025-11-18 15:33:38

What kind of systemd hook where? The mkinitcpio??
Please post your complete system journal for a boot covering the loss, eg.

sudo journalctl -b -5 | curl -F 'file=@-' 0x0.st

for 5 boots ago
A bunch of disconnected random excerpts doesn't tell much about what's going on.

Should maybe also add that sd-vconsole gives error if systemd hook is not present:

https://bbs.archlinux.org/viewtopic.php?id=310236

I'm a little shocked nobody wanted to even try to help out with this issue.

The day only has 24h and if the forum is busy threads sometimes can fall through the cracks.
This is why you're expected to do exactly what you did: keep working on the problem yourself and share the progress.
Raises the chances that you get caught and doesn't count as bumping

Bedna · 2025-11-18 17:09:36

Thank you for responding.

Yeah, me not knowing what commands to run that can be helpful was kinda the reason I made the post. xD
And yes, the systemd hook is the one in mkinitcpio. I didn't have that hook, only udev up until the pacnew a few days ago and did not connect the dots until way later, my bad...
My current (and the one I used in the past) is: HOOKS=(base udev autodetect microcode modconf keyboard keymap block filesystems)

-5 is one of the boots it failed after a minute or so forcing me to reboot: http://0x0.st/Kfyt.txt

My network actually died exactly like before today, but with the difference that it happened 6hrs after startup of the system, so the problem might still be there and the removal of the systemd hook might be a correlation rather than causation.
About the vconsole, I don't actually care about that, I just figured I mention it in case it was related to systemd in this regard somehow. I survive without it.

loqs · 2025-11-18 18:16:49

If turned off means suspend then possibly https://git.kernel.org/pub/scm/linux/ke … f02e0feba4

Bedna · 2025-11-18 19:42:17

loqs wrote:

If turned off means suspend then possibly https://git.kernel.org/pub/scm/linux/ke … f02e0feba4

No, I shut down the computer every night.

But then again, the problem in the past with my wifi I explained at the beginning of op was that the wifi chip never actually shutdown and I had to remove power to the system for it to release the usb interface, so my mobo might live by rules of its own...
But I have tried that method (removing power during the night) and the behavior persisted and I still had to reboot once after first startup.

If anybody want me to go back to the old settings with systemd hook in mkinitcpio to reproduce the behavior, let me know. But keep in mind that I only have one shot per day since it only happens after the computer has been shut off for at least a few hours. So if you want me to do that, clear instructions on what commands to run to gather further information is probably the best.

Last edited by Bedna (2025-11-18 19:51:02)

seth · 2025-11-18 20:46:59

http://0x0.st/Kfyt.txt doesn't use a wifi connection at all but

Nov 16 12:20:37 bednaArch kernel: r8169 0000:0e:00.0 eth0: RTL8125B, d8:5e:d3:e4:b5:67, XID 641, IRQ 139

The boot is only ~2 minutes and there're not signs of issues w/ it

Nov 16 12:20:45 bednaArch NetworkManager[805]: <info>  [1763292045.1620] manager: NetworkManager state is now CONNECTED_GLOBAL
Nov 16 12:21:11 bednaArch systemd-timesyncd[529]: Contacted time server 98.128.175.45:123 (2.arch.pool.ntp.org).
Nov 16 12:21:11 bednaArch systemd-timesyncd[529]: Initial clock synchronization to Sun 2025-11-16 12:21:11.619929 CET.
Nov 16 12:22:09 bednaArch systemd-logind[808]: New session '2' of user 'bedna' with class 'user' and type 'wayland'.
Nov 16 12:22:34 bednaArch systemd-logind[808]: The system will reboot now!

What's your metric for "network stops working"?
Can you still

ping _gateway

or

ping 8.8.8.8

?

If anybody want me to go back to the old settings with systemd hook in mkinitcpio to reproduce the behavior, let me know.

Providing a journal from then should suffice.

Bedna · 2025-11-18 22:21:25

seth wrote:

http://0x0.st/Kfyt.txt doesn't use a wifi connection at all but
Nov 16 12:20:37 bednaArch kernel: r8169 0000:0e:00.0 eth0: RTL8125B, d8:5e:d3:e4:b5:67, XID 641, IRQ 139

I never use the wifi, that is why it took a long time for me to realize it was that that made my boot freeze for about one minute as I mentioned in OP.
The wifi works when the lan drops, I tried that, but the wifi just came with the mobo, I rely on lan and very rarely use it so it is disabled by default. Same with bluetooth.

The boot is only ~2 minutes and there're not signs of issues w/ it

Hence my confusion and this thread...

What's your metric for "network stops working"?
Can you still
ping _gateway
or
ping 8.8.8.8
?

Nope and nope. Nothing on the lan seems reachable, can't ping inside or outside the lan. If I stop the connection via networkmanager (KDE network gui) and try to connect to it again, it just "spins" forever.

If anybody want me to go back to the old settings with systemd hook in mkinitcpio to reproduce the behavior, let me know.
Providing a journal from then should suffice.

Well, that WAS the log. The log is so short because the lan dropped after that time. That is the problem each time after a longer shutdown... xD
If you want me to reactivate the systemd hook and reproduce the issue, and use something else to probe my system when lan drops after I start the computer in the morning, I can, but you have to tell me what because I have no idea.

Edit
I found one that lasted a bit longer, all of four minutes, and I had started using stuff like firefox, then things started crashing, probably because I also had connected to my nfs drive. So there are a bunch of stuff in there, maybe you can find some clue there.
http://0x0.st/KfgN.txt

Last edited by Bedna (2025-11-18 22:46:15)

seth · 2025-11-18 22:39:37

The systemd hook will implicitly activate resume from hibernation automagics - there're quite some partitions (3 ssd and 2 nvme drives): do you happen to use multitple OS?
Does there happen to be a parallel windows installation?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Bedna · 2025-11-18 22:53:09

seth wrote:

The systemd hook will implicitly activate resume from hibernation automagics - there're quite some partitions (3 ssd and 2 nvme drives): do you happen to use multitple OS?
Does there happen to be a parallel windows installation?
=> 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

I don't have any resume configured in the kernel parameters, IIRC that is needed for resume to work so I have "disabled" it so if computer ever goes to sleep it never enters hibernation. So that is likely not the issue either.

No windows, but used to so I know the hustle. xD
But there is also a manjaro installation I very rarely use, but on complete separate device so no shared bootloader (one boot partition each), I select what to boot into by pressing f12 at boot time and select in the uefi, and default is arch.
This is very unlikely to have anything to do with that.

Last edited by Bedna (2025-11-18 22:56:56)

seth · 2025-11-18 23:11:08

IIRC that is needed for resume to work so I have "disabled" it

systemd can/does this automagically - I'm trying to reason why there's different behavior between systemd and busybox

But there is also a manjaro installation I very rarely use, but on complete separate device

The only relevant question is whether one system boots while the other is hibernating.

Post your current mkinitcpio.conf, restore the breaking condition, post that mkinitcpio.conf as well, reboot, wait for the network to break down, log

ip a; ip r; ping -c1 _gateway; ping -c1 8.8.8.8; ping -c1 google.com

Iff we assume relevance of the wifi, can you disable it in the BIOS/UEFI?
If not, try to rfkill it and see whether the network still breaks.

Bedna · 2025-11-18 23:46:11

$ cat /etc/mkinitcpio.conf

# vim:set ft=sh:
# MODULES
# The following modules are loaded before any boot hooks are
# run.  Advanced users may wish to specify all system modules
# in this array.  For instance:
#     MODULES=(usbhid xhci_hcd)
MODULES=(btrfs nvidia nvidia_drm nvidia_uvm nvidia_modeset)

# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image.  This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=(/usr/bin/btrfs)

# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way.  This is useful for config files.
FILES=()

# HOOKS
# This is the most important setting in this file.  The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added.  Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
##   This setup specifies all modules in the MODULES setting above.
##   No RAID, lvm2, or encrypted root is needed.
#    HOOKS=(base)
#
##   This setup will autodetect all modules for your system and should
##   work as a sane default
#    HOOKS=(base udev autodetect microcode modconf block filesystems fsck)
#
##   This setup will generate a 'full' image which supports most systems.
##   No autodetection is done.
#    HOOKS=(base udev microcode modconf block filesystems fsck)
#
##   This setup assembles a mdadm array with an encrypted root file system.
##   Note: See 'mkinitcpio -H mdadm_udev' for more information on RAID devices.
#    HOOKS=(base udev microcode modconf keyboard keymap consolefont block mdadm_udev encrypt filesystems fsck)
#
##   This setup loads an lvm2 volume group.
#    HOOKS=(base udev microcode modconf block lvm2 filesystems fsck)
#
##   This will create a systemd based initramfs which loads an encrypted root filesystem.
#    HOOKS=(base systemd autodetect microcode modconf kms keyboard sd-vconsole sd-encrypt block filesystems fsck)
#
##   NOTE: If you have /usr on a separate partition, you MUST include the
#    usr and fsck hooks.
#HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck) # default config from pacnew
#HOOKS=(base udev autodetect microcode keyboard keymap modconf block filesystems) # pacnew nov 2025, this is the old line that works
HOOKS=(base systemd autodetect microcode modconf keyboard keymap sd-vconsole block filesystems)

# COMPRESSION
# Use this to compress the initramfs image. By default, zstd compression
# is used for Linux ≥ 5.9 and gzip compression is used for Linux < 5.9.
# Use 'cat' to create an uncompressed image.
#COMPRESSION="zstd"
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"

# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=()

# MODULES_DECOMPRESS
# Decompress loadable kernel modules and their firmware during initramfs
# creation. Switch (yes/no).
# Enable to allow further decreasing image size when using high compression
# (e.g. xz -9e or zstd --long --ultra -22) at the expense of increased RAM usage
# at early boot.
# Note that any compressed files will be placed in the uncompressed early CPIO
# to avoid double compression.
#MODULES_DECOMPRESS="no"

mkinitcpio -P completed successfully.

This is the status of rfkill now, ie default.

$ rfkill list

0: hci0: Bluetooth
        Soft blocked: yes
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: no

I'll see if I can disable it in UEFI, I don't remember if there is an option and update thread tomorrow with information.

Edit.

I turned off wifi and bluetooth in UEFI and oddly:

$ rfkill list

0: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: no

But I bet it's the same thing connected to the wifi bug referenced in OP. If I pull the plug from my system for just 10 minutes, the wifi chipset will be turned off too. I'll pull the plug tonight.

But I found another setting, Network stack configuration. It was set to default witch was disabled. I don't know what that is, should I try to enable it?

For reference. this is the output without systemd & sd-vconsole hook and with udev hook, ie fully working network.

$ ip a; ip r; ping -c1 _gateway; ping -c1 8.8.8.8; ping -c1 google.com

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
2: enp14s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether <redacted> brd ff:ff:ff:ff:ff:ff
    inet 192.168.99.10/24 brd 192.168.99.255 scope global dynamic noprefixroute enp14s0
       valid_lft 33371sec preferred_lft 33371sec
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether <redacted> brd ff:ff:ff:ff:ff:ff permaddr <redacted>
default via 192.168.99.1 dev enp14s0 proto dhcp src 192.168.99.10 metric 100 
192.168.99.0/24 dev enp14s0 proto kernel scope link src 192.168.99.10 metric 100 
PING _gateway (192.168.99.1) 56(84) bytes of data.
64 bytes from _gateway (192.168.99.1): icmp_seq=1 ttl=64 time=0.680 ms

--- _gateway ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.680/0.680/0.680/0.000 ms
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=12.4 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.437/12.437/12.437/0.000 ms
PING google.com (142.250.74.14) 56(84) bytes of data.
64 bytes from arn09s21-in-f14.1e100.net (142.250.74.14): icmp_seq=1 ttl=113 time=12.3 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.326/12.326/12.326/0.000 ms

Last edited by Bedna (2025-11-19 00:16:48)

seth · 2025-11-19 08:24:09

HOOKS=(base systemd autodetect microcode modconf keyboard keymap sd-vconsole block filesystems)

is

#HOOKS=(base systemd autodetect microcode modconf kms keyboard keymap sd-vconsole block filesystems fsck) # default config from pacnew

minus "kms" and "fsck"
The "keymap" in there is a bug, sd-vconsole does this, too

There's btw. nothing wrong w/ using

#HOOKS=(base udev autodetect microcode keyboard keymap modconf block filesystems) # pacnew nov 2025, this is the old line that works

I don't know what that is, should I try to enable it?

Most likely PXE, it might implicitly configure the wifi NIC, so I'd keep it disabled.
If the problem is between the busybox and systemd HOOKs, systemd might just fail to take control over/reset the wireless NIC during the boot?

Bedna · 2025-11-19 09:49:23

Well, like clockwork my network dropped about a minute after booting and logging in.

Look, I get it, you think I'm trolling and that is why you are asking about windows and pings even though I said in OP that nothing can be pinged, BUT I AM NOT TROLLING!!!

$ ip a; ip r; ping -c1 _gateway; ping -c1 8.8.8.8; ping -c1 google.com

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000  
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00  
   inet 127.0.0.1/8 scope host lo  
      valid_lft forever preferred_lft forever  
2: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000  
   link/ether <redacted> brd ff:ff:ff:ff:ff:ff  
   inet 192.168.99.10/24 brd 192.168.99.255 scope global dynamic noprefixroute enp13s0  
      valid_lft 43030sec preferred_lft 43030sec  
3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000  
   link/ether <redacted> brd ff:ff:ff:ff:ff:ff permaddr <redacted>
default via 192.168.99.1 dev enp13s0 proto dhcp src 192.168.99.10 metric 100    
192.168.99.0/24 dev enp13s0 proto kernel scope link src 192.168.99.10 metric 100    
PING _gateway (192.168.99.1) 56(84) bytes of data.  
From bednaArch (192.168.99.10) icmp_seq=1 Destination Host Unreachable  
  
--- _gateway ping statistics ---  
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms  
  
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.  
From 192.168.99.10 icmp_seq=1 Destination Host Unreachable  
  
--- 8.8.8.8 ping statistics ---  
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms  
  
ping: google.com: Temporary failure in name resolution

http://0x0.st/KfGz.txt

If nobody cares that enabling systemd (the default config on arch) causes this system to drop lan without traces in logs I can easily go back to removing it and vconsole. fsck IIRC should not be enabled if you have btrfs on root, but I could be wrong, but that is the reason I removed it.
BUT, it DID drop once yesterday without the systemd hook, albeit after about 6hrs and not like clockwork right after the "first boot of the day" like it does with the systemd hook in mkinitcpio.
On a personal level, I would really like to know why this is happening on my system...

There also seems to be something going on at hardware level, because even though I had the power plugged out the entire night and have wifi disabled in uefi (I double checked when I was forced to restart after lan dropped), it is STILL there, but nothing to rfkill since it is already soft disabled (gigabyte uefi bug?):

$ rfkill list

0: phy0: Wireless LAN
        Soft blocked: yes
        Hard blocked: no

So again, if someone wants me to run some command to probe my system while this is happening each first boot after a long shutdown, let me know what.
Pings are great and all, but it doesn't give any information about WHY this is happening.

seth · 2025-11-19 13:36:44

you think I'm trolling

No. I wanted to see the actual error messages.

Disable opensnitch, resp look at this

2: enp14s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
2: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

lennarts predictable-my-ass NIC names change (depending on the initramfs system ?)
This will screw up any kind of NIC specific rules you may or not have in netfilter
=> https://wiki.archlinux.org/title/Networ … face_names to get some control over that.

Bedna · 2025-11-19 16:08:47

seth wrote:

you think I'm trolling
2: enp14s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
2: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000  
lennarts predictable-my-ass NIC names change (depending on the initramfs system ?)
This will screw up any kind of NIC specific rules you may or not have in netfilter
=> https://wiki.archlinux.org/title/Networ … face_names to get some control over that.

I have disabled the opensnitch service and will retry in the morning.

But about predictable network interface names, I have neither /etc/systemd/network/99-default.link.d/traditional-naming.conf nor /etc/udev/rules.d/80-net-setup-link.rules
The only thing in /etc/systemd/network is a rule I setup for wol to work.
And /etc/udev/rules.d/ is completely empty.
So that leaves the kernel parameter, and there is a warning about using that "unless I know what I am doing" witch in this regard, I do not.

So should I create a rule in /etc/systemd/network
Or just touch the file /etc/udev/rules.d/80-net-setup-link.rules and then symlink it to /dev/null
Or should I go with the kernel parameter?
Or should I do one thing at a time, and start with just disabling opensnitch for now?

seth · 2025-11-19 19:44:38

ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules

will do.
nb. that this will fix the device name as "eth0" - if you've any netfilter rules (from opensnitch or othewise) specific to enp14s0 those would still not apply correctly.

rn the name change (caused by the different initramfs system) and a firewall are my best explanations for what's going on.

Bedna · 2025-11-19 20:23:24

if you've any netfilter rules (from opensnitch or othewise) specific to enp14s0 those would still not apply correctly.

And as of this boot:

2: enp13s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000

There is a setting in opensnitch called "flush connections on start" that kills the existing sockets forcing them to reconnect so openshitch can intercept them, so you might be on to something here. IIRC I did shut down opensnitch at some point trying re-eastblish by restarting networkmanager, but maybe that was not enough.
Strange that it only happens on first boot after long shutown, not ALL shutdowns, and only with systemd hook in mkinitcpio.
Also strange that the network works for a little while before breaking if this is the reason.

Ill do some testing and keep the thread updated when I have more information.

seth · 2025-11-19 20:59:13

Strange that it only happens on first boot after long shutown, not ALL shutdowns, and only with systemd hook in mkinitcpio.

enp13s0 / enp14s0 is driven by the bus geography - some stray device randomly (not) showing up on the bus will alter the position (which might easily hark back to the wifi nic situation)

Bedna · 2025-11-19 21:31:00

seth wrote:

Strange that it only happens on first boot after long shutown, not ALL shutdowns, and only with systemd hook in mkinitcpio.
enp13s0 / enp14s0 is driven by the bus geography - some stray device randomly (not) showing up on the bus will alter the position (which might easily hark back to the wifi nic situation)

I see...
I made a ticket on gigabytes support portal about not being able to shut off my wifi. But I don't have high hopes of getting anything useful out of that, I have previous experiences with them. I reported a bug on one of their beta firmwares, where the fans were in wrong polarization, so when supposed to run at full speed they went to 0% and vice versa. Took a week before they even removed that version from their web page, and 6 more before they answered, coincidentally one day after they released a new stable UEFI version. Their response was "please update your firmware". ?

TracerP · 2025-11-19 22:26:21

Yo I have the same issue and quite similar hardware mobo - gigabyte x670 gaming x ax with RTL8125B and mt7922 for wifi.
I could not pin this out but after reading this thread it does occurs at first boot of the day but after reset I do not have the problem, I though that this is maybe bug in the r8169 driver but I tried r8125 with the same result (ethernet dropping), I also could not disable WiFi in the bios so I blacklisted wifi driver so I'm testing that for a moment. I also turned off ASPM in kernel parameters just in case because I got "ASPM disbled on Tx timeout" warning in journal couple of times but it didn't helped.
I didn't yet tried LTS kernel that next on my list. If I can help debug this it would be excellent

Here is my journal when it happened today 19.11 but I was in the important meeting so I manually downed the interface and bringed it up to make it work for a while
http://0x0.st/KOsa.txt (timestamp 09:12:03)

Here is from 2 days ago 17.11 with warning ASPM disabled on Tx timeout
http://0x0.st/KOsS.txt (timestamp 12:27:48)

lspci -v | grep -i wireless -A 9                                        
11:00.0 Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Subsystem: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter
        Flags: fast devsel, IRQ 255, IOMMU group 26
        Memory at f830300000 (64-bit, prefetchable) [disabled] [size=1M]
        Memory at f6100000 (64-bit, non-prefetchable) [disabled] [size=32K]
        Capabilities: <access denied>
        Kernel modules: mt7921e

lspci -v | grep -i ethernet -A 9                                       
10:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
        Subsystem: Gigabyte Technology Co., Ltd Device e000
        Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 26
        I/O ports at e000 [size=256]
        Memory at f6200000 (64-bit, non-prefetchable) [size=64K]
        Memory at f6210000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8169
        Kernel modules: r8169, r8125

sudo dmidecode -t 2                                                                  
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.7.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
        Manufacturer: Gigabyte Technology Co., Ltd.
        Product Name: X670 GAMING X AX
        Version: x.x
        Serial Number: Default string
        Asset Tag: Default string
        Features:
                Board is a hosting board
                Board is replaceable
        Location In Chassis: Default string
        Chassis Handle: 0x0003
        Type: Motherboard
        Contained Object Handles: 0

P.S I also updated bios to newest F36 just in case because I was running some older beta version I think. So now I'm testing blacklisted wifi driver and new bios version.

P.S2 I use Arch with this setup for about a year now and this is relatively new issue (maybe 2weeks) but I can't pinpoint what or which update caused it (if any)

Edit: blacklisting wifi driver and new bios did not changed a bit it happened again. Tomorrow I will check with LTS kernel if that helps

Last edited by TracerP (2025-11-19 23:20:15)

Bedna · 2025-11-20 19:25:19

Update:
Disabling opensnitchd.service seems to "fix" the issue.
But I also disabled plasma firewall so I need to do some further testing if enabling that also causes issues.

I created an issue on openshitch github: https://github.com/evilsocket/opensnitch/issues/1462
Opensnitch is installed via arch stable repos.

As mentioned above by @TracerP, I have LTS kernel installed, but since I only can cause this issue after a long shutdown period, it takes time to test everything.
I have had F36 uefi the entire time as of this issue.

About network interface changing name between enp13s0 & enp14s0. I checked logs backwards, and it used to always be enp13s0, then it changed to enp14s0 for a few boots (4 or 5 IIRC) then went back to enp13s0 again, and that is what it has been called since then.
I have not yet tried to remove predictable names, I feel doing everything slow an methodical is smarter in this situation even if I can only do one configuration/test per day.

I will keep you updated from my side.

Last edited by Bedna (2025-11-20 19:31:15)

TracerP · 2025-11-20 19:53:22

Ahh sorry I didn't notice you are using LTS.
Unfortunelty any of my actions isn't helping and it happened again.

I don't use opensnitch or plasma firewalll im running simple i3 and thats all.

Im also starting to delete all packages for wayland/hyprland that I installed for testing as well as returning to the lightdm from sddm, to check if maybe there is something wrong.

Im just baffled that we have the same motherboard chipset and the same ethernet card and same problem in simillar timeframe, but I hope that at least your problem will be resolved <3

This time it happened when playing online game on steam with proton
http://0x0.st/KOSs.txt (again manually restarted interface to end run quickly)

Bedna · 2025-11-21 08:53:04

So, it is not just opensnitch. plasma firewall ALSO seems to cause the issue.

opensnitchd.service is masked, and plasma firewall is enabled in the gui, and network dies almost immediately.

I can not pull down the network with nmcli down and then bring it up again, the command just freezes when using "up" and nothing happens so I have to cancel it with ctrl+c and then reboot. I know of no other way to "fix" the network when it dies.

The interface is still called enp13s0 so it changing name being related to opensnitch or plasma firewall seems more and more unlikely, but I will get to that in a few days after testing LTS and making sure having no firewall running is actually working, I have only had that config ONCE so it working under those conditions could also be a fluke.

http://0x0.st/KO2y.txt

There is always a bunch of "drkonqi-coredump-processor", every boot. Involving things NOT started on the system, like steam, discord, spotify, pyenv versions etc.
Even things that no longer exist on the system like:

Nov 21 09:40:57 bednaArch drkonqi-coredump-processor[4102]: "/app/lib/org.nickvision.tubeconverter/org.nickvision.tubeconverter.gnome" 9786 "/var/lib/systemd/coredump/core.org\\x2enickvision\\x2e.1000.a1cdd2a844c94c579e1bd5e5561b9f95.9786.1755693517000000.zst"
Nov 21 09:40:57 bednaArch drkonqi-coredump-processor[4102]: "/app/lib/org.nickvision.tubeconverter/org.nickvision.tubeconverter.gnome" 11653 "/var/lib/systemd/coredump/core.org\\x2enickvision\\x2e.1000.a1cdd2a844c94c579e1bd5e5561b9f95.11653.1755693545000000.zst"

That application was removed months ago.
And after all those konqi entries:

Nov 21 09:41:19 bednaArch kernel: [UFW BLOCK] IN=enp13s0 OUT= MAC=01:00:5e:00:00:01:c4:ea:1d:b8:ce:46:08:00 SRC=192.168.99.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2

This was most likely me pinging my gateway.

Also:

$ systemctl is-enabled drkonqi-coredump-processor@.service
disabled

$ systemctl --user is-enabled drkonqi-coredump-launcher.socket
disabled

$ cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d %F

Maybe it has nothing to do with this, but I find that very strange.

Last edited by Bedna (2025-11-21 11:29:35)

seth · 2025-11-21 15:30:19

opensnitchd.service is masked, and plasma firewall is enabled in the gui, and network dies almost immediately.

So probably exclusively the plasma firewall (whatever that's supposed to be) and no opensnitch at all that sets a bogus netfilter rule?
Can you print is rule list (ipdates or nftables?)

The interface is still called enp13s0 so it changing name being related to opensnitch or plasma firewall seems more and more unlikely

Posts #12 and #14 suggest that enp13s0 is aligned w/ bad and enp14s0 with good behavior?
You actually are still following the pattern…

That application was removed months ago.

Its coredumps from when it crashed are still around, that's dead weight but no concern.

systemctl is-enabled drkonqi-coredump-processor@.service

systemctl is-enabled drkonqi-coredump-processor@bedna.service

but idk whether it's started via the service.

Arch Linux

#1 2025-11-14 14:35:55

Network stops working after system being turned off for a few hours

The issue:

#2 2025-11-18 07:05:50

Re: Network stops working after system being turned off for a few hours

#3 2025-11-18 15:33:38

Re: Network stops working after system being turned off for a few hours

#4 2025-11-18 17:09:36

Re: Network stops working after system being turned off for a few hours

#5 2025-11-18 18:16:49

Re: Network stops working after system being turned off for a few hours

#6 2025-11-18 19:42:17

Re: Network stops working after system being turned off for a few hours

#7 2025-11-18 20:46:59

Re: Network stops working after system being turned off for a few hours

#8 2025-11-18 22:21:25

Re: Network stops working after system being turned off for a few hours

#9 2025-11-18 22:39:37

Re: Network stops working after system being turned off for a few hours

#10 2025-11-18 22:53:09

Re: Network stops working after system being turned off for a few hours

#11 2025-11-18 23:11:08

Re: Network stops working after system being turned off for a few hours

#12 2025-11-18 23:46:11

Re: Network stops working after system being turned off for a few hours

#13 2025-11-19 08:24:09

Re: Network stops working after system being turned off for a few hours

#14 2025-11-19 09:49:23

Re: Network stops working after system being turned off for a few hours

#15 2025-11-19 13:36:44

Re: Network stops working after system being turned off for a few hours

#16 2025-11-19 16:08:47

Re: Network stops working after system being turned off for a few hours

#17 2025-11-19 19:44:38

Re: Network stops working after system being turned off for a few hours

#18 2025-11-19 20:23:24

Re: Network stops working after system being turned off for a few hours

#19 2025-11-19 20:59:13

Re: Network stops working after system being turned off for a few hours

#20 2025-11-19 21:31:00

Re: Network stops working after system being turned off for a few hours

#21 2025-11-19 22:26:21

Re: Network stops working after system being turned off for a few hours

#22 2025-11-20 19:25:19

Re: Network stops working after system being turned off for a few hours

#23 2025-11-20 19:53:22

Re: Network stops working after system being turned off for a few hours

#24 2025-11-21 08:53:04

Re: Network stops working after system being turned off for a few hours

#25 2025-11-21 15:30:19

Re: Network stops working after system being turned off for a few hours

Board footer