TR : ath10k: firmware crash in station mode

[Yeoh Chun-Yeow]

Based on my testing, due to firmware 636 is not able to support
standalone monitor mode, and bridge requires promiscuous mode, it
would crash. Then, I have tested with AP firmware and it works well.
But then, I have not up the node for long time.

By the way, I am associating the AP before setting "iw dev wlan0 set
4addr on" and bridge it.

----
Chun-Yeow

On Fri, May 23, 2014 at 10:55 PM, Vu Hai NGUYEN
<vh.nguyen at actiasodielec.fr> wrote:
>>Yes, you can do it with firmware 10.1.467.2-1 but not firmware 999.999.0.636.
>
> They all crashed, but the 999 crashed sooner (even before associated with the AP) , I've posted it the logs before for Michal Kazior. Here is my old email:
> http://lists.infradead.org/pipermail/ath10k/2014-May/002042.html
>
>>>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.
>
>>I enable directly the debug_mask when I load the module "modprobe ath10k_core.ko debug_mask=0x0xffffff3f" (I thought it is the same thing like what you do, right?).
>>You can found de debug mess in the attached file (debug_10-1.txt). (line 3007: wlan0: associated and then in line 3008: ath10k: firmware crashed!)
>
>>>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.
>
>>Yes it crashed sooner. There are no wlan0: associated in the debug message. (attached file: debug_999.txt).
>
>
> NGUYEN Vu Hai
> Acita-Sodielec
> Route de Mayres - B.P. 9
> 12100 St GEORGES DE LUZENCON
> FRANCE
>