Arch Linux

qwik

Member

Registered: 2025-06-19

Posts: 3

Shutdown taking forever - possibly due to NM?

Hey guys. For the past few weeks to months, the system has been taking absolutely forever to shut down via the `reboot` command.
Symptoms:
Black screen immediately after command, then nothing for many seconds until a TTY interface appears briefly before shutting down fully.
It usually contains a varying amount of ^@^@^@^@^@^@^@s and "watchdog did not stop" (I think!), sometimes including something else that I can't usually read in time.

journalctl log:

Jun 23 02:19:00 tomfoolery systemd[1]: zerotier-one.service: Deactivated successfully.
Jun 23 02:19:00 tomfoolery systemd[1]: Stopped ZeroTier One.
Jun 23 02:19:00 tomfoolery systemd[1]: zerotier-one.service: Consumed 4min 9.784s CPU time, 24.6M memory peak, 2.4M memory swap peak.
Jun 23 02:19:00 tomfoolery systemd[1]: Stopped target Network is Online.
Jun 23 02:19:00 tomfoolery systemd[1]: NetworkManager-wait-online.service: Deactivated successfully.
Jun 23 02:19:00 tomfoolery systemd[1]: Stopped Network Manager Wait Online.
Jun 23 02:19:40 tomfoolery NetworkManager[608]: <info>  [1750659580.4761] dhcp6 (enp42s0): state changed new lease, address=fd00:bc03:2a65:10::86a 2605:59c8:2612:2f10::86a
Jun 23 02:19:40 tomfoolery dbus-broker-launch[606]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Jun 23 02:20:26 tomfoolery NetworkManager[608]: <info>  [1750659626.3458] device (wlo1): set-hw-addr: set MAC address to 9A:32:89:4B:FE:3A (scanning)
Jun 23 02:20:26 tomfoolery NetworkManager[608]: <info>  [1750659626.3610] device (wlo1): supplicant interface state: inactive -> interface_disabled
Jun 23 02:20:26 tomfoolery NetworkManager[608]: <info>  [1750659626.3611] device (p2p-dev-wlo1): supplicant management interface state: inactive -> interface_disabled
Jun 23 02:20:26 tomfoolery NetworkManager[608]: <info>  [1750659626.3614] device (wlo1): supplicant interface state: interface_disabled -> inactive
Jun 23 02:20:26 tomfoolery NetworkManager[608]: <info>  [1750659626.3614] device (p2p-dev-wlo1): supplicant management interface state: interface_disabled -> inactive
Jun 23 02:20:29 tomfoolery systemd[860]: app-Elite\x20Dangerous@d1a6c9a4d17444bba7ad62f7101f53d0.service: State 'stop-sigterm' timed out. Killing.

Last edited by qwik (Yesterday 06:39:19)

seth

Member

Registered: 2012-09-03

Posts: 64,734

Re: Shutdown taking forever - possibly due to NM?

Please post your complete system journal for the boot:

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

But it looks like you're attempting to get a new netwrok connection during the shutdown…

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc