You are not logged in.

#1 2024-08-31 11:43:15

0x4248
Member
Registered: 2024-08-31
Posts: 5

WiFi broken after recent update

After recently updating arch linux on my razer blade 15 2021 base connecting to a network trough the KDE network panel seems to not work.

Networks show up but then it seems the network turns off.

Looking in journalctl i can see that iwd is getting a segfault when using the KDE ui to connect. Using iwd without the NetworkManager service running seems to work fine. Here is what journalctl looks like.

Aug 31 12:17:55 razer iwd[2313]:         2.4GHz Band:
Aug 31 12:17:46 razer NetworkManager[2038]: <info>  [1725103066.3378] device (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "XXXXXXXXXXX
Aug 31 12:17:46 razer NetworkManager[2038]: <info>  [1725103066.3378] device (p2p-dev-wlan0): supplicant management interface state: 4way_handshake -> completed
Aug 31 12:17:46 razer wpa_supplicant[2045]: wlan0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-57 noise=9999 txrate=490000
Aug 31 12:17:46 razer NetworkManager[2038]: <info>  [1725103066.3384] device (wlan0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Aug 31 12:17:46 razer NetworkManager[2038]: <info>  [1725103066.3397] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.3657] dhcp4 (wlan0): state changed new lease, address=XXXXXXXX, acd pending
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5609] dhcp4 (wlan0): state changed new lease, address=XXXXXXXX
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5620] policy: set 'XXXXXXXX' (wlan0) as default for IPv4 routing and DNS
Aug 31 12:17:47 razer NetworkManager[2038]: <warn>  [1725103067.5878] dns-sd-resolved[88be0506e5cab141]: send-updates SetLinkDomains@4 failed: GDBus.Error:org.freedesktop.resolve1.LinkBusy: >
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5883] device (wlan0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5928] device (wlan0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5932] device (wlan0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5940] manager: NetworkManager state is now CONNECTED_SITE
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.5957] device (wlan0): Activation: successful, device activated.
Aug 31 12:17:47 razer systemd-networkd[716]: wlan0: Gained IPv6LL
Aug 31 12:17:47 razer NetworkManager[2038]: <info>  [1725103067.6349] audit: op="statistics" interface="wlan0" ifindex=4 args="2000" pid=1223 uid=1000 result="success"
Aug 31 12:17:48 razer NetworkManager[2038]: <info>  [1725103068.9222] dhcp6 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Aug 31 12:17:48 razer NetworkManager[2038]: <info>  [1725103068.9233] policy: set 'XXXXXXXX' (wlan0) as default for IPv6 routing and DNS
Aug 31 12:17:55 razer kernel: iwd[771]: segfault at 28 ip 00005d3121738932 sp 00007ffcc0a13688 error 4 in iwd[38932,5d3121709000+a0000] likely on CPU 0 (core 0, socket 0)
Aug 31 12:17:55 razer kernel: Code: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Aug 31 12:17:55 razer systemd-coredump[2292]: Process 771 (iwd) of user 0 terminated abnormally with signal 11/SEGV, processing...
Aug 31 12:17:55 razer systemd[1]: Created slice Slice /system/drkonqi-coredump-processor.
Aug 31 12:17:55 razer systemd[1]: Created slice Slice /system/systemd-coredump.
Aug 31 12:17:55 razer systemd[1]: Started Process Core Dump (PID 2292/UID 0).
Aug 31 12:17:55 razer systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Aug 31 12:17:55 razer sudo[2277]:     blix : TTY=pts/2 ; PWD=/home/blix ; USER=root ; COMMAND=/usr/bin/journalctl --follow
Aug 31 12:17:55 razer systemd-coredump[2293]: [?] Process 771 (iwd) of user 0 dumped core.
                                             
                                              Stack trace of thread 771:
                                              #0  0x00005d3121738932 n/a (iwd + 0x38932)
                                              #1  0x00007af997369bbd n/a (libell.so.0 + 0x1dbbd)
                                              #2  0x00007af9973643cb n/a (libell.so.0 + 0x183cb)
                                              #3  0x00007af997364655 l_main_iterate (libell.so.0 + 0x18655)
                                              #4  0x00007af997364ace l_main_run (libell.so.0 + 0x18ace)
                                              #5  0x00007af9973663a4 l_main_run_with_signal (libell.so.0 + 0x1a3a4)
                                              #6  0x00005d312170bd30 n/a (iwd + 0xbd30)
                                              #7  0x00007af997152e08 n/a (libc.so.6 + 0x25e08)
                                              #8  0x00007af997152ecc __libc_start_main (libc.so.6 + 0x25ecc)
                                              #9  0x00005d312170c585 n/a (iwd + 0xc585)
                                              ELF object binary architecture: AMD x86-64
