ath10k: firmware crash in station mode

[Vu Hai NGUYEN]

>The 636 crashes because the interface is in promiscuous mode (it's
>either put in a bridge or you have tcpdump running on it?). This won't
>work with 636. See mailing list archives. 636 has broken monitor mode
>and it crashes often.

>Can you please retry with debug_mask=0xffffffff to get full dumps and
>see what kind of frame is being sent? I guess it's an ipv6 neighbour
>solicitation but the request itself might be malformed for some reason
>causing firmware to crash unexpectedly.

>Also, can you try the test without making wlan interface promiscuous
>(on both firmwares, with debug_mask=0xffffffff) too, please?

Yes I used promiscuous to set up my station in bridge mode, the firmware crashed 
but If don't use promiscuous (put my station in router mode), the firmware didn't crash and
I can associate with the access point without problem. 
You can found in the attached file 4 dmesg file (with/without promicuous) for both version of firmware.
(If I set debug mask=0xffffffff there are many lines "htt rx pop" and I can not see all the dmesg, so I 
only set the mask=0xffffff3f).
But I wonder if there will be any progress of the firmware in the future for promiscuous so that I can 
set up bridge mode?  

>Ideally you should generate backports tree yourself from a given
>kernel tree (e.g. kvalo's ath master branch). See
>https://backports.wiki.kernel.org/index.php/Documentation/backports/hacking
>for more details on this.

Thanks, I'll try it.

>I'm not sure if your backports have the offending patch that breaks
>DFS or not. If so you might need to cherry-pick it to your backports
>tree manually or regenerate backports.

>If you use backports 3.15-rc1-1 (as found on
>http://drvbp1.linux-foundation.org/~mcgrof/rel-html/backports/) then
>there's no DFS bug there unless you tried to replace net/mac80211 and
>net/wireless (as you've done with drivers/net/wireless/ath/ ...).

I didn't touch mac80211 and wireless, only the folder ath

>If you generate backports with kvalo/ath master branch then DFS won't
>work as it is now (due to the bug I've mentioned earlier). Kalle
>doesn't have the patch that deals with it, yet. You'll need to
>cherry-pick the following 2 patches before generating backports from kvalo/ath:

 > https://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211-next.git/commit/?id=67ae07a109f3d518085e3b81aa48740e8c5cc3f7
 >https://git.kernel.org/cgit/linux/kernel/git/jberg/mac80211-next.git/commit/?id=00ec75fc5a6499d8fdeb6ec9f8f5df68b9291c74

 I did not get your suggest here, How can I "cherry-pick" thoses 2 patch before generating backports? I think that I sould generate the backport first and then apply these 2 patchs later?

NGUYEN Vu Hai
Acita-Sodielec
Route de Mayres - B.P. 9
12100 St GEORGES DE LUZENCON
FRANCE







Michał
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 10-1_no_promiscuous.txt
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140519/cccc1e73/attachment-0004.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 10-1_promiscuous.txt
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140519/cccc1e73/attachment-0005.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 999_no_promiscuous.txt
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140519/cccc1e73/attachment-0006.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 999_promiscuous.txt
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140519/cccc1e73/attachment-0007.txt>