On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@xxxxxxxxxxx> wrote: > > 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! :)). > > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@xxxxxxxxxxx> wrote: > > > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@xxxxxxxxxxx> wrote: > > > > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote: > > > > > > > > The proof of concept patch for v5.10-rc2 is here: > > > > > > > > https://patchwork.kernel.org/project/linux-wireless/patch/1605121102-14352-1-git-send-email-kvalo@xxxxxxxxxxxxxx/ > > > > > > > > Hopefully it makes it possible to boot the firmware now. But this is > > > > a > > > > quick hack and most likely buggy, so keep your expectations low :) > > > > > > > > In case there are these warnings during firmware initialisation: > > > > > > > > ath11k_pci 0000:05:00.0: qmi failed memory request, err = -110 > > > > ath11k_pci 0000:05:00.0: qmi failed to respond fw mem req:-110 > > > > > > > > Try reverting this commit: > > > > > > > > 7fef431be9c9 mm/page_alloc: place pages to tail in > > > > __free_pages_core() > > > > > > > > That's another issue which is debugged here: > > > > > > > > http://lists.infradead.org/pipermail/ath11k/2020-November/000550.html > > > > > > > > > > Applying the patch and revert patch 7fef431be9c9 worked on the first > > > glance. > > > > > > After a couple of minutes the connection get broken. The kernel log > > > shows the following error: > > > > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd > > > ath11k_pc > > > i 0000:55:00.0: failed to enable PMF QOS: (-11 > > > > > > It is also not possible to unload the ath11k_pci, rmmod will hang. > > > > > > > > > > I can confirm the same behavior as Stefani so far. After applying the > > patch, and reverting commit 7fef431be9c9, I am able to connect to a > > network. It hasn't disconnected yet (I'm sending this email via that > > connection). I'll report what I find next. > > > > Thanks again for the help! Sigh.... sorry for the top post again. I'll now get a real email client.