Aug 31 12:17:55 razer sudo[2277]: pam_unix(sudo:session): session opened for user root(uid=0) by blix(uid=1000)
Aug 31 12:17:55 razer systemd[1]: systemd-coredump@0-2292-0.service: Deactivated successfully.
Aug 31 12:17:55 razer systemd[1]: iwd.service: Main process exited, code=dumped, status=11/SEGV
Aug 31 12:17:55 razer systemd[1]: iwd.service: Failed with result 'core-dump'.
Aug 31 12:17:55 razer kernel: wlan0: deauthenticating from XXXXXXXXXXXXXXXX by local choice (Reason: 3=DEAUTH_LEAVING)
Aug 31 12:17:55 razer wpa_supplicant[2045]: wlan0: CTRL-EVENT-DISCONNECTED bssid=XXXXXXXXXXXXXXXX reason=3 locally_generated=1
Aug 31 12:17:55 razer wpa_supplicant[2045]: wlan0: Added BSSID XXXXXXXXXXXXXXXX into ignore list, ignoring for 10 seconds
Aug 31 12:17:55 razer wpa_supplicant[2045]: wlan0: BSSID XXXXXXXXXXXXXXXX ignore list count incremented to 2, ignoring for 10 seconds
Aug 31 12:17:55 razer systemd-networkd[716]: wlan0: Link DOWN

Offline

#2 2024-08-31 13:25:30

gromit
Package Maintainer (PM)
From: Germany
Registered: 2024-02-10
Posts: 1,173
Website

Re: WiFi broken after recent update

Are you using the testing repositories? https://lists.archlinux.org/archives/li … 2LWEBGOX7/

Offline

#3 2024-08-31 13:34:45

0x4248
Member
Registered: 2024-08-31
Posts: 5

Re: WiFi broken after recent update

Sorry i forgot to mention, no I am not.
I posted on reddit to see if anyone else is affected and it seems several people are having this issue
https://www.reddit.com/r/archlinux/comm … _updating/

Offline

#4 2024-08-31 13:39:48

gromit
Package Maintainer (PM)
From: Germany
Registered: 2024-02-10
Posts: 1,173
Website

Re: WiFi broken after recent update

So which versions of iwd and ell do you have installed? (pacman -Q iwd ell)

Offline

#5 2024-08-31 14:53:01

0x4248
Member
Registered: 2024-08-31
Posts: 5

Re: WiFi broken after recent update

iwd 2.20-1
ell 0.68-1

A peron on reddit: https://www.reddit.com/r/archlinux/comm … are_button
said that downgrading these fixes the issues

sudo pacman -U file:///var/cache/pacman/pkg/iwd-2.19-1-x86_64.pkg.tar.zst
sudo pacman -U file:///var/cache/pacman/pkg/ell-0.67-1-x86_64.pkg.tar.zst

Offline

#6 2024-08-31 14:57:35

0x4248
Member
Registered: 2024-08-31
Posts: 5

Re: WiFi broken after recent update

This has now fixed the issue

Offline

#7 2024-08-31 15:00:10

gromit
Package Maintainer (PM)
From: Germany
Registered: 2024-02-10
Posts: 1,173
Website

Re: WiFi broken after recent update

Yes, but this means that you have enabled the testing repositories, as this is the very ell version that has been pulled from testing, please check your "/etc/pacman.conf"!

See the answers below!

Last edited by gromit (2024-08-31 15:06:47)

Offline

#8 2024-08-31 15:01:46

Scimmia
Fellow
Registered: 2012-09-01
Posts: 12,874

Re: WiFi broken after recent update

with the IWD update, ell was re-updated and moved to Extra.

Offline

#9 2024-08-31 15:04:16

WorMzy
Administrator
From: Scotland
Registered: 2010-06-16
Posts: 12,876
Website

Re: WiFi broken after recent update

Version 0.68-1 of ell is in extra: https://archlinux.org/packages/extra/x86_64/ell/

Edit: should've refreshed.

Last edited by WorMzy (2024-08-31 15:04:58)


Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Offline

#10 2024-08-31 15:52:06

0x4248
Member
Registered: 2024-08-31
Posts: 5

