Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55096 - [linux-firmware] ath10k_pci firmware ver 10.2.4.70.63-2 issue

Attached to Project: Arch Linux
Opened by Gilbert (gmcms) - Thursday, 10 August 2017, 09:39 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 10 August 2017, 15:23 GMT
Task Type Bug Report
Category Upstream Bugs
Status Assigned
Assigned To Laurent Carlier (lordheavy)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Hi, ath10k_pci firmware ver 10.2.4.70.63-2 that has been added in the linux-firmware package is crashing with the following dmesg output:

-----------------------------------------------------------------------------------------------------------
[ 3.794990] ath10k_pci 0000:01:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 3.956604] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[ 3.956616] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 3.957508] ath10k_pci 0000:01:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
[ 3.999024] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 5.141993] ath10k_pci 0000:01:00.0: firmware crashed! (uuid 5e1bf845-c278-425c-8c6d-c335a7833655)
[ 5.151307] ath10k_pci 0000:01:00.0: qca988x hw2.0 target 0x4100016c chip_id 0x043222ff sub 0000:0000
[ 5.151315] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 5.152235] ath10k_pci 0000:01:00.0: firmware ver 10.2.4.70.63-2 api 5 features no-p2p,raw-mode,mfp,allows-mesh-bcast crc32 4ff9e14d
[ 5.152254] ath10k_pci 0000:01:00.0: board_file api 1 bmi_id N/A crc32 bebc7c08
[ 5.152265] ath10k_pci 0000:01:00.0: htt-ver 0.0 wmi-op 5 htt-op 2 cal otp max-sta 128 raw 0 hwcrypto 1
[ 5.154307] ath10k_pci 0000:01:00.0: firmware register dump:
[ 5.160007] ath10k_pci 0000:01:00.0: [00]: 0x4100016C 0x000015B3 0x009BFF84 0x00955B31
[ 5.167961] ath10k_pci 0000:01:00.0: [04]: 0x009BFF84 0x00060130 0x00000013 0x00000000
[ 5.175943] ath10k_pci 0000:01:00.0: [08]: 0x009C8EA4 0x00007170 0x00000001 0x00435300
[ 5.183891] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x00958360 0x0095836B
[ 5.191842] ath10k_pci 0000:01:00.0: [16]: 0x00958080 0x0094078E 0x00000000 0x00000000
[ 5.199789] ath10k_pci 0000:01:00.0: [20]: 0x409BFF84 0x0040AB44 0x004101E0 0x0000000C
[ 5.207760] ath10k_pci 0000:01:00.0: [24]: 0x809BFE1C 0x0040ABA4 0x00000006 0xC09BFF84
[ 5.215724] ath10k_pci 0000:01:00.0: [28]: 0x8098E907 0x0040ABD4 0x009C8E7C 0x0000016B
[ 5.223674] ath10k_pci 0000:01:00.0: [32]: 0x8098FD3B 0x0040ABF4 0x004209EC 0x00420B0C
[ 5.231614] ath10k_pci 0000:01:00.0: [36]: 0x8098A7DA 0x0040AC34 0x00420AA0 0x004062DC
[ 5.239564] ath10k_pci 0000:01:00.0: [40]: 0x80988785 0x0040AC94 0x00410760 0x00400000
[ 5.247505] ath10k_pci 0000:01:00.0: [44]: 0x8098AEC8 0x0040AD44 0x00410760 0x00000001
[ 5.255478] ath10k_pci 0000:01:00.0: [48]: 0x809B67C4 0x0040AD84 0x00410760 0x00411344
[ 5.263438] ath10k_pci 0000:01:00.0: [52]: 0x809B293C 0x0040ADA4 0x00400000 0x00416FA4
[ 5.271395] ath10k_pci 0000:01:00.0: [56]: 0x809C0C3D 0x0040ADE4 0x0040AE08 0x00412118
[ 5.279354] ath10k_pci 0000:01:00.0: Copy Engine register dump:
[ 5.285332] ath10k_pci 0000:01:00.0: [00]: 0x00057400 0 0 3 3
[ 5.291813] ath10k_pci 0000:01:00.0: [01]: 0x00057800 3 3 8 9
[ 5.298290] ath10k_pci 0000:01:00.0: [02]: 0x00057c00 1 1 0 1
[ 5.304762] ath10k_pci 0000:01:00.0: [03]: 0x00058000 1 1 2 1
[ 5.311238] ath10k_pci 0000:01:00.0: [04]: 0x00058400 0 0 40 0
[ 5.317712] ath10k_pci 0000:01:00.0: [05]: 0x00058800 0 0 0 0
[ 5.324183] ath10k_pci 0000:01:00.0: [06]: 0x00058c00 0 0 0 0
[ 5.330657] ath10k_pci 0000:01:00.0: [07]: 0x00059000 0 0 0 0
[ 10.309204] ath10k_pci 0000:01:00.0: wmi unified ready event not received
[ 10.395159] ath10k_pci 0000:01:00.0: could not init core (-110)
[ 10.401285] ath10k_pci 0000:01:00.0: could not probe fw (-110)
[ 10.422652] ath10k_pci 0000:01:00.0: cannot restart a device that hasn't been started
-----------------------------------------------------------------------------------------------------------

