Start a Conversation

Unsolved

This post is more than 5 years old

R

12959

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

24 Posts

January 17th, 2017 09:00

Is anyone reading this? Just now another occurrance:

C. No connection to router. Output of dmesg:

[  300.430076] mce: [Hardware Error]: Machine check events logged
 333.567425] wlp58s0: AP 88:03:55:f4:9c:e8 changed bandwidth, new config is 2462 MHz, width 1 (2462/0 MHz)
[  589.594545] nfs: server 192.168.1.100 not responding, timed out
[  788.526044] nfs: server 192.168.1.100 not responding, timed out
[  991.556287] nfs: server 192.168.1.100 not responding, timed out
[ 1190.482152] nfs: server 192.168.1.100 not responding, timed out
[ 1401.718170] nfs: server 192.168.1.100 not responding, timed out

(192.1680.1.100 is network-attached-storage)

 

Many thanks

January 18th, 2017 17:00

Same problem here: WIFI is VERY instable.

Ubuntu 16.04 - Gnome 3.18 - Kernel Linux version 4.4.0-59-generic -  XPS 13 9360 - BIOS version: 1.2.3

24 Posts

January 19th, 2017 13:00

D. Another crash:

[17239.485180] 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
[17239.487198] ath10k_pci 0000:3a:00.0: firmware register dump:
[17239.487208] ath10k_pci 0000:3a:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[17239.487214] ath10k_pci 0000:3a:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[17239.487219] ath10k_pci 0000:3a:00.0: [08]: 0x00498110 0x00955A00 0x0000000B 0x00400000
[17239.487223] ath10k_pci 0000:3a:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[17239.487228] ath10k_pci 0000:3a:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[17239.487233] ath10k_pci 0000:3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[17239.487237] ath10k_pci 0000:3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[17239.487242] ath10k_pci 0000:3a:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313B8
[17239.487247] ath10k_pci 0000:3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 0x00429548
[17239.487251] ath10k_pci 0000:3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000002
[17239.487256] ath10k_pci 0000:3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[17239.487260] ath10k_pci 0000:3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[17239.487265] ath10k_pci 0000:3a:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[17239.487270] ath10k_pci 0000:3a:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[17239.487274] ath10k_pci 0000:3a:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[17239.585795] ieee80211 phy0: Hardware restart was requested
 

24 Posts

January 19th, 2017 14:00

E. And another one:

[20634.804968] ath10k_pci 0000:3a:00.0: firmware crashed! (uuid a373e5e5-e4a9-4391-b091-f6c7b58f9f73)
[20634.804985] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 target 0x05030000 chip_id 0x00340aff sub 1a56:1535
[20634.804989] ath10k_pci 0000:3a:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
[20634.805896] 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
[20634.806401] ath10k_pci 0000:3a:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7
[20634.806415] 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
[20634.808476] ath10k_pci 0000:3a:00.0: firmware register dump:
[20634.808486] ath10k_pci 0000:3a:00.0: [00]: 0x05030000 0x000015B3 0x009860FA 0x00955B31
[20634.808492] ath10k_pci 0000:3a:00.0: [04]: 0x009860FA 0x00060730 0x00000004 0x0040E8A0
[20634.808497] ath10k_pci 0000:3a:00.0: [08]: 0x00498110 0x00955A00 0x0000000B 0x00400000
[20634.808502] ath10k_pci 0000:3a:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
[20634.808507] ath10k_pci 0000:3a:00.0: [16]: 0x00952CC4 0x00910712 0x00000000 0x0091080D
[20634.808513] ath10k_pci 0000:3a:00.0: [20]: 0x409860FA 0x0040E7E8 0x00000000 0x0041E0DC
[20634.808518] ath10k_pci 0000:3a:00.0: [24]: 0x800B5A1D 0x0040E848 0x000FFFFF 0xC09860FA
[20634.808523] ath10k_pci 0000:3a:00.0: [28]: 0x809B3230 0x0040E948 0x00000018 0x004313B8
[20634.808528] ath10k_pci 0000:3a:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9C0 0x00429548
[20634.808533] ath10k_pci 0000:3a:00.0: [36]: 0x8091D252 0x0040E9B8 0x00000000 0x00000002
[20634.808538] ath10k_pci 0000:3a:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10
[20634.808543] ath10k_pci 0000:3a:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x00000001
[20634.808548] ath10k_pci 0000:3a:00.0: [48]: 0x80911210 0x0040EAD8 0x00000010 0x004041D0
[20634.808553] ath10k_pci 0000:3a:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
[20634.808558] ath10k_pci 0000:3a:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
[20634.911972] ieee80211 phy0: Hardware restart was requested

I think you're getting the point. All that's missing now, is a fix ;)

24 Posts

January 29th, 2017 11:00

Anything I can do to get someone at Dell to notice this issue? Are these messages being read?

24 Posts

January 30th, 2017 14:00

After an email to Dell I was pointed to askubuntu.com/.../getting-killer-wireless-ac-1535-working-for-installing-ubuntu-16-04 which seems to have solved the problems for now

16 Posts

January 31st, 2017 01:00

Hi,

I had similar issues with wireless when connecting to one certain wifi network. The wireless adapter stopped working and nm-applet crashed. I don't know if this is related, my dmesg dump looks different.

