You are not logged in.

Pages: 1

#1 2025-01-16 13:15:02

prayner96
Member
Registered: 2022-03-06
Posts: 72

[SOLVED] wpa_supplicant interface service timing out for devices

I am facing a 90s delay in boot time at the `network.target` .

[baz_morty@bazmorty ~]$ 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 @1min 31.513s
└─lightdm.service @1min 31.453s +59ms
  └─systemd-user-sessions.service @1min 31.408s +42ms
    └─network.target @1min 31.406s
      └─wpa_supplicant@wlp0s20f3.service @2.447s
        └─basic.target @2.445s
          └─dbus-broker.service @2.430s +13ms
            └─dbus.socket @2.428s
              └─sysinit.target @2.428s
                └─systemd-update-done.service @2.424s +3ms
                  └─ldconfig.service @2.377s +46ms
                    └─local-fs.target @2.375s
                      └─efi.mount @2.338s +36ms
                        └─dev-nvme0n1p1.device @1.486s

The journal tells me that wpa_supplicant interface services are timing out for several devices

sudo journalctl -b
[...]
Jan 16 13:53:24 bazmorty kernel: wlp0s20f3: Limiting TX power to 30 (30 - 0) dBm as advertised by a4:97:33:fd:21:9e
Jan 16 13:53:24 bazmorty dhcpcd[490]: wlp0s20f3: carrier acquired
Jan 16 13:53:24 bazmorty dhcpcd[490]: wlp0s20f3: connected to Access Point: CURRENT_NETWORK
Jan 16 13:53:24 bazmorty dhcpcd[490]: wlp0s20f3: IAID cc:19:41:1e
Jan 16 13:53:24 bazmorty dhcpcd[490]: wlp0s20f3: adding address fe80::2494:aed4:2f4a:fb6d
Jan 16 13:53:25 bazmorty dhcpcd[490]: wlp0s20f3: rebinding lease of 192.168.1.35
Jan 16 13:53:25 bazmorty systemd[1]: systemd-rfkill.service: Deactivated successfully.
Jan 16 13:53:26 bazmorty dhcpcd[490]: wlp0s20f3: soliciting an IPv6 router
Jan 16 13:53:26 bazmorty dhcpcd[490]: wlp0s20f3: leased 192.168.1.35 for 43200 seconds
Jan 16 13:53:26 bazmorty dhcpcd[490]: wlp0s20f3: adding route to 192.168.1.0/24
Jan 16 13:53:26 bazmorty dhcpcd[490]: wlp0s20f3: adding default route via 192.168.1.1
Jan 16 13:53:28 bazmorty dhcpcd[490]: wlp0s20f3: Router Advertisement from fe80::a697:33ff:fefd:2190
Jan 16 13:53:28 bazmorty dhcpcd[490]: wlp0s20f3: requesting DHCPv6 information
Jan 16 13:53:29 bazmorty dhcpcd[490]: wlp0s20f3: REPLY6 received from fe80::a697:33ff:fefd:2190
Jan 16 13:53:29 bazmorty dhcpcd[490]: wlp0s20f3: refresh in 86400 seconds
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-OLD_NETWORK.device: Job sys-subsystem-net-devices-OLD_NETWORK.device/start timed out.
Jan 16 13:54:49 bazmorty systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/OLD_NETWORK.
Jan 16 13:54:49 bazmorty systemd[1]: Dependency failed for WPA supplicant daemon (for interface OLD_NETWORK).
Jan 16 13:54:49 bazmorty systemd[1]: wpa_supplicant@OLD_NETWORK.service: Job wpa_supplicant@OLD_NETWORK.service/start failed with result 'dependency'.
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-OLD_NETWORK.device: Job sys-subsystem-net-devices-EE-Hub-hxR9.device/start failed with result 'timeout'.
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-CURRENT_NETWORK.device: Job sys-subsystem-net-devices-MOVISTAR_PLUS_2190.device/start timed out.
Jan 16 13:54:49 bazmorty systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/CURRENT_NETWORK.
Jan 16 13:54:49 bazmorty systemd[1]: Dependency failed for WPA supplicant daemon (for interface CURRENT_NETWORK).
Jan 16 13:54:49 bazmorty systemd[1]: wpa_supplicant@CURRENT_NETWORK.service: Job wpa_supplicant@CURRENT_NETWORK.service/start failed with result 'dependency'.
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-NETWORK1.device: Job sys-subsystem-net-devices-CURRENT_NETWORK.device/start failed with result 'timeou>
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-interface.device: Job sys-subsystem-net-devices-interface.device/start timed out.
Jan 16 13:54:49 bazmorty systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/interface.
Jan 16 13:54:49 bazmorty systemd[1]: Dependency failed for WPA supplicant daemon (for interface interface).
Jan 16 13:54:49 bazmorty systemd[1]: wpa_supplicant@interface.service: Job wpa_supplicant@interface.service/start failed with result 'dependency'.
Jan 16 13:54:49 bazmorty systemd[1]: sys-subsystem-net-devices-interface.device: Job sys-subsystem-net-devices-interface.device/start failed with result 'timeout'.