Re: WiFi broken after recent update

gromit wrote:

Yes, but this means that you have enabled the testing repositories, as this is the very ell version that has been pulled from testing, please check your "/etc/pacman.conf"!

See the answers below!


Yeah i havent got testing on just checked

Offline

#11 2024-08-31 19:58:35

kecef
Member
Registered: 2014-06-05
Posts: 7

Re: WiFi broken after recent update

Same issue on my laptop after today's update.
I've got tons of these messages in dmesg:

[ 1024.299548] wlan0: authenticate with xx:xx:xx:xx:xx:xx
[ 1024.304573] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 1032.458279] iwd[5251]: segfault at 28 ip 000064621c03a932 sp 00007fff4127aa88 error 4 in iwd[64621c00b000+a0000] likely on CPU 2 (core 0, socket 0)
[ 1032.458322] Code: 8b 7b 20 67 e8 3f 7a 06 00 48 89 df 48 8b 5d f8 c9 ff 25 09 98 0a 00 90 f3 0f 1e fa 48 8b 07 c7 40 60 00 00 00 00 48 8b 47 18 <f6> 40 28 01 75 08 e9 d3 f8 ff ff 0f 1f 00 e9 5b ff ff ff 66 66 2e
[ 1032.514642] wlan0: authenticate with xx:xx:xx:xx:xx:xx
[ 1032.519870] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 1044.314577] iwd[5315]: segfault at 28 ip 000064e640deb932 sp 00007ffec2a0c228 error 4 in iwd[64e640dbc000+a0000] likely on CPU 1 (core 1, socket 0)
[ 1044.314619] Code: 8b 7b 20 67 e8 3f 7a 06 00 48 89 df 48 8b 5d f8 c9 ff 25 09 98 0a 00 90 f3 0f 1e fa 48 8b 07 c7 40 60 00 00 00 00 48 8b 47 18 <f6> 40 28 01 75 08 e9 d3 f8 ff ff 0f 1f 00 e9 5b ff ff ff 66 66 2e
[ 1044.315778] wlan0: authenticate with xx:xx:xx:xx:xx:xx
[ 1044.321086] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 1/3)
[ 1044.450207] wlan0: send auth to xx:xx:xx:xx:xx:xx (try 2/3)
[ 1044.451298] wlan0: authenticated
[ 1044.453559] wlan0: associate with xx:xx:xx:xx:xx:xx (try 1/3)
[ 1044.457297] wlan0: RX AssocResp from xx:xx:xx:xx:xx:xx (capab=0x1511 status=0 aid=3)
[ 1044.463924] wlan0: associated
[ 1044.493733] wlan0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING)
[ 1051.884449] iwd[5340]: segfault at 28 ip 000064434a58c932 sp 00007ffe660dc368 error 4 in iwd[64434a55d000+a0000] likely on CPU 1 (core 1, socket 0)
[ 1051.884491] Code: 8b 7b 20 67 e8 3f 7a 06 00 48 89 df 48 8b 5d f8 c9 ff 25 09 98 0a 00 90 f3 0f 1e fa 48 8b 07 c7 40 60 00 00 00 00 48 8b 47 18 <f6> 40 28 01 75 08 e9 d3 f8 ff ff 0f 1f 00 e9 5b ff ff ff 66 66 2e

Offline

#12 2024-08-31 22:36:25

loqs
Member
Registered: 2014-03-06
Posts: 18,471

Re: WiFi broken after recent update

Offline

#13 2024-09-01 08:31:15

seth
Member
Registered: 2012-09-03
Posts: 65,769

Re: WiFi broken after recent update

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00005ffa6a0376de in get_survey_done (user_data=0x5ffa783a3f90) at src/scan.c:2059
2059            if (!results->sr->canceled)
(gdb) backtrace
#0  0x00005ffa6a0376de in get_survey_done (user_data=0x5ffa783a3f90) at src/scan.c:2059
#1  0x0000749646a29bbd in ?? () from /usr/lib/libell.so.0
#2  0x0000749646a243cb in ?? () from /usr/lib/libell.so.0
#3  0x0000749646a24655 in l_main_iterate () from /usr/lib/libell.so.0
#4  0x0000749646a24ace in l_main_run () from /usr/lib/libell.so.0
#5  0x0000749646a263a4 in l_main_run_with_signal () from /usr/lib/libell.so.0
#6  0x00005ffa6a00d642 in main (argc=<optimized out>, argv=<optimized out>) at src/main.c:614