[   12.314003] cfg80211: World regulatory domain updated:

[   12.314006] cfg80211:  DFS Master region: unset

[   12.314007] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

[   12.314008] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

[   12.314009] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)

[   12.314010] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)

[   12.314011] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)

[   12.314012] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)

[   12.314013] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)

[   12.314013] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)

[   12.314014] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)

[   12.325126] ath10k_pci 0000:3a:00.0: enabling device (0000 -> 0002)

[   12.327316] ath10k_pci 0000:3a:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0

[   12.473787] Non-volatile memory driver v1.3

[   12.568699] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/cal-pci-0000:3a:00.0.bin failed with error -2

[   12.568944] ath10k_pci 0000:3a:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2

[   12.568946] ath10k_pci 0000:3a:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2

[   14.754387] ath10k_pci 0000:3a:00.0: qca6174 hw3.2 (0x05030000, 0x00340aff sub 1a56:1535) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 fwapi 4 bdapi 2 htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 features wowlan,ignore-otp,no-4addr-pad

[   14.754390] ath10k_pci 0000:3a:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0

[   14.823909] ath: EEPROM regdomain: 0x6c

[   14.823912] ath: EEPROM indicates we should expect a direct regpair map

[   14.823914] ath: Country alpha2 being used: 00

[   14.823914] ath: Regpair used: 0x6c

[   14.828194] ath10k_pci 0000:3a:00.0 wlp58s0: renamed from wlan0

[   14.864954] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready

[   17.123532] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready

[   17.188622] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready

24 Posts

February 1st, 2017 13:00

Hmm too optimistic too soon. It's not working, the problem still exists

4 Operator

 • 

783 Posts

March 10th, 2017 11:00

@Community,

Thank you for your feedback and discussion regarding the Killer N1535 card.

Please note that I’m not a wireless expert but I asked around and a colleague gave me this firmware:

github.com/.../4.4

Our experience so far with this firmware has been positive. We’re asking the community to try out the firmware and post back with any feedback. For any issues remaining after the firmware update I may want to start individual cases with community members in order to obtain product captures for Dell engineering.

Below is the recommend method to install this firmware:

-once firmware is downloaded replace every item inside of folder /lib/firmware/ath10k/QCA6174 with everything inside of github.com/.../QCA6174

-Reboot the system and test WIFI

We’re looking forward to your feedback.

10 Posts

March 15th, 2017 04:00

I don't think these instructions work, in dmesg it whinges it can't find the firmware files and doesn't work :-(

4 Operator

 • 

783 Posts

March 28th, 2017 11:00

Thanks for the feedback Beurle. I will take apart the instructions and find out what's going on with them.

If you still need assistance with WIFI send me a friend request and include your service tag.

4 Operator

 • 

783 Posts

April 26th, 2017 16:00

@Community,

I received some updated instructions. Please share any feedback you have. For any issues remaining after the firmware update I may want to start individual cases with community members in order to obtain product captures for Dell engineering.

Killer N1535 Manual Firmware Update Process:

1. In a terminal, confirm the QCA6174 with this command: sudo lspci | grep –i qca6174

2. Download the latest firmware and extract the contents: codeload.github.com/.../master

3. Or you can download the ZIP and save it with the browser at this url as shown: https://github.com/kvalo/ath10k-firmware

4. Open the “Downloads” folder, then “right click” the “ath10k-firmware-master.zip” and “extract here”

5. Confirm the contents of the extracted folder as shown. You should see the “QCA6174” folder.

6. Back in a terminal, type “sudo nautilus” to open a root privilege file manager

   a. Sudo nautilus

   b. Click on “computer”

   c. Click on folder “lib”

7. Navigate to the QCA6174 firmware directory

   a. Click on “firmware

   b. Click to open “ath10k

   c. Right click & “Delete” the “QCA6174” directory (we are removing everything)

8. Navigate to your other file manager window where your extracted download folder is:

   a. Confirm your new source file location in Downloads/auth10k-firmware

   b. Confirm your new destination file location in ../firmware/ath10k

   c. Copy & paste the QCA6174 directory with all of its contents into the destination

        directory as shown. The path should be: /lib/firmware/ath10k/

9. Open /lib/firmware/ath10k/QCA6174/HW3.0 and rename file: firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1 To: firmware-4.bin


10. Now reboot and test your new Killer Wi-Fi firmware

10 Posts

May 2nd, 2017 04:00

These instructions worked for me but there is a typo, not sure whether the firmware fixes the wireless yet

sudo lspci | grep –I qca6174

Should be

sudo lspci | grep –i qca6174

4 Operator

 • 

783 Posts

May 2nd, 2017 10:00

@Beurle,

Thank you for your note. I've fixed the typo.

I'm looking forward to your feedback regarding your wireless card's behavior/performance.

34 Posts

May 6th, 2017 08:00

Justin,

I've been using the Dell 16.04 install, but yesterday installed UbuntuGnome 17.04 and ran into the same issues with wifi. Very slow, lots of intermittent outages, pages loading without css, etc.

I followed the steps you outlined above. They are very clear and well written. Rebooted and the difference is night and day. Only been using the new driver for a short while, but so far very happy with it. Thanks.

No Events found!

Top