ath10: problems on monitor mode ..

[Michal Kazior]

On 16 July 2013 09:54, Hwan Jin Ko <ymir.kr at gmail.com> wrote:
> Hello!

Hi,


> Also, I have problems on monitor mode and changing channels.
>
> <snip>
> ~ # iw wlan2 interface add mon2 type monitor
> ~ # iwconfig
> wlan0     IEEE 802.11abgn  ESSID:off/any
>           Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
> wlan2     IEEE 802.11abgn  ESSID:off/any
>           Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
> lo        no wireless extensions.
> mon2      IEEE 802.11abgn  Mode:Monitor  Tx-Power=20 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Power Management:off
> eth0      no wireless extensions.
> wlan1     IEEE 802.11abgn  ESSID:off/any
>           Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
> ~ # iw mon2 set channel 153
> command failed: Device or resource busy (-16)

You can't change a channel if there's a station interface running too
for quite some time now. That's not ath10k limitation.


> ~ # aireplay-ng -0 1 -a 00:11:22:33:44:55 -c 55:66:77:88:99:00 -D mon2
> [  723.393865] device mon2 entered promiscuous mode
> [  723.586609] BUG: unable to handle kernel NULL pointer dereference at   (null)
> [  723.594206] IP: [<c1226331>] ath10k_tx+0x101/0x2cd

Oh, good catch. Thanks!

I'll prepare a patch.


> Here is another test result ..
> aireplay-ng is worked but firmware crashed! message is displayed.
>
> <snip>
> ~ # ifconfig wlan2 down
> ~ # iwconfig wlan2 mode monitor
> ~ # ifconfig wlan2 up
> [  180.003417] ath10k: Monitor mode already enabled
> ~ # iw wlan2 set channel 153
> ~ # iwconfig
> wlan0     IEEE 802.11abgn  ESSID:off/any
>           Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
> wlan2     IEEE 802.11abgn  Mode:Monitor  Frequency:5.765 GHz  Tx-Power=30 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Power Management:off
> lo        no wireless extensions.
> eth0      no wireless extensions.
> wlan1     IEEE 802.11abgn  ESSID:off/any
>           Mode:Managed  Access Point: Not-Associated   Tx-Power=16 dBm
>           Retry  long limit:7   RTS thr:off   Fragment thr:off
>           Encryption key:off
>           Power Management:off
> ~ # aireplay-ng -0 1 -a 00:11:22:33:44:55 -c 55:66:77:88:99:00 -D wlan2
> [  207.106034] device wlan2 entered promiscuous mode
> [  207.301895] ath10k: firmware crashed!
> [  207.305810] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> [  207.312382] ath10k: firmware version: 1.0.0.636
> [  207.318219] ath10k: target register Dump Location: 0x00401930
> [  207.325317] ath10k: target Register Dump
> [  207.329456] ath10k: [00]: 0x4100016C 0x00000000 0x0098B7DA 0x00000000
> [  207.336291] ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.343132] ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.350018] ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.356808] ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x0098B7DA
> [  207.363580] ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
> [  207.370398] ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.377143] ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.383943] ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.390759] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.397497] ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.404364] ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.411345] ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.418198] ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
> [  207.425040] ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
> 16:15:18  Sending 64 directed DeAuth. STMAC: [55:66:77:88:99:00] [ 0| 0 ACKs]
> ~ #
> </snip>

Unfortunately this seems to be a firmware issue.


Pozdrawiam / Best regards,
Michał Kazior.