Connection Problems with on QCA9880-BR4A

[Michal Kazior]

On 15 November 2016 at 23:42, Felix <kramerfe at gmail.com> wrote:
> Hi,
>
> Connected is usually a few minutes away from dsiconnected. I am running
> tcpdump without pcap filters. Here are my iptables and udev rules. If I use
> the SR71 everything works fine therefore I doubt it has anything to do with
> these.
[...]
> The option debug_mask=0xffffff3f does not give me any addidtional entries in
> dmesg or journalctl. I also tried "modprobe ath10k_core
> debug_mask=0xffffffff" with the same result and shows the debug_mask value
> seems properly set:
>>> cat /sys/module/ath10k_core/parameters/debug_mask
> 4294967295
>>> python -c 'print "%i" % 0xffffffff'
> 4294967295
[...]
>>> journalctl
[...]
> Nov 15 21:27:17 android3427 kernel: ath10k_pci 0000:02:00.0: qca988x hw2.0
> target 0x4100016c chip_id 0x043202ff sub 19b6:d03c
> Nov 15 21:27:17 android3427 kernel: ath10k_pci 0000:02:00.0: kconfig debug 0
> debugfs 0 tracing 0 dfs 0 testmode 0
[...]

Your driver is compiled without debug prints which explains why you're
not seeing any difference after setting debug_mask. You'll need to
recompile for that.


[...]
> Nov 15 21:27:52 android29646 kernel: wlan0: authenticate with XXX0
> Nov 15 21:27:52 android29646 kernel: wlan0: send auth to XXX0 (try 1/3)
> Nov 15 21:27:52 android29646 kernel: wlan0: authenticated
> Nov 15 21:27:52 android29646 kernel: ath10k_pci 0000:02:00.0 wlan0:
> disabling HT as WMM/QoS is not supported by the AP
> Nov 15 21:27:52 android29646 kernel: ath10k_pci 0000:02:00.0 wlan0:
> disabling VHT as WMM/QoS is not supported by the AP

Your AP doesn't even HT nor VHT nor WMM enabled. Is this expected?


> Nov 15 21:27:52 android29646 kernel: wlan0: associate with XXX0 (try 1/3)
> Nov 15 21:27:52 android29646 kernel: wlan0: RX AssocResp from XXX0
> (capab=0x11 status=0 aid=1)
> Nov 15 21:27:52 android29646 kernel: wlan0: associated
> Nov 15 21:27:52 android29646 kernel: wlan0: Limiting TX power to 17 dBm as
> advertised by XXX0
[...]
> Nov 15 21:30:12 android29646 kernel: wlan0: deauthenticated from XXX0
> (Reason: 2=PREV_AUTH_NOT_VALID)

It seems AP is kicking you out. EAP likely didn't complete up all the
way and a timeout on AP is triggered.

I suspect lack of QoS is source of cofusion here. Either driver is
requesting firmware to use wrong tid or firmware tries to be clever
and ends up using wrong hardware queue where the final EAPOL gets
stuck and is never transmitted. That's just a guess though.

Driver dumps (debug_mask=0xffffffff actually) would be really useful here.


Michał