Downgrading the linux-firmware package until getting ath10k_pci firmware ver 10.2.4.70.54 is solving the issue and the wireless pcie board is working fine.

Thanks

This task depends upon

Comment by Francisco Pina (Stunts) - Sunday, 03 September 2017, 21:30 GMT
I'd just like to add that this is an upstream issue and is apparently already being tackled by the Qualcomm Atheros team:
http://lists.infradead.org/pipermail/ath10k/2017-August/010042.html
Comment by Laurent Carlier (lordheavy) - Monday, 21 May 2018, 06:49 GMT
Is it still an issue ?
Comment by Leonam S (simoes) - Friday, 23 November 2018, 09:09 GMT
Hi.
I'm still have a problem, someone can help?

"
____ uname -a
Linux archlinux 4.14.81-1-lts #1 SMP Tue Nov 13 21:23:49 CET 2018 x86_64 GNU/Linux


____ dmesg | grep ath10k
[ 2.844987] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 3.248043] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:05:00.0.bin failed with error -2
[ 3.248062] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/cal-pci-0000:05:00.0.bin failed with error -2
[ 3.251084] ath10k_pci 0000:05:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
[ 3.251086] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 3.251724] ath10k_pci 0000:05:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[ 6.320010] ath10k_pci 0000:05:00.0: unable to read from the device
[ 6.320013] ath10k_pci 0000:05:00.0: could not execute otp for board id check: -110
[ 6.320017] ath10k_pci 0000:05:00.0: failed to get board id from otp: -110
[ 6.320044] ath10k_pci 0000:05:00.0: could not probe fw (-110)



