Skip to main content
Start a Conversation

Unsolved

This post is more than 5 years old

R

rudiw

24 Posts

12968

January 14th, 2017 17:00

wifi adapter firmware crash?

I'm running Ubuntu 16.10 on my XPS 13 kaby lake, and I'm having quite annoying stability problems, that force a restart every hour or so. I can't the cause of the problems down exactly, as the symptoms are inconsistent, but I'll try to post them here once they occur.

A.
Symptom: lagging internet, no connection at times, ping mosty good though. Youtube videos load/buffer, but mysteriously won't play. Speedtest.net stuck on 'connecting', but this site does load. Very strange.

Output of dmesg:

(...)
[    9.298826] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2
[    9.298840] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
[    9.299374] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    9.299377] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[    9.302836] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
(...)
[ 6339.841272] wlp58s0: AP 88:03:55:f4:9c:e8 changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)
[ 6366.148122] ath10k_pci 0000:3a:00.0: firmware crashed! (uuid 8b4464c0-1f1e-406c-866d-282fcfd1e9cc)
[ 6366.148127] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[ 6366.148128] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[ 6366.148506] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[ 6366.148682] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[ 6366.148683] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 6366.150684] ath10k_pci 0000:3a:00.0: firmware register dump:
[ 6366.150686] ath10k_pci 0000:3a:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[ 6366.150687] ath10k_pci 0000:3a:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[ 6366.150688] ath10k_pci 0000:3a:00.0: [08]: 0x00498110 0x00955A00 0x0000000B 0x00400000
[ 6366.150689] ath10k_pci 0000:3a:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[ 6366.150690] ath10k_pci 0000:3a:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[ 6366.150691] ath10k_pci 0000:3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[ 6366.150692] ath10k_pci 0000:3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[ 6366.150693] ath10k_pci 0000:3a:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313B8
[ 6366.150694] ath10k_pci 0000:3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 0x00429548
[ 6366.150695] ath10k_pci 0000:3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000002
[ 6366.150696] ath10k_pci 0000:3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[ 6366.150697] ath10k_pci 0000:3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[ 6366.150698] ath10k_pci 0000:3a:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[ 6366.150699] ath10k_pci 0000:3a:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[ 6366.150699] ath10k_pci 0000:3a:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[ 6366.248857] ieee80211 phy0: Hardware restart was requested
[ 6368.660835] ath10k_pci 0000:3a:00.0: device successfully recovered
(...)
11540.298003] wlp58s0: AP 88:03:55:f4:9c:e8 changed bandwidth, new config is 2462 MHz, width 2 (2452/0 MHz)
[11540.338899] ath10k_pci 0000:3a:00.0: firmware crashed! (uuid c59533d0-3f26-4fab-aac0-8fc4ff707dbb)
[11540.338916] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[11540.338939] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[11540.340716] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[11540.341490] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[11540.341496] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[11540.343543] ath10k_pci 0000:3a:00.0: firmware register dump:
[11540.343556] ath10k_pci 0000:3a:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[11540.343564] ath10k_pci 0000:3a:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[11540.343572] ath10k_pci 0000:3a:00.0: [08]: 0x00498110 0x00955A00 0x0000000B 0x00400000
[11540.343579] ath10k_pci 0000:3a:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[11540.343585] ath10k_pci 0000:3a:00.0: [16]: 0x00952CC4 0x000B5990 0x00000000 0x0091080D
[11540.343592] ath10k_pci 0000:3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[11540.343599] ath10k_pci 0000:3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[11540.343605] ath10k_pci 0000:3a:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313DC
[11540.343611] ath10k_pci 0000:3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548
[11540.343619] ath10k_pci 0000:3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000001
[11540.343629] ath10k_pci 0000:3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[11540.343636] ath10k_pci 0000:3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[11540.343643] ath10k_pci 0000:3a:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[11540.343650] ath10k_pci 0000:3a:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[11540.343657] ath10k_pci 0000:3a:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[11540.443459] ieee80211 phy0: Hardware restart was requested
[11542.928535] ath10k_pci 0000:3a:00.0: device successfully recovered
[11615.657666] wlp58s0: AP 88:03:55:f4:9c:e8 changed bandwidth, new config is 2462 MHz, width 1 (2462/0 MHz)

