ath10k: firmware crash in station mode

[Michal Kazior]

On 15 May 2014 09:07, Vu Hai NGUYEN <vh.nguyen at actiasodielec.fr> wrote:
> I tried to set up station mode using ath10k and wpa_supplicant.
> If I used the firmware in branch 10.1 version firmware-2.bin_10.1.467.2-1 (which said that support STA mode but not well tested) , it crashed after associating with the access point:
>
> wlan0: SME: Trying to authenticate with 00:15:61:10:51:de (SSID='actia' freq=2457 MHz)
> wlan0: authenticate with 00:15:61:10:51:de
> wlan0: send auth to 00:15:61:10:51:de (try 1/3)
> wlan0: authenticated
> wlan0: Trying to associate with 00:15:61:10:51:de (SSID='actia' freq=2457 MHz)
> wlan0: associate with 00:15:61:10:51:de (try 1/3)
> wlan0: RX AssocResp from 00:15:61:10:51:de (capab=0x421 status=0 aid=1)
> wlan0: associated
> ath10k: firmware crashed!
> ath10k: hardware name qca988x hw2.0 version 0x4100016c
> ath10k: firmware version: 10.1.467.2-1
> ath10k: target register Dump Location: 0x00401930
> ath10k: target Register Dump
> ath10k: [00]: 0x4100016C 0x00000000 0x009A123A 0x00000000
> ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x009A123A
> ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
> ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
> ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
[...]

This is NULL dereference in firmware. I suspect it's an incomplete
driver-firmware setup (i.e. some commands weren't issued or were
invalid).

Can you enable debug logs ( echo 0xffffff3f | sudo tee
/sys/module/ath10k_core/parameters/debug_mask ) before you try to
associate and post logs, please? I'd like to see command sequence sent
to firmware before the crash happens.


> Than I tried another version of firmware from branch 999. (which said that support STA mode) but it worse, the firmware crashed before seeing the access point. (can not associate)

Can you post the crash logs (as noted above) when you try the 999
branch too, please? It seems 999 crashes sooner than 10.1. It might be
helpful to see the different crash points.


> This crashed is because of my system or just only the firmware issue? And is the firmware still continue developping? (There is a debug message of my system in the attached file if any one are interested in)

I have no idea what version of kernel you're using. Perhaps you broke
your source tree when merging/rebasing/cherry-picking/backporting?
What's your git head commit?

I can associate ath10k with both firmware branches without a problem.


> Btw is there anyone could set a channel (from 52 and more) that employs DFS sucessfully confirm it for me cause I can not do it until now :D
> Thank you all of you for the support,

Yes, this works (or at least it should). It might be tricky to get it
right for someone who's not familiar with regulatory shenanigans in
some cases.

Recently there was a bug introduced that broke DFS (see linux-wireless
mailing list; it's in the process of being fixed), but since you
haven't provided any information what your kernel tree is I can't tell
if that's the actual problem or not.


Michał