Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-23 Thread Rafał Miłecki
On 22 September 2016 at 16:09, Rafał Miłecki wrote: > On 22 September 2016 at 14:24, Rafał Miłecki wrote: >> I got the same problem again, but this time there was only 1 skb in my >> flowring. >> That resulted in less serial console messages and no reboot. >>

Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-22 Thread Rafał Miłecki
On 22 September 2016 at 14:24, Rafał Miłecki wrote: > On 09/22/2016 01:59 PM, Rafał Miłecki wrote: >> >> And again... >> >> I decided to focus on brcmf_flowring_delete a bit more. >> >> As I can see flowrings are created and removed from time to time, in most >> cases >> they

Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-22 Thread Rafał Miłecki
On 09/22/2016 01:59 PM, Rafał Miłecki wrote: And again... I decided to focus on brcmf_flowring_delete a bit more. As I can see flowrings are created and removed from time to time, in most cases they are empty when being deleted. When they are not, things go wrong. In below log you can see

Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-22 Thread Rafał Miłecki
And again... I decided to focus on brcmf_flowring_delete a bit more. As I can see flowrings are created and removed from time to time, in most cases they are empty when being deleted. When they are not, things go wrong. In below log you can see brcmfmac removing flowring that got 8 skb packets.

Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-20 Thread Rafał Miłecki
Hi Hante, I hit this problem again and I'm afraid it's getting even more complex. Last time you were suspecting flowring deletion but it didn't make much sense to me. It was because I didn't see brcmf_flowring_delete anywhere in my log. Well, today it was different. I saw brcmf_flowring_delete

Re: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-15 Thread Rafał Miłecki
On 15 September 2016 at 11:20, Hante Meuleman wrote: > Thank you for the extensive debugging. We are looking into this. Arend wrote > yesterday to ask for detailed timing on wen eapol is inserted. We want this > so we can increase the timeout. This is not a "nice"

RE: brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-15 Thread Hante Meuleman
rds, Hante -Original Message- From: Rafał Miłecki [mailto:zaj...@gmail.com] Sent: Thursday, September 15, 2016 10:12 AM To: Hante Meuleman; Arend van Spriel; brcm80211-dev-l...@broadcom.com Cc: linux-wireless@vger.kernel.org; Rafał Miłecki Subject: brcmf_txfinalize misses 802.1x packet leading to infinit

brcmf_txfinalize misses 802.1x packet leading to infinite WARNINGs

2016-09-15 Thread Rafał Miłecki
Hi, Yesterday I explained on OpenWrt forum [0] that there are 2 problems leading to WARNINGs triggered by brcmf_netdev_wait_pend8021x. The first one is firmware problem with A-MPDU implementation. I already reported this in "AMPDU stalls with brcmfmac4366b-pcie.bin triggering WARNINGs" e-mail