Wifi keeps disconnecting due to iwd crash

svartkanin · 2022-02-09 07:35:02

For a couple of days now the wifi keeps disconnecting and re-connecting continously for about 10-15min after that it stabilizes eventually and manages to connect without issues.
In the `journalctl` logs I can see entries regarding core dumps

Feb 09 08:18:14 mordor audit[11289]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11289 comm="iwd" exe="/usr/lib/iwd/iwd" sig=11 res=1
Feb 09 08:18:15 mordor systemd-coredump[11306]: Process 11289 (iwd) of user 0 dumped core.
                                                Module iwd with build-id 1f1ffb2da98d28599dcadfea13ccfa00849ce2df
                                                #1  0x00005555b2fd17f2 n/a (iwd + 0x387f2)
                                                #7  0x00005555b2facaba n/a (iwd + 0x13aba)
                                                #9  0x00005555b2fad39e n/a (iwd + 0x1439e)
Feb 09 08:18:15 mordor systemd[1]: iwd.service: Main process exited, code=dumped, status=11/SEGV
Feb 09 08:18:15 mordor systemd[1]: iwd.service: Failed with result 'core-dump'.
Feb 09 08:18:15 mordor audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Feb 09 08:18:15 mordor systemd[1]: iwd.service: Scheduled restart job, restart counter is at 93.
Feb 09 08:18:15 mordor audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 09 08:18:15 mordor audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 09 08:18:15 mordor iwd[11316]: Wireless daemon version 1.24
Feb 09 08:18:15 mordor iwd[11316]: station: Network configuration is disabled.
Feb 09 08:18:15 mordor audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=iwd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Feb 09 08:18:15 mordor iwd[11316]: Wiphy: 0, Name: phy0
Feb 09 08:18:15 mordor iwd[11316]:         Permanent Address: 30:24:32:23:4c:2c
Feb 09 08:18:15 mordor iwd[11316]:         2.4Ghz Band:
Feb 09 08:18:15 mordor iwd[11316]:                 Bitrates (non-HT):
Feb 09 08:18:15 mordor iwd[11316]:                          1.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                          2.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                          5.5 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         11.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                          6.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                          9.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         12.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         18.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         24.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         36.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         48.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         54.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                 HT Capabilities:
Feb 09 08:18:15 mordor iwd[11316]:                         HT40
Feb 09 08:18:15 mordor iwd[11316]:                         Short GI for 20Mhz
Feb 09 08:18:15 mordor iwd[11316]:                         Short GI for 40Mhz
Feb 09 08:18:15 mordor iwd[11316]:                 HT RX MCS indexes:
Feb 09 08:18:15 mordor iwd[11316]:                         0-15
Feb 09 08:18:15 mordor iwd[11316]:         5Ghz Band:
Feb 09 08:18:15 mordor iwd[11316]:                 Bitrates (non-HT):
Feb 09 08:18:15 mordor iwd[11316]:                          6.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                          9.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         12.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         18.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         24.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         36.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         48.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                         54.0 Mbps
Feb 09 08:18:15 mordor iwd[11316]:                 HT Capabilities:
Feb 09 08:18:15 mordor iwd[11316]:                         HT40
Feb 09 08:18:15 mordor iwd[11316]:                         Short GI for 20Mhz
Feb 09 08:18:15 mordor iwd[11316]:                         Short GI for 40Mhz
Feb 09 08:18:15 mordor iwd[11316]:                 HT RX MCS indexes:
Feb 09 08:18:15 mordor iwd[11316]:                         0-15
Feb 09 08:18:15 mordor iwd[11316]:                 VHT Capabilities:
Feb 09 08:18:15 mordor iwd[11316]:                         Short GI for 80Mhz
Feb 09 08:18:15 mordor iwd[11316]:                         Max RX MCS: 0-9 for NSS: 2
Feb 09 08:18:15 mordor iwd[11316]:                         Max TX MCS: 0-9 for NSS: 2
Feb 09 08:18:15 mordor iwd[11316]:         Ciphers: CCMP TKIP BIP
Feb 09 08:18:15 mordor iwd[11316]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Feb 09 08:18:21 mordor iwd[11316]: Unexpected connection related event -- is another supplicant running?
Feb 09 08:18:21 mordor iwd[11316]: Unexpected connection related event -- is another supplicant running?
Feb 09 08:18:30 mordor audit[11316]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11316 comm="iwd" exe="/usr/lib/iwd/iwd" sig=11 res=1
Feb 09 08:18:30 mordor kernel: iwd[11316]: segfault at 1100730103 ip 00007f8d0abab3a3 sp 00007ffc4b9ba410 error 4 in libell.so.0.0.2[7f8d0aba9000+4a000]
Feb 09 08:18:30 mordor kernel: audit: type=1701 audit(1644391110.030:2592): auid=4294967295 uid=0 gid=0 ses=4294967295 pid=11316 comm="iwd" exe="/usr/lib/iwd/iwd" sig=11 res=1
Feb 09 08:18:30 mordor systemd-coredump[11359]: Process 11316 (iwd) of user 0 dumped core.
                                                Module iwd with build-id 1f1ffb2da98d28599dcadfea13ccfa00849ce2df
                                                #1  0x00005598705b67e9 n/a (iwd + 0x387e9)
                                                #7  0x0000559870591aba n/a (iwd + 0x13aba)
                                                #9  0x000055987059239e n/a (iwd + 0x1439e)