https://git.kernel.org/pub/scm/network/ … 89d982d080 unconditioanlly dereferences results and results->sr
https://git.kernel.org/pub/scm/network/ … d080#n1986 indicates that results->sr might be invalid.

Offline

#14 2024-09-02 16:28:18

smolloy
Member
Registered: 2024-03-07
Posts: 11

Re: WiFi broken after recent update

For what it's worth, I was hit by this as well.  Watching "journalctl -f" I managed to catch one of the crashes.

Sep 02 14:32:32 archdell systemd[1]: drkonqi-coredump-processor@31-15064-0.service: Deactivated successfully.
Sep 02 14:32:32 archdell kernel: wlan0: deauthenticating from d6:92:5e:2c:9c:47 by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 02 14:32:32 archdell drkonqi-coredump-processor[15066]: The socket path doesn't exist @ "/run/user/0/drkonqi-coredump-launcher"
Sep 02 14:32:32 archdell drkonqi-coredump-processor[15066]: "/usr/lib/iwd/iwd" 14715 "/var/lib/systemd/coredump/core.iwd.0.bbbb6c6a26d14b7a80222bcbf920cf16.14715.1725280352000000.zst"
Sep 02 14:32:32 archdell systemd[1]: systemd-coredump@31-15064-0.service: Deactivated successfully.
Sep 02 14:32:32 archdell systemd[1]: iwd.service: Failed with result 'core-dump'.
Sep 02 14:32:32 archdell systemd[1]: iwd.service: Main process exited, code=dumped, status=11/SEGV
Sep 02 14:32:32 archdell systemd-coredump[15065]: [?] Process 14715 (iwd) of user 0 dumped core.

                                                  Stack trace of thread 14715:
                                                  #0  0x000063dbc1ca6932 n/a (iwd + 0x38932)
                                                  #1  0x000077903d8e3bbd n/a (libell.so.0 + 0x1dbbd)
                                                  #2  0x000077903d8de3cb n/a (libell.so.0 + 0x183cb)
                                                  #3  0x000077903d8de655 l_main_iterate (libell.so.0 + 0x18655)
                                                  #4  0x000077903d8deace l_main_run (libell.so.0 + 0x18ace)
                                                  #5  0x000077903d8e03a4 l_main_run_with_signal (libell.so.0 + 0x1a3a4)
                                                  #6  0x000063dbc1c79d30 n/a (iwd + 0xbd30)
                                                  #7  0x000077903d6cce08 n/a (libc.so.6 + 0x25e08)
                                                  #8  0x000077903d6ccecc __libc_start_main (libc.so.6 + 0x25ecc)
                                                  #9  0x000063dbc1c7a585 n/a (iwd + 0xc585)
                                                  ELF object binary architecture: AMD x86-64
Sep 02 14:32:32 archdell systemd[1]: Started Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
Sep 02 14:32:32 archdell systemd[1]: Started Process Core Dump (PID 15064/UID 0).
Sep 02 14:32:32 archdell systemd-coredump[15064]: Process 14715 (iwd) of user 0 terminated abnormally with signal 11/SEGV, processing...

Rolling back iwd and ell fixed the issue.  It's possible that I didn't have to roll back both.  Perhaps just one would have been enough.

(It made we wonder why this would be crashing so often (roughly every five minutes), and I found that there was more than one supplicant running.  I disabled iwd and enabled NetworkManager and wpa_supplicant, and now all is running as it should.)

Offline

#15 2024-09-02 16:34:14

loqs
Member
Registered: 2014-03-06
Posts: 18,471

Re: WiFi broken after recent update

The issue should be fixed in iwd 2.20-2 although having multiple processes trying to control the same interface is not ideal.

Offline

#16 2024-09-02 19:50:00

seth
Member
Registered: 2012-09-03
Posts: 65,769

Re: WiFi broken after recent update

As a matter of fact it matches my gut feeling in the bug why people run into the survey failure itfp…

Offline

#17 2024-09-03 13:44:37

PotHix
Member
Registered: 2024-09-03
Posts: 1

Re: WiFi broken after recent update

smolloy wrote:

(It made we wonder why this would be crashing so often (roughly every five minutes), and I found that there was more than one supplicant running.  I disabled iwd and enabled NetworkManager and wpa_supplicant, and now all is running as it should.)

Thanks for mentioning that. It was the same thing for me (crashing very often), and I also had both running. Just kept one of them as well. smile

Offline

Board footer

Powered by FluxBB