FS#62615 - [wpa_supplicant] WiFi network unreliable since update to wpa_supplicant 2.8

Attached to Project: Arch Linux
Opened by Johannes Maibaum (jmx) - Sunday, 12 May 2019, 10:58 GMT
Last edited by Antonio Rojas (arojas) - Monday, 27 May 2019, 16:33 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Since the update to wpa_supplicant 2.8-1, my WiFi network connection at home is next to unusable. While general web browsing seems to be possible (with lots of patience), trying anything else on the network is next to impossible.

- ssh'ing to another machine on my network kind of works, but with significant lags.
- ping'ing even my access point/router times out 99% of the time
- arp-scan doesn't work at all (reports 0 other machines on the network)

Connecting to my home network via ethernet cable fixes all of the above, as well as downgrading wpa_supplicant to package version 2.6-2 brings WiFi network performance back to normal.

Additional info:
* "bad" wpa_supplicant package version: 2.8-1; "good" package version: 2.6-2
* networkmanager 1.18.0-1
* uname -a: Linux <...> 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux


lshw output for my wifi adapter (queried, while I am on 2.6-2):
*-network
description: Wireless interface
product: QCA6174 802.11ac Wireless Network Adapter
vendor: Qualcomm Atheros
physical id: 0
bus info: pci@0000:3a:00.0
logical name: wlp58s0
version: 32
serial: 9c:b6:d0:d3:0f:79
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=ath10k_pci driverversion=5.0.13-arch1-1-ARCH firmware=RM.4.4.1.c2-00057-QCARMSWP-1 ip=192.168.<x.x> latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: irq:136 memory:dc000000-dc1fffff

* I could not find any official upstream bug tracker (or even general info on where to post bug reports apart from than sending them directly to j at w1 dot fi, which might be a little over the top at this point) at https://w1.fi/wpa_supplicant/, so gave up trying to report there for the moment. Might be worth posting to their mailing list, but I didn't have time yet to read through their archive to see if there is any similar reports.

Steps to reproduce:
For me, it's just a matter of switching back and forth between wpa_supplicant 2.8-1 and 2.6-2, but YMMV.

Any hints on where to search for more detailed logs is highly appreciated, as I'm struggling to find more info on what is actually going wrong on 2.8-1.
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 27 May 2019, 16:33 GMT
Reason for closing:  Not a bug
Comment by Johannes Maibaum (jmx) - Tuesday, 14 May 2019, 19:05 GMT
I have added two logs of two quick boots where I did the following using wpa_supplicant 2.8-1 and wpa_supplicant 2.6-2:

1. Enable verbose debugging messages shortly after bootup using these commands (taken from: https://wiki.gnome.org/Projects/NetworkManager/Debugging):

sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugTimestamp variant:boolean:true

sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1 /fi/w1/wpa_supplicant1 org.freedesktop.DBus.Properties.Set string:fi.w1.wpa_supplicant1 string:DebugLevel variant:string:"msgdump"

2. Trying an arp-scan around my local network using my WiFi device (0 hosts responded using v2.8, a sane amount of hosts responded using v2.6)

3. Trying to ping my router (.1) in my network 5 times (timed out 100% using v2.8, worked flawlessly using v2.6)

4. Waited for the next automatic WiFi rescan by network-manager to appear in the messages

5. Rebooted


Any hints what resources might be helpful to gather logs from next would be highly appreciated!

Comment by Johannes Maibaum (jmx) - Sunday, 19 May 2019, 16:21 GMT
I found out that my issue was not related to wpa_supplicant. It turned out to be a firmware issue with my Qualcom QCA6174 wifi module.

Manually installing `firmware-6.bin_WLAN.RM.4.4.1.c3-00030` from https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1.c3 fixed this.

This bug report can be closed as invalid.

Loading...