Rate marked as a VHT rate but data is invalid: MCS: 10, NSS: 2

[Michal Kazior]

On 30 April 2015 at 20:26, mindfsck <mindfsck at gmail.com> wrote:
> Hello,
>
> I got my Broadcom card somehow working always for a handful seconds
> following this guide:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184/comments/115

I think you mean Qualcomm Atheros card.


>
> So first of all a big thank you! :)
>
> When I googled my problem (this emails' subject line) I found mostly ath9k
> from 2013...
> Maybe someone here can point me to a fix or workaround (if available)?
> I can change kernel code, apply patches, test things etc.
>
> Here is the kernel log:
> --
> [    5.319175] ath10k_pci 0000:03:00.0: pci irq msi-x interrupts 8 irq_mode
> 0 reset_mode 0
> [    5.505523] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/cal-pci-0000:03:00.0.bin failed with error -2
> [    5.505773] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/board-pci-168c:003e:11ad:0804.bin failed with error -2
> [    5.505775] ath10k_pci 0000:03:00.0: failed to load spec board file,
> falling back to generic: -2
> [    5.505946] ath10k_pci 0000:03:00.0: Direct firmware load for
> ath10k/QCA6174/hw2.1/firmware-5.bin failed with error -2
> [    5.505948] ath10k_pci 0000:03:00.0: could not fetch firmware file
> 'ath10k/QCA6174/hw2.1/firmware-5.bin': -2
>
> ...
>
> [   10.315505] ahci 0000:00:1f.2: port does not support device sleep
> [   14.314165] wlan1: authenticate with 00:1b:2f:61:b5:e8
> [   14.391351] wlan1: send auth to 00:1b:2f:61:b5:e8 (try 1/3)
> [   14.393075] wlan1: authenticated
> [   14.393232] ath10k_pci 0000:03:00.0 wlan1: disabling HT as WMM/QoS is not
> supported by the AP
> [   14.393235] ath10k_pci 0000:03:00.0 wlan1: disabling VHT as WMM/QoS is
> not supported by the AP
> [   14.394803] wlan1: associate with 00:1b:2f:61:b5:e8 (try 1/3)
> [   14.397284] wlan1: RX AssocResp from 00:1b:2f:61:b5:e8 (capab=0x431
> status=0 aid=3)
> [   14.420679] wlan1: associated
> [   14.420709] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready
> [   14.552494] ------------[ cut here ]------------
> [   14.552520] WARNING: CPU: 2 PID: 0 at net/mac80211/rx.c:3578
> ieee80211_rx+0x26c/0x940 [mac80211]()
> [   14.552522] Rate marked as a VHT rate but data is invalid: MCS: 10, NSS:
> 2

Either ath10k doesn't parse VHT-SIG properly or firmware reports
invalid VHT-SIG field. Can't say much without debug logs.


[...]
> [  210.696624] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
> 14ca9744-7171-4365-9612-3f5ede30cbec)
> [  210.696635] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff, 168c:003e:11ad:0804 fallback) fw killer-n1525-fw api 4 htt 3.0
> wmi 4 cal otp max_sta 32
> [  210.696637] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 dfs 0
> testmode 0
> [  210.698647] ath10k_pci 0000:03:00.0: firmware register dump:
> [  210.698648] ath10k_pci 0000:03:00.0: [00]: 0x05010000 0x00000000
> 0x0099BFAA 0x00000000
> [  210.698650] ath10k_pci 0000:03:00.0: [04]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698651] ath10k_pci 0000:03:00.0: [08]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698652] ath10k_pci 0000:03:00.0: [12]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698653] ath10k_pci 0000:03:00.0: [16]: 0x00000000 0x00000000
> 0x00000000 0x0099BFAA
> [  210.698655] ath10k_pci 0000:03:00.0: [20]: 0x00000000 0x004018F0
> 0x00000000 0x00000000
> [  210.698656] ath10k_pci 0000:03:00.0: [24]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698657] ath10k_pci 0000:03:00.0: [28]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698658] ath10k_pci 0000:03:00.0: [32]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698659] ath10k_pci 0000:03:00.0: [36]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698660] ath10k_pci 0000:03:00.0: [40]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698661] ath10k_pci 0000:03:00.0: [44]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698663] ath10k_pci 0000:03:00.0: [48]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698664] ath10k_pci 0000:03:00.0: [52]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.698665] ath10k_pci 0000:03:00.0: [56]: 0x00000000 0x00000000
> 0x00000000 0x00000000
> [  210.742185] ath10k_pci 0000:03:00.0: device has crashed during init
> [  210.766216] ath10k_pci 0000:03:00.0: device has crashed during init
> [  210.766218] ath10k_pci 0000:03:00.0: failed to wait for target init: -70
> [  210.766650] ieee80211 phy0: Hardware restart was requested
> [  210.766663] ath10k_pci 0000:03:00.0: failed to synchronize monitor vdev 1
> stop: -108
> [  210.766664] ath10k_pci 0000:03:00.0: failed to stop monitor vdev: -108
> [  210.806322] ath10k_pci 0000:03:00.0: device has crashed during init
> [  210.830324] ath10k_pci 0000:03:00.0: device has crashed during init
> [  210.830327] ath10k_pci 0000:03:00.0: failed to wait for target init: -70
> [  212.227905] ath10k_pci 0000:03:00.0: device successfully recovered
> [  216.232179] ath10k_pci 0000:03:00.0: firmware crashed! (uuid
> 9c23d4de-4420-4632-8665-62e3a7076276)
> [  216.232190] ath10k_pci 0000:03:00.0: qca6174 hw2.1 (0x05010000,
> 0x003405ff, 168c:003e:11ad:0804 fallback) fw killer-n1525-fw api 4 htt 3.0
> wmi 4 cal otp max_sta 32
> [  216.232192] ath10k_pci 0000:03:00.0: debug 0 debugfs 1 tracing 1 dfs 0
> testmode 0
> [  216.234197] ath10k_pci 0000:03:00.0: firmware register dump:

Either device reset didn't reset it entirely or there's a recurring
condition in driver which leads to the crash. Without debug logs I
can't help much. You'll need to compile ath10k with debug enabled and
gather traces with `trace-cmd` [1].


[1]: https://wireless.wiki.kernel.org/en/users/drivers/ath10k/debug#tracing


Michał