I just try to use QCA9880 mini pcie card with ath10k drivers in git source tree.

[Michal Kazior]

On 16 July 2013 09:33, Hwan Jin Ko <ymir.kr at gmail.com> wrote:
> Hello!
>
> I just try to use QCA9880 mini pcie card with ath10k drivers in git source tree.
> When I type iwlist command with scanning option, kernel shows firmware
> crashed message and not worked.
>
> Firmware is from https://github.com/kvalo/ath10k-firmware
>
> <snip>
> ~ # iwlist wlan2 scanning
> [ 100.100067] ath10k: firmware crashed!
> [ 100.103960] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> [ 100.110674] ath10k: firmware version: 1.0.0.636
> [ 100.116692] ath10k: target register Dump Location: 0x00401930
> [ 100.123928] ath10k: target Register Dump
> [ 100.128285] ath10k: [00]: 0x4100016C 0x00000000 0x009B58F2 0x00000000
> [ 100.135309] ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.142288] ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.149256] ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.156048] ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x009B58F2
> [ 100.163018] ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
> [ 100.170048] ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.176969] ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.183957] ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.190950] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.197859] ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.204834] ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.211759] ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.218798] ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
> [ 100.225757] ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000

Hi Hwan,

First of all - are you using a vanilla kernel or do you have some
custom patches applied?

This dump looks familiar to me (considering the circumstances) as if
the scan channel list hasn't been sent to the firmware. This can
happen if there's ath regulatory domain hack from OpenWRT applied.

If that is not the case then I'ld like to ask you to gather some more logs.

You can either gather printk logs, by making sure you load the
ath10k_core with `modprobe ath10k_core debug_mask=0xFFFFFFFF`, or you
can gather traces with `trace-cmd record -e ath10k` (traces need to be
enabled in the kernel and ath10k).


Pozdrawiam / Best regards,
Michał Kazior.