Bug 196361 - ath10k qca6174 hw 2.1 gets stuck after some time
Summary: ath10k qca6174 hw 2.1 gets stuck after some time
Status: RESOLVED WILL_NOT_FIX
Alias: None
Product: Networking
Classification: Unclassified
Component: Wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: networking_wireless@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-07-14 01:14 UTC by Stijn Tintel
Modified: 2021-12-08 09:44 UTC (History)
3 users (show)

See Also:
Kernel Version: 4.12
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg (96.55 KB, text/plain)
2017-07-14 01:17 UTC, Stijn Tintel
Details

Description Stijn Tintel 2017-07-14 01:14:45 UTC
Reporting a new bug as #196033 is for a different hw revision, and I'm seeing other things in dmesg.

After reconnecting from one AP to another and back a couple of times, and a firmware crash on *every* attempt (#195987), the driver gets stuck:

sylvester ~ # time iw wlan0 scan
command failed: Network is down (-100)

real    0m0.759s
user    0m0.000s
sys     0m0.003s
sylvester ~ # time ip link set dev wlan0 up
RTNETLINK answers: Resource temporarily unavailable

real    0m7.242s
user    0m0.000s
sys     0m0.003s

After unloading and reloading the ath10k_pci module, I am able to scan and associate again.
Comment 1 Stijn Tintel 2017-07-14 01:17:20 UTC
Created attachment 257505 [details]
dmesg
Comment 2 Michal Hlavac 2017-08-21 22:07:33 UTC
Can confirm problems with 4.12.8 and that it works with 4.11.8.
I have Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter with opensuse Tumbleweed.
Workaround is to run nmcli con up <NAME>, but it occurs too often (cca every 10 minutes).
Comment 3 Christoph K. 2017-08-22 07:16:03 UTC
This seems to be a bug with a newer firmware used by 4.12.

See this thread for a workaround:

https://bbs.archlinux.org/viewtopic.php?id=228793
Comment 4 Stijn Tintel 2021-12-08 09:44:48 UTC
Apparently nobody gives a damn. The card is where it belongs, in the trash. Together with all other QCA hardware I used to own.

Note You need to log in before you can comment on or make changes to this bug.