B.

I can connect a bluetooth speaker, but the device doesn't show up under "Sound Settings...". The output of dmesg:

[  300.662152] mce: [Hardware Error]: Machine check events logged
[ 1889.286852] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=113823 end=113824) time 165 us, min 1073, max 1079, scanline start 1072, end 1083
[ 2021.106323] input: 88:C6:26:C7:E0:8F as /devices/virtual/input/input24
[ 2880.210454] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=164643 end=164644) time 151 us, min 1192, max 1199, scanline start 1191, end 1203
[ 2957.603851] input: 88:C6:26:C7:E0:8F as /devices/virtual/input/input25
[ 2973.092613] input: 88:C6:26:C7:E0:8F as /devices/virtual/input/input26
[ 3003.939216] input: 88:C6:26:C7:E0:8F as /devices/virtual/input/input27

Any help is greatly appreciated, as this system is impossible to work with

beurle

10 Posts

May 8th, 2017 02:00

I have been using this for a week and no dropouts, tried all the likely places including airport WiFi. It seems to be up a little earlier on boot. Ping times to the AP don't seem to be as consistently low as I remember Intel wireless to be.

I'd call it fixed!

DELL-Justin C

4 Operator

 • 

783 Posts

May 10th, 2017 16:00

@Bit101 and Beurle,

Glad to hear that, thank you for your feedback.

Would you both be able to share with me the make(s)/model(s) of access points you use?

@Community,

If there are any remaining concerns after the firmware update, please let me know and include what make(s)/model(s) of access points connected to while having any concerns.

jospoortvliet

3 Posts

October 22nd, 2017 04:00

Justin,

I went through the process of updating the firmware on my Dell XPS 13 9360 which suffered from wifi connection breaking sometimes every 5 minutes - it seemed whenever a certain amount of data was transferred, the wifi would stop receiving/transmitting though apps would think the connection was still up. They just wouldn't get any data... I would have to turn on/off the wifi. Interestingly, the touchpad would also frequently lose its multi-touch capabilities, often immediately after restarting the wifi.

I run openSUSE Tumbleweed which has kernel 4.13.6 right now.

But whatever the causes and weird interactions, I updated to the latest firmware following the process above (using openSUSE equivalents) and lo and behold, the issues are gone completely! Wifi has been stable and the touchpad hasn't shown a single hiccup.

So: THANK YOU!

EDIT: you asked for access point info. I run a Archer C7 with OpenWRT 15.05.1 on it.

hamkaas

13 Posts

October 24th, 2017 13:00

Hi Justin,

Like Jos I 'm also using a Dell XPS 13 9360 with Tumbleweed.
And maybe Tumbleweed users are in luck.
OpenSuse just released a new snapshot that perhaps fixes this particular issue.
Except from the connection stopping after 10 minutes it was quite stable for many months and performed well.

I was filing a bug report for Tumbleweed just before i noticed the update.
Technical details are here:
bugzilla.opensuse.org/show_bug.cgi

In a nutshell:
My specific issue seems to be fixed in WLAN.RM.4.4.1-00051-QCARMSWP-1(firmware-6.bin) which has been commited to the official linux firmware repository on 2017-10-09. That firmware update was added to the Tumbleweed snapshot today.

Replacing single firmware files should only be done for testing purpose in my opinion.
In case an update for the firmware package is installed, all changes are lost or you are left with a mix of files.

What probably solved it for you Jos was that following the instruction from Justin you deleted the entire folder QCA6174. That resulted in firmware-6.bin not being found but instead loaded firmware-4.bin containing WLAN.RM.2.0-00180-QCARMSWPZ-1. Which is the same version as in the current Tumbleweed package.

As for Ubuntu:
Both 16.04.3 (proposed repo) and 17.10 appear to have firmware-6.bin containing WLAN.RM.4.4-00022-QCARMSWPZ-2 which is the same as the one I had my issue with.
So I wonder:

1. Do Ubuntu 17.10 users now have the same issue Jos and I had? so after 10 minutes the connection stops responding?

2. In case the package from 16.04.3 (proposed repo) lands as an update, will they also have this issue?

