Firmware 636 crashed with 4addr

Yeoh Chun-Yeow yeohchunyeow at gmail.com
Wed Apr 16 21:45:37 PDT 2014


Hi, Michal

Hopefully this is sufficient. Please see the attached file.

I up the wlan, connect to AP, set 4addr on, then bridge the wlan0 to
bridge interface.

---
Chun-Yeow

On Wed, Apr 16, 2014 at 6:43 PM, Michal Kazior <michal.kazior at tieto.com> wrote:
> On 16 April 2014 12:40, Yeoh Chun-Yeow <yeohchunyeow at gmail.com> wrote:
>> Sure, any specific logs or traces that you want?
>
> I think hexdumps aren't necessary. debug_mask=0xffffff3f should suffice.
>
>
>> Will do it later.
>
> Okay :-)
>
>
> Michał
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ath10k-dbg.log
Type: text/x-log
Size: 124391 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/ath10k/attachments/20140417/d40fc411/attachment-0001.bin>


More information about the ath10k mailing list