____ lspci -v
05:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)
Subsystem: Lenovo QCA9377 802.11ac Wireless Network Adapter
Flags: bus master, fast devsel, latency 0, IRQ 126
Memory at f1000000 (64-bit, non-prefetchable) [size=2M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/8 Maskable+ 64bit-
Capabilities: [70] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [148] Virtual Channel
Capabilities: [168] Device Serial Number 00-00-00-00-00-00-00-00
Capabilities: [178] Latency Tolerance Reporting
Capabilities: [180] L1 PM Substates
Kernel driver in use: ath10k_pci
Kernel modules: ath10k_pci

"
Comment by Francisco Pina (Stunts) - Friday, 23 November 2018, 10:18 GMT
This no longer occurs with my card:
02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter

However, I have noticed that your card "QCA9337" is quite recent (released in 2018, but I was unable to find out more). Maybe the `linux-firmware` package does not yet support it?
Comment by Leonam S (simoes) - Monday, 26 November 2018, 09:15 GMT
How can I check that? I'm a "linux-noob" :D
Because in the sites that i saw, says that should work:
1 - http://www.sparklan.com/p2-products-detail.php?PKey=1d2bsjqrHnqa85aaHl0mpJtOWcBpjf5kKBc0DfFEU90&WNFQ-158ACN(BT)
2 - https://wireless.wiki.kernel.org/en/users/Drivers/Atheros

And worked before, but some "linux firmware update" makes the wifi stopping to work.

I tried this (https://bbs.archlinux.org/viewtopic.php?id=233379) but, without success.

Comment by Francisco Pina (Stunts) - Monday, 26 November 2018, 11:11 GMT
If it has already worked in the past, what you should do is use the "Arch Linux archive" (https://wiki.archlinux.org/index.php/Arch_Linux_Archive) to figure out which "linux-firmware" version broke your support.
Once you have that figured out, an upstream bug-report is likely to be the best course of action. The most likely place to get attention is probably this mailing list (http://lists.infradead.org/pipermail/ath10k), which seems pretty active with developers from the ath10k driver.
But make sure you know which `linux-firmware` version breaks support.
Comment by Leonam S (simoes) - Monday, 26 November 2018, 12:24 GMT
WORKS!
Thanks!
(this video help me too (https://www.youtube.com/watch?v=LfgY3dEWr-U)

Have a nice week and thanks again!

Comment by Francisco Pina (Stunts) - Monday, 26 November 2018, 22:29 GMT
I'm really glad it helped.
But if you could expose the problem upstream and link us back to your bug report, that would be A+, since it will help everyone else in the future.
Thank you!
Comment by Leonam S (simoes) - Tuesday, 27 November 2018, 10:19 GMT
How can I do that?

I just know that:
____ dmesg | grep ath10k
[ 2.844987] ath10k_pci 0000:05:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0
[ 3.248043] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:05:00.0.bin failed with error -2
[ 3.248062] ath10k_pci 0000:05:00.0: Direct firmware load for ath10k/cal-pci-0000:05:00.0.bin failed with error -2
[ 3.251084] ath10k_pci 0000:05:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 17aa:0901
[ 3.251086] ath10k_pci 0000:05:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 3.251724] ath10k_pci 0000:05:00.0: firmware ver WLAN.TF.2.1-00021-QCARMSWP-1 api 6 features wowlan,ignore-otp crc32 42e41877
[ 6.320010] ath10k_pci 0000:05:00.0: unable to read from the device
[ 6.320013] ath10k_pci 0000:05:00.0: could not execute otp for board id check: -110
[ 6.320017] ath10k_pci 0000:05:00.0: failed to get board id from otp: -110
[ 6.320044] ath10k_pci 0000:05:00.0: could not probe fw (-110)
Comment by Francisco Pina (Stunts) - Monday, 03 December 2018, 11:53 GMT
I'd recommend posting to the Ath10K mailing list (http://lists.infradead.org/pipermail/ath10k), and expose the issue you were having (much like you did here).
Then, explain which version of `linux-firmware` makes the card work again. This will let them know between which versions the bug you suffer from was introduced. This means that you have to explain how to reproduce your issue, and how to work around it.
Make sure you follow up on the emails, as the devs may request further information. Don' forget to link back here so we can also follow up on the discussion.
Comment by Leonam S (simoes) - Monday, 03 December 2018, 14:01 GMT
Currently:
linux-firmware installed: 20180815.f1b95fe-1
linux-lts installed: 4.14.69-1
linux-lts-headers installed: 4.14.69-1

Ok "http://lists.infradead.org/pipermail/ath10k" .
Comment by Marcin Mielniczuk (marmistrz) - Tuesday, 28 May 2019, 17:13 GMT
This sometimes happens to me on the linux-lts kernel, currently 4.19.46-1-lts. A workaround is simply:

# modprobe -r ath10k_pci && modprobe ath10k_pci
Comment by Ben Fiedler (bfiedler) - Tuesday, 17 September 2019, 13:44 GMT
~~The current HEAD in the official repo (https://github.com/kvalo/ath10k-firmware) contains code that works for me on a Dell XPS 13 7th Gen (Kaby Lake):~~

~~https://github.com/kvalo/ath10k-firmware/commit/da1564dafe1c8175faf694482d1649f56229ae96~~

Scratch that, it still crashes...

Loading...