Firmware 636 crashed with 4addr

Yeoh Chun-Yeow yeohchunyeow at gmail.com
Thu Apr 17 02:10:50 PDT 2014


Yes, this is from my ubuntu laptop, the previous one is from my
embedded board. Both are using the latest ath10k-next.

----
Chun-Yeow

On Thu, Apr 17, 2014 at 5:04 PM, Michal Kazior <michal.kazior at tieto.com> wrote:
> On 17 April 2014 10:34, Yeoh Chun-Yeow <yeohchunyeow at gmail.com> wrote:
>> I have captured more on the log. It's about 6M.
>
> Thanks! This gives me a better picture of what's going on.
>
> What caught my eye is your vif macaddr (60:02:b4:9d:99:91). It doesn't
> seem like an original for the hw (00:03:7f:xx:xx:xx). I wouldn't be
> surprised if that's the problem.
>
> The 4addr patch alone shouldn't be a problem since it only deals with
> rx frame processing and is beyond what fw is doing.
>
> I'll check sta vif on 636 later today and see if I can reproduce this.
>
>
> Michał



More information about the ath10k mailing list