Firmware 636 crashed with 4addr

[Michal Kazior]

On 16 April 2014 12:01, Yeoh Chun-Yeow <yeohchunyeow at gmail.com> wrote:
> Hi, all
>
> Anyone knows the reason of the following firmware crashed whenever the
> managed interface is set with 4addr on and bridged to a bridge
> interface.
>
> ifconfig br-lan up
> iw wlan0 set 4addr on
> brctl addif br-lan wlan0
> [   78.130000] device wlan0 entered promiscuous mode
> [   78.130000] br-lan: port 1(wlan0) entered forwarding state
> [   78.140000] br-lan: port 1(wlan0) entered forwarding state
> [   79.140000] ath10k: firmware crashed!
> [   79.150000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
> [   79.150000] ath10k: firmware version: 999.999.0.636
> [   79.160000] ath10k: target register Dump Location: 0x0040AC14
> [   79.170000] ath10k: target Register Dump
> [   79.170000] ath10k: [00]: 0x4100016C 0x00000000 0x009C4521 0x00000000
> [   79.180000] ath10k: [04]: 0x009C4521 0x00060530 0x00000019 0x00955A00
> [   79.180000] ath10k: [08]: 0x00014855 0x00000000 0x0040CC94 0x00000020
> [   79.190000] ath10k: [12]: 0x00000000 0x00000000 0x00958360 0x0095836B
> [   79.200000] ath10k: [16]: 0x80991091 0x0040AD94 0x0042EADC 0x00000000
> [   79.200000] ath10k: [20]: 0x0000FFFF 0x00000000 0x00000045 0x004340C0
> [   79.210000] ath10k: [24]: 0x809A0978 0x0040AD94 0x00439304 0x052157C7
> [   79.220000] ath10k: [28]: 0x809AD1A2 0x0040ADE4 0x00439304 0x0043F8BC
> [   79.220000] ath10k: [32]: 0x00000001 0x00000018 0x00000000 0x0042F664
> [   79.230000] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
> [   79.230000] ath10k: [40]: 0x00000000 0x00000000 0x00000045 0x00412700
> [   79.240000] ath10k: [44]: 0x00439C00 0x00000000 0x00000000 0x00400000
> [   79.250000] ath10k: [48]: 0x809AE0B4 0x0040AE04 0x00400000 0x0043F8BC
> [   79.250000] ath10k: [52]: 0x00000001 0x00000000 0x004231F0 0x00400000
> [   79.260000] ath10k: [56]: 0x809AE17E 0x0040AE44 0x0040FE6C 0x0040D310
> [   82.270000] ath10k: failed to to request monitor vdev 1 stop: -11
> [   87.270000] ath10k: failed to synchronise monitor vdev 1: -145
> [   87.270000] ath10k: failed to stop monitor vdev: -145
> [   90.280000] ath10k: failed to request wmi monitor vdev 1 removal: -11
> [   90.280000] ath10k: failed to delete monitor vdev: -11
>
> Further investigation shows that this is not happening to firmware
> 10.1.467.2-1.

I'm suspecting this is because of monitor vdev.

Firmware 999.999.0.636 is incapable of running monitor vdev alone,
i.e. it has to be paired with another non-monitor vdev.

Please try to first connect the interface *before* adding it to the
bridge. I'm guessing this should work. Be aware, that if you then
disconnect from AP without first removing the interface from the
bridge you'll most likely crash the firmware too.


Michał