I have a quick look at my conf file:

$ cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/run/wpa_supplicant
update_config=1

network={
	ssid="CURRENT_NETWORK"
	psk="..."
	mesh_fwding=1
}

network={
	ssid="MI 9"
	psk="..."
	mesh_fwding=1
	frequency=5745
}

network={
	ssid="OLD_NETWORK"
	psk="..."
	mesh_fwding=1
}

The service is inactive according to systemctl, but I am able to connect to the wifi.

[baz_morty@bazmorty ~]$ systemctl status wpa_supplicant.service
○ wpa_supplicant.service - WPA supplicant
     Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant.service; disabled; preset: disabled)
     Active: inactive (dead)

I could disable this service using systemctl, but then I think that I would have to manually connect to the wifi each time I boot up my laptop... If that is correct, I am not sure how I can maintain my wifi connections enabled on bootup without disabling the service.

Last edited by prayner96 (2025-01-16 14:07:51)

Offline

#2 2025-01-16 13:48:21

prayner96
Member
Registered: 2022-03-06
Posts: 72

Re: [SOLVED] wpa_supplicant interface service timing out for devices

Ran

sudo systemctl disable wpa_supplicant.service

No change in behaviour

Offline

#3 2025-01-16 13:57:45

prayner96
Member
Registered: 2022-03-06
Posts: 72

Re: [SOLVED] wpa_supplicant interface service timing out for devices

[baz_morty@bazmorty ~]$ sudo systemctl status wpa_supplicant@CURRENT_NETWORK.service
○ wpa_supplicant@CURRENT_NETWORK.service - WPA supplicant daemon (for interface CURRENT_NETWORK)
     Loaded: loaded (/usr/lib/systemd/system/wpa_supplicant@.service; enabled; preset: disabled)
     Active: inactive (dead)

Jan 16 14:52:38 bazmorty systemd[1]: Dependency failed for WPA supplicant daemon (for interface CURRENT_NETWORK).
Jan 16 14:52:38 bazmorty systemd[1]: wpa_supplicant@CURRENT_NETWORK.service: Job wpa_supplicant@CURRENT_NETWORK.service/start failed with result 'dependency'.

Last edited by prayner96 (2025-01-16 13:58:05)

Offline

#4 2025-01-16 14:07:03

prayner96
Member
Registered: 2022-03-06
Posts: 72

Re: [SOLVED] wpa_supplicant interface service timing out for devices

Problem solved. I ran:

sudo systemctl disable wpa_supplicant@CURRENT_NETWORK.service
sudo systemctl disable wpa_supplicant@OLD_NETWORK.service
sudo systemctl disable wpa_supplicant@interface.service

And on reboot, the boot went from 1m39s to 2.5s

graphical.target @2.495s
└─lightdm.service @2.469s +26ms
  └─systemd-user-sessions.service @2.464s +4ms
    └─network.target @2.463s
      └─wpa_supplicant.service @2.454s +9ms
        └─basic.target @2.451s
          └─dbus-broker.service @2.438s +11ms
            └─dbus.socket @2.436s
              └─sysinit.target @2.436s
                └─systemd-update-utmp.service @2.430s +5ms
                  └─systemd-tmpfiles-setup.service @2.399s +30ms
                    └─run-credentials-systemd\x2dtmpfiles\x2dsetup.service.mount @2.402s

I do not understand why my internet is still running.

Offline

#5 2025-01-16 21:04:35

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,245

Re: [SOLVED] wpa_supplicant interface service timing out for devices

WPA_Supplicant can be run standalone but it is more commonly started by another tool.
That can be several but given the dhcpcd error messages your network is probably managed by dhcpcd

Please post the output of systemd-analyze blame .

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

Pages: 1

Board footer

Powered by FluxBB