extra note
In my understanding, if a firmware-6.bin is installed, it will be loaded instead of firmware-4.bin.
Thats why some people on Arch simply deleted or renamed firmware-6.bin
bbs.archlinux.org/viewtopic.php

Router: TP-Link Archer C7 v2 (rebranded router from my ISP) with LEDE Reboot 17.01.4

EDIT: formatting

DELL-Justin C

4 Operator

 • 

783 Posts

October 24th, 2017 18:00

@Jospoortvliet,

Thank you for sharing your experience and details here on the Dell Community. Glad to hear the firmware update helped you out.

@Hamkaas,

Thank you for your detailed account and questions. I actually don't know if owners with 16.04.3 and 17.10 are having the same issue. Due to your feedback, what we might do here is look into updating my firmware update post, as well as the official Dell knowledge base document, to include this latest firmware you found. I will work on that.

Thank you!

garakkio

2 Posts

January 31st, 2018 05:00

I followed the KB guide, but my wireless is still not working on many wifi networks (weird, because on some networks is working indeed).

Attached output from dmesg

[mer gen 31 12:06:10 2018] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[mer gen 31 12:06:10 2018] Bridge firewalling registered
[mer gen 31 12:06:10 2018] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[mer gen 31 12:06:10 2018] ip_tables: (C) 2000-2006 Netfilter Core Team
[mer gen 31 12:06:10 2018] Initializing XFRM netlink socket
[mer gen 31 12:06:10 2018] Netfilter messages via NETLINK v0.30.
[mer gen 31 12:06:10 2018] ctnetlink v0.93: registering with nfnetlink.
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-24b5655002d4: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-52995785ae2f: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-6134212654af: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-9a89a5518af9: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-cd2899cd3790: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-08687e20ae4f: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-91b48082c5ad: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-ae2a6b225cc2: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-ee073608dcb5: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-f1b59750ff89: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-684419f1679d: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[mer gen 31 12:06:10 2018] IPv6: ADDRCONF(NETDEV_UP): br-995c1bc81218: link is not ready
[mer gen 31 12:06:11 2018] IPv6: ADDRCONF(NETDEV_UP): br-b6e431f70d4d: link is not ready
[mer gen 31 12:06:11 2018] IPv6: ADDRCONF(NETDEV_UP): br-c92e4f9aa0c2: link is not ready
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[mer gen 31 12:06:12 2018] Non-volatile memory driver v1.3
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3a:00.0.bin failed with error -2
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[mer gen 31 12:06:12 2018] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 20d869c3
[mer gen 31 12:06:14 2018] ath10k_pci 0000:3a:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[mer gen 31 12:06:15 2018] ath: EEPROM regdomain: 0x6c
[mer gen 31 12:06:15 2018] ath: EEPROM indicates we should expect a direct regpair map
[mer gen 31 12:06:15 2018] ath: Country alpha2 being used: 00
[mer gen 31 12:06:15 2018] ath: Regpair used: 0x6c
[mer gen 31 12:06:15 2018] ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0
[mer gen 31 12:06:15 2018] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[mer gen 31 12:06:17 2018] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[mer gen 31 12:06:17 2018] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready
[mer gen 31 12:06:26 2018] wlp58s0: authenticate with 32:91:8f:c6:70:62
[mer gen 31 12:06:26 2018] wlp58s0: send auth to 32:91:8f:c6:70:62 (try 1/3)
[mer gen 31 12:06:26 2018] wlp58s0: send auth to 32:91:8f:c6:70:62 (try 2/3)
[mer gen 31 12:06:26 2018] wlp58s0: send auth to 32:91:8f:c6:70:62 (try 3/3)
[mer gen 31 12:06:26 2018] wlp58s0: authentication with 32:91:8f:c6:70:62 timed out
[mer gen 31 12:06:48 2018] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready

garakkio

2 Posts

June 22nd, 2018 06:00

It looks like issue was solved after upgrading to Ubuntu 18.04

At least, a couple of wi-fi networks that were not previously working are working now.

I keep my fingers crossed...

Intro

15 Posts

September 22nd, 2018 05:00

View More

View All

No Events found!

Top