From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from z5.mailgun.us ([104.130.96.5]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kd67M-0001Jm-3B for ath11k@lists.infradead.org; Thu, 12 Nov 2020 06:30:01 +0000 MIME-Version: 1.0 Date: Thu, 12 Nov 2020 14:29:53 +0800 From: Carl Huang Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 In-Reply-To: References: <20201103160838.GA246433@bjorn-Precision-5520> <874km61732.fsf@nanos.tec.linutronix.de> <87mtzxkus5.fsf@nanos.tec.linutronix.de> <87wnz0hr9k.fsf@codeaurora.org> <87ft5hehlb.fsf@codeaurora.org> <6b60c8f1-ec37-d601-92c2-97a485b73431@posteo.de> <87v9ec9rk3.fsf@codeaurora.org> <87imab4slq.fsf@codeaurora.org> Message-ID: <5f7f39fc69a6bc4219297f2d2c25e224@codeaurora.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "ath11k" Errors-To: ath11k-bounces+kvalo=adurom.com@lists.infradead.org To: wi nk Cc: Govind Singh , linux-pci@vger.kernel.org, Stefani Seibold , linux-wireless@vger.kernel.org, Devin Bayer , Christoph Hellwig , Thomas Krause , Bjorn Helgaas , Kalle Valo , Thomas Gleixner , ath11k@lists.infradead.org, David Woodhouse On 2020-11-12 10:31, wi nk wrote: > On Thu, Nov 12, 2020 at 2:11 AM wi nk wrote: >> >> On Thu, Nov 12, 2020 at 2:10 AM wi nk 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 wrote: >> > > >> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold 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@codeaurora.org/ >> > > > > >> > > > > 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. > > So the connection remained super stable for a while, so I decided to > tempt fate and suspend the laptop to see what would happen :). > > [ 5994.143715] PM: suspend exit > [ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 5997.260353] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: > -11 > [ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6000.332303] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6003.404368] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6016.204351] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6019.276323] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6031.052275] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout > [ 6034.128261] ath11k_pci 0000:55:00.0: failed to send > WMI_PDEV_SET_PARAM cmd > [ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11 > [ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request, > mode: 4, err = -110 > [ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode > off > > I was able to remove the ath11k module using rmmod -f , and then > modprobe ath11k + atk11k_pci and the device was able to reassociate > and bring the connection back up. Please apply below to have a try: https://patchwork.kernel.org/project/linux-wireless/patch/20201112062555.3335-1-cjhuang@codeaurora.org/ -- ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k