From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-10.4 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,NICE_REPLY_A,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 681CEC56202 for ; Sun, 15 Nov 2020 13:30:36 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 25BDD23A32 for ; Sun, 15 Nov 2020 13:30:36 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=posteo.de header.i=@posteo.de header.b="ad2eT7c2" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726949AbgKONaP (ORCPT ); Sun, 15 Nov 2020 08:30:15 -0500 Received: from mout01.posteo.de ([185.67.36.65]:43266 "EHLO mout01.posteo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726438AbgKONaO (ORCPT ); Sun, 15 Nov 2020 08:30:14 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 5E0C4160060 for ; Sun, 15 Nov 2020 14:30:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1605447011; bh=MGqMsgArhZl+KrAtGwxgm1ffeCx32N+ssaCovhTwn1w=; h=To:Cc:From:Subject:Date:From; b=ad2eT7c23Z+XuPVzHLMv5JN57GRDkTzKad6+9LdRgrX/QkoeAfpJ8RDs571IxLCpa BoyUknVDi5mR/oxj3Ql05Wojfw9tLNPQhrlj/NvZnQYTmPTFX0s5/pvVGiJQBFBHXD pAwQzcf62lnqU4vyUXIKgGcx009G65K+OdHmMiBgecn96i0TECfUj+6z0PbNCdjL8g 3t1Tg9rWqDKGFhCUSnfH3ANKpSFXUfgi/PtI7n9zz3puk/XQxxpVAqJ0KN+S0W97UI iJHHJ/d6rqcTB7SG+/rU31eiT5+GYk/M9b0RS7wjbLR1Mde3nf4eluv2gXT/Sz2nTR 3Htop1slosBsA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4CYtNv6Lphz6tmL; Sun, 15 Nov 2020 14:30:07 +0100 (CET) To: wi nk , Kalle Valo Cc: Govind Singh , linux-pci@vger.kernel.org, Stefani Seibold , linux-wireless@vger.kernel.org, Devin Bayer , Christoph Hellwig , Bjorn Helgaas , Thomas Gleixner , ath11k@lists.infradead.org, David Woodhouse 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> <0b58872b4f27dbf5aad2a39f5ec4a066e080d806.camel@seibold.net> <875z6b3v22.fsf@codeaurora.org> <87pn4j2bna.fsf@codeaurora.org> From: Thomas Krause Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 Message-ID: Date: Sun, 15 Nov 2020 14:30:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.3.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Am 12.11.20 um 16:44 schrieb wi nk: > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo wrot= e: >> wi nk writes: >> >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo wro= te: >>>> Stefani Seibold 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=3D0x411 status=3D0 aid=3D8) >>>>>> [ 16.738443] wlp85s0: associated >>>>>> [ 16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link become= s >>>>>> 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 bran= ch >>>>>> did you apply it to? I applied it to ath11k-qca6390-bringup and w= hen >>>>>> 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 luc= ky >>>>>> 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 th= e >>>> baseline when debuggin these ath11k problems. It helps to compare th= e >>>> results if everyone have the same baseline. >>>> >>>> -- >>>> https://patchwork.kernel.org/project/linux-wireless/list/ >>>> >>>> https://wireless.wiki.kernel.org/en/developers/documentation/submitt= ingpatches >>> Absolutely, I'll rebuild to 5.10 later today and apply the same serie= s >>> of patches and report back. >> Great, thanks. >> >>> I'll also test out the patch on both versions from Carl to fix >>> resuming. It stands to reason that we may be seeing another regressio= n >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see= >>> any disconnections or instability once the interface is online. >> Yeah, there is something strange happening between v5.9 and v5.10 we >> have not yet figured out. Most likely it has something to do with memo= ry >> allocations and DMA transfers failing, but no clear understanding yet.= >> >> But to keep things simple let's only discuss the MSI problem on this >> thread, and discuss the timeouts in the another thread: >> >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html >> >> I'll include you and other reporters to that thread. >> >> -- >> https://patchwork.kernel.org/project/linux-wireless/list/ >> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittin= gpatches > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch > applied and 7fef431be9c9 reverted. I can't get my machine to boot > into anything usable with that configuration. I'm running ubuntu so > its starting right into X and sometime between showing the available > users and me clicking the icon to login the machine freezes. I can > see in the system tray that the wifi adapter is being activated and > appears to have associated with an AP, I just can't do much beyond > that as the keyboard backlight wakes up, but the caps lock key doesn't > work. I see similar behavior with the 5.9 configuration, but after a > reboot or two I win whatever race is occuring. With 5.10, I tried > maybe 10-15 times with 0 success. I can confirm this behavior on my configuration. I managed to login once = and select the Wifi and connect to it. It seemed curiously enough be=20 stable long enough to enter the Wifi passphrase. After the connection=20 was established, the system hang and on each attempt to reboot into the=20 graphical system it would freeze at some point (sometimes even before=20 showing the login screen). Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same=20 behavior) with the patch applied, 7fef431be9c9 reverted and firmware=20 downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mout02.posteo.de ([185.67.36.66]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1keI6n-0004P1-1D for ath11k@lists.infradead.org; Sun, 15 Nov 2020 13:30:22 +0000 Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id CED332400FC for ; Sun, 15 Nov 2020 14:30:11 +0100 (CET) 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> <0b58872b4f27dbf5aad2a39f5ec4a066e080d806.camel@seibold.net> <875z6b3v22.fsf@codeaurora.org> <87pn4j2bna.fsf@codeaurora.org> From: Thomas Krause Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 Message-ID: Date: Sun, 15 Nov 2020 14:30:05 +0100 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US 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 , Kalle Valo Cc: Govind Singh , linux-pci@vger.kernel.org, Stefani Seibold , linux-wireless@vger.kernel.org, Devin Bayer , ath11k@lists.infradead.org, Bjorn Helgaas , Thomas Gleixner , Christoph Hellwig , David Woodhouse Am 12.11.20 um 16:44 schrieb wi nk: > On Thu, Nov 12, 2020 at 10:00 AM Kalle Valo wrote: >> wi nk writes: >> >>> On Thu, Nov 12, 2020 at 8:15 AM Kalle Valo wrote: >>>> Stefani Seibold 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 >>> Absolutely, I'll rebuild to 5.10 later today and apply the same series >>> of patches and report back. >> Great, thanks. >> >>> I'll also test out the patch on both versions from Carl to fix >>> resuming. It stands to reason that we may be seeing another regression >>> between Stefani (5.10) and myself (5.9 bringup branch) as I don't see >>> any disconnections or instability once the interface is online. >> Yeah, there is something strange happening between v5.9 and v5.10 we >> have not yet figured out. Most likely it has something to do with memory >> allocations and DMA transfers failing, but no clear understanding yet. >> >> But to keep things simple let's only discuss the MSI problem on this >> thread, and discuss the timeouts in the another thread: >> >> http://lists.infradead.org/pipermail/ath11k/2020-November/000641.html >> >> I'll include you and other reporters to that thread. >> >> -- >> https://patchwork.kernel.org/project/linux-wireless/list/ >> >> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches > Ok, I've tried a clean checkout of 5.10-rc2 with the one MSI patch > applied and 7fef431be9c9 reverted. I can't get my machine to boot > into anything usable with that configuration. I'm running ubuntu so > its starting right into X and sometime between showing the available > users and me clicking the icon to login the machine freezes. I can > see in the system tray that the wifi adapter is being activated and > appears to have associated with an AP, I just can't do much beyond > that as the keyboard backlight wakes up, but the caps lock key doesn't > work. I see similar behavior with the 5.9 configuration, but after a > reboot or two I win whatever race is occuring. With 5.10, I tried > maybe 10-15 times with 0 success. I can confirm this behavior on my configuration. I managed to login once and select the Wifi and connect to it. It seemed curiously enough be stable long enough to enter the Wifi passphrase. After the connection was established, the system hang and on each attempt to reboot into the graphical system it would freeze at some point (sometimes even before showing the login screen). Kernel was both based on 5.10-rc2 and 5.10-rc3 (I did see the same behavior) with the patch applied, 7fef431be9c9 reverted and firmware downloaded and copied to /lib/firmware/ath11k/QCA6390/hw2.0/. -- ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k