Stefani Seibold <stefani@xxxxxxxxxxx> writes: > Am Donnerstag, den 12.11.2020, 02:10 +0100 schrieb wi nk: >> I've yet to see any instability after 45 minutes of exercising it, I >> do see a couple of messages that came out of the driver: >> >> [ 8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005 >> [ 11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a >> >> then when it associates: >> >> [ 16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3) >> [ 16.722636] wlp85s0: authenticated >> [ 16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3) >> [ 16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea >> (capab=0x411 status=0 aid=8) >> [ 16.738443] wlp85s0: associated >> [ 16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes >> ready >> >> The adapter is achieving around 500 mbps on my gigabit connection, my >> 2018 mbp sees around 650, so it's doing pretty well so far. >> >> Stefani - when you applied the patch that Kalle shared, which branch >> did you apply it to? I applied it to ath11k-qca6390-bringup and when >> I revert 7fef431be9c9 there is a small merge conflict I needed to >> resolve. I wonder if either the starting branch, or your chosen >> resolution are related to the instability you see (or I'm just lucky >> so far! :)). >> > > I used the vanilla kernel tree > https://git.kernel.org/torvalds/t/linux-5.10-rc2.tar.gz. On top of this > i applied the > > RFT-ath11k-pci-support-platforms-with-one-MSI-vector.patch > > and reverted the patch 7fef431be9c9 I did also my testing on v5.10-rc2 and I recommend to use that as the baseline when debuggin these ath11k problems. It helps to compare the results if everyone have the same baseline. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
