[SOLVED] NetworkManager slowing down startup time

NachoGoro · 2024-01-30 19:15:48

A few days ago my machine started taking quite long to boot.

It seems to be caused by NetworkManager, but not sure why (I have not changed anything in my physical network setup, nor have I consciously changed any configuration setting).

$ systemd-analyze critical-chain 
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @56.241s
└─multi-user.target @56.241s
  └─smb.service @56.124s +100ms
    └─network-online.target @56.068s
      └─NetworkManager-wait-online.service @33.491s +22.576s
        └─NetworkManager.service @8.830s +24.627s
          └─basic.target @8.829s
            └─dbus-broker.service @8.800s +27ms
              └─dbus.socket @8.799s
                └─sysinit.target @8.796s
                  └─systemd-update-done.service @8.735s +59ms
                    └─systemd-journal-catalog-update.service @8.624s +80ms
                      └─systemd-tmpfiles-setup.service @8.477s +107ms
                        └─local-fs.target @8.435s
                          └─run-user-1000-gvfs.mount @44.342s
                            └─run-user-1000.mount @43.337s
                              └─local-fs-pre.target @1.668s
                                └─systemd-tmpfiles-setup-dev.service @1.518s +150ms
                                  └─systemd-sysusers.service @1.304s +166ms
                                    └─systemd-tmpfiles-setup-dev-early.service @1.165s +109ms
                                      └─kmod-static-nodes.service @702ms +49ms
                                        └─systemd-journald.socket @698ms
                                          └─-.mount @663ms
                                            └─-.slice @663ms

I have checked the journal for NetworkManager, and found a warning "DNS plugin did not become ready again. Assume something is wrong", here is the full log:
https://pastes.io/liyg1cuycd

Any help debugging it would be greatly appreciated!

Last edited by NachoGoro (2024-02-01 15:20:38)

seth · 2024-01-30 21:51:11

That's not a full log, please don't filter the journal for random tokens

W/

Jan 30 17:55:06 desktop NetworkManager[1383]: <info>  [1706633706.3323] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jan 30 17:55:06 desktop NetworkManager[1383]: <warn>  [1706633706.3325] dns-mgr: update-pending changed: DNS plugin did not become ready again. Assume something is wrong

I'll just baselessly (for now) blame dbus-broker

Please post your complete system journal for the boot:

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

NachoGoro · 2024-01-31 07:42:12

Thanks! Here it's the full log: http://0x0.st/HDQp.txt

seth · 2024-01-31 09:35:18

1. There's a completely stale rtw_8821cu wlp2s0f0u10
2. the r8169 enp10s0 only gets a carrier at Jan 31 08:36:24 (you plugged the cable because the wifi dodn't work?)
3. the NIC that ultimately connects (late) is the iwlwifi wlp9s0
4. There's a bridge virbr0 but it seems only from libvirt, there's no intent to bridge the NICs?

=> What happens if you remove the rtw_8821cu dongle?

NachoGoro · 2024-01-31 16:53:56

After unplugging the WiFi dongle it boots normally.

I got the WiFi dongle because I normally use the Ethernet connection, but I sometimes need to connect to the separate WiFi network where some devices are connected. I cannot connect to that secondary network over cable unfortunately.

seth · 2024-01-31 20:42:35

Do you have stale profiles for the dongle, eg.

I sometimes need to connect to the separate WiFi network where some devices are connected

so NM tries to use it first and only moves on after constant failure?
Can you explicitly scan and connect w/ the dongle?

NachoGoro · 2024-02-01 15:20:23

Well, this is embarassing. Turns out my machine has an internal wireless network card and I never knew because I connected the dongle the first day and had it plugged in ever since. I am not sure if I usually connected to those networks over the dongle or the internal WiFi card, but I seem to be able to scan and connect to WiFi networks without the dongle at all.

I could try to disable the internal card to try the dongle, but it's probably irrelevant at this point, as I don't need it any more.

Thank you once again for your help, seth, I believe this is as solved as I need it. We could try to figure out why it stopped working suddenly, but I wouldn't want to waste your time any more.

Last edited by NachoGoro (2024-02-01 15:21:35)

Arch Linux

#1 2024-01-30 19:15:48

[SOLVED] NetworkManager slowing down startup time

#2 2024-01-30 21:51:11

Re: [SOLVED] NetworkManager slowing down startup time

#3 2024-01-31 07:42:12

Re: [SOLVED] NetworkManager slowing down startup time

#4 2024-01-31 09:35:18

Re: [SOLVED] NetworkManager slowing down startup time

#5 2024-01-31 16:53:56

Re: [SOLVED] NetworkManager slowing down startup time

#6 2024-01-31 20:42:35

Re: [SOLVED] NetworkManager slowing down startup time

#7 2024-02-01 15:20:23

Re: [SOLVED] NetworkManager slowing down startup time

Board footer