Feb 09 08:18:30 mordor systemd[1]: iwd.service: Main process exited, code=dumped, status=11/SEGV
Feb 09 08:18:30 mordor systemd[1]: iwd.service: Failed with result 'core-dump'.

Does anyone know how to debug the issue?

flyingscorpio · 2022-02-09 07:59:44

Do you have other network managers installed?

svartkanin · 2022-02-09 11:11:38

I have

wpa_cli

with

wpa_supplicant

there as well, but that's on it since I installed the system I think. Is there a way to check what else is running on it?

Last edited by svartkanin (2022-02-09 11:12:13)

V1del · 2022-02-09 11:19:29

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f #This should only contain one networking service
sudo journalctl -b #Check/post the entire output without filtering for iwd

Generally if you use networkmanager and expect to be able to click something to connect to a network you have conflicting networking services. NetworkManager uses wpa_supplicant by default and you absolutely need to disable iwd and not use iwctl if you intend for this to work or configure NetworkManager to use iwd rather than wpa_supplicant as the backend.

svartkanin · 2022-02-09 11:24:07

This is the output for the first command

automatic-backup.service                 | system
bluetooth.service                        | bluetooth.target.wants
dbus-org.bluez.service                   | system
dbus-org.freedesktop.network1.service    | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
docker.service                           | multi-user.target.wants
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
iwd.service                              | multi-user.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
ntpd.service                             | multi-user.target.wants
numLockOnTty.service                     | multi-user.target.wants
p11-kit-server.socket                    | sockets.target.wants
pamac-cleancache.timer                   | timers.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-pulse.socket                    | sockets.target.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
systemd-networkd.service                 | multi-user.target.wants
systemd-networkd.socket                  | sockets.target.wants
systemd-networkd-wait-online.service     | network-online.target.wants
systemd-resolved.service                 | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
xdg-user-dirs-update.service             | default.target.wants

V1del · 2022-02-09 12:30:34

three conflicting services... Which tutorial or instructions did you use here? This is the third time in two weeks I'm seeing this, whichever tutorial you all are following needs to stop doing this .

If you intend to click on something to manage wifi you need to stop iwd and all three systemd-networkd services. NetworkManager should be the only thing that's listed in that list with relation to networking.

Last edited by V1del (2022-02-09 12:30:55)

jprestwo · 2022-02-09 20:49:33

V1del wrote:

three conflicting services... Which tutorial or instructions did you use here? This is the third time in two weeks I'm seeing this, whichever tutorial you all are following needs to stop doing this .
If you intend to click on something to manage wifi you need to stop iwd and all three systemd-networkd services. NetworkManager should be the only thing that's listed in that list with relation to networking.

systemd-networkd shouldn't be an issue AFAIK. IWD doesn't do any IP/DNS configuration unless enabled. NetworkManager may also get people into trouble unless the backend is set right. Maybe the NM service even starts wpa_supplicant? I have no idea.

I what might help is updating the wiki. The "installation" section is all but non-existant, and there is nothing about these conflicting pieces of software. If someone has an Arch install with wpa_supplicant + NM and they want IWD, following the wiki will get them into this exact situation.

svartkanin · 2022-02-09 21:35:59

I've used archinsall (provided within the arch ISO) to setup the system, I didn't look under the hood what exact network mangers it's installing but it might be doing too much magic there...

I removed iwd now, rebooted, had to explicitly enable wpa_supplicant service and now it seems to be stable with NetworkManager

seth · 2022-02-09 22:45:14

had to explicitly enable wpa_supplicant service

NM defaults to wpa_supplicant to provide a wifi carrier, explicitly enabling will likely cause competitive wpa_supplicant's and in any event, NM and systemd-networkd are in conflict for sure.

Alad · 2022-02-10 10:22:55

I what might help is updating the wiki.

Since iwd segfaulted, what would help the most is file a bug report on flyspray or upstream.

Some references were added with https://wiki.archlinux.org/index.php?ti … did=717569 and https://wiki.archlinux.org/index.php?ti … did=717436

Arch Linux

#1 2022-02-09 07:35:02

Wifi keeps disconnecting due to iwd crash

#2 2022-02-09 07:59:44

Re: Wifi keeps disconnecting due to iwd crash

#3 2022-02-09 11:11:38

Re: Wifi keeps disconnecting due to iwd crash

#4 2022-02-09 11:19:29

Re: Wifi keeps disconnecting due to iwd crash

#5 2022-02-09 11:24:07

Re: Wifi keeps disconnecting due to iwd crash

#6 2022-02-09 12:30:34

Re: Wifi keeps disconnecting due to iwd crash

#7 2022-02-09 20:49:33

Re: Wifi keeps disconnecting due to iwd crash

#8 2022-02-09 21:35:59

Re: Wifi keeps disconnecting due to iwd crash

#9 2022-02-09 22:45:14

Re: Wifi keeps disconnecting due to iwd crash

#10 2022-02-10 10:22:55

Re: Wifi keeps disconnecting due to iwd crash

Board footer