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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no 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 04DB7C5517A for ; Wed, 11 Nov 2020 19:24:16 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 9796A2087D for ; Wed, 11 Nov 2020 19:24:15 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=technolu-st.20150623.gappssmtp.com header.i=@technolu-st.20150623.gappssmtp.com header.b="ExiNS17a" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727740AbgKKTYO (ORCPT ); Wed, 11 Nov 2020 14:24:14 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727702AbgKKTYO (ORCPT ); Wed, 11 Nov 2020 14:24:14 -0500 Received: from mail-ej1-x642.google.com (mail-ej1-x642.google.com [IPv6:2a00:1450:4864:20::642]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 430C4C0613D4 for ; Wed, 11 Nov 2020 11:24:12 -0800 (PST) Received: by mail-ej1-x642.google.com with SMTP id cw8so4281622ejb.8 for ; Wed, 11 Nov 2020 11:24:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technolu-st.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=17t0cJZV83rKsdnF26ww0x8Qr/bgJ69PEyc9Tg6QeSc=; b=ExiNS17a/zUnWHOCo86frpvNdG7ej33nbmJqo1kWfIWFOhO5vU83hkuoQWpKK38ysd aM/y7fynS/NWiLjeFIeky6lvAOKsO9RWsLM7Iv6PYnnPHJuMN14DzcDfVoabEEhFozWn YZ9sRNTRhU6PyfEgNjl57++iL9JXKN5aUsRFNGisW1eCJzkJYIT70ZtfeyxHWd2izt1x BJd+X+5/hw9VKe62FQk0pD8ogncWqB+NdtFy+UoWNCmVWHRkjifPgmlCU9DIkNv6PhWE 1ph4M76zE/KxHB0pkE9xuWk3cO0kyVaAD//AKv6cc2IE6/q3NxGYgjmhkObxpOMQQvif 4SIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=17t0cJZV83rKsdnF26ww0x8Qr/bgJ69PEyc9Tg6QeSc=; b=U9Iu7GU7WtCpGkt0bqfmbaHKiOtoNlx5gm7tc4VmIgOWa26tTQGwxeFq3Cq9EZtirI JkvZCo6ewyGQGsSiBxbcqPM69iIooCEYVbBvArEBdGrJESgHlcz9Q/dur0Ch0sdc/hWU E6wbFG+fo7754DK8hIJXv/A7DrlueMEr6Ei2XQDqobGcyFW+ZgrTfkdI6ab4tkms2j2X l5i1Ioezp5hIsNMiPl64gTVWOC+3FLHRcI17Al0cwtz3v2llxAY33H/hqnNCAC1ItfmL PQ+ql4qvJXkkLqY7dRld+GIHe/3NhVUOCnzUDp+dTnZirfTOkk73rxY7gn0XgqwJwd/q QbQg== X-Gm-Message-State: AOAM530HRXdUk6B6/c4d7Mzb2vEzSjKss1PCdGyu4TQKHsq+S+RrO2sJ 3FOirFMKKNFWuZXCylVxaZ4WG3F8bu2SED7zQbr0eA== X-Google-Smtp-Source: ABdhPJw7o+dPmaEGjq8oyHyvXpyezprGFoE+FcyvOGGYPi8wbF8KZirC7QFGBQ6ozUKd81XDNvNdvsU/Ra6dVjQAQd4= X-Received: by 2002:a17:906:8812:: with SMTP id zh18mr25328865ejb.361.1605122650885; Wed, 11 Nov 2020 11:24:10 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <87imab4slq.fsf@codeaurora.org> From: wi nk Date: Wed, 11 Nov 2020 20:24:00 +0100 Message-ID: Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 To: Kalle Valo Cc: Thomas Krause , 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Kalle, Thanks so much for your and your teams efforts. I've applied the patch, and I'm receiving some errors similar to what you thought might occur: [ 7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is experimental! [ 7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem 0x8e300000-0x8e3fffff 64bit] [ 7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002) [ 7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1 [ 8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed, result: 1, err: 48 [ 8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22 I've reverted the commit you mentioned and am rebuilding now. I'll test in a few minutes. Thanks! On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo wrote: > > Kalle Valo writes: > > > Thomas Krause writes: > > > >> Am 10.11.20 um 09:33 schrieb Kalle Valo: > >>> > >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a > >>>> separate "Virtualisation" setting in BIOS. See if you have that and try > >>>> enabling it. > >>> I was informed about another setting to test: try disabling "Enable > >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's > >>> what few people have recommended. > >>> > >>> Please let me know how it goes. > >>> > >> I have two options under "Virtualization" in the BIOS: "Enable Intel > >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were > >> enabled. Secure boot was also turned off. BIOS version is also at the > >> most current version 1.1.1. > > > > This is good to know, thanks for testing. Now we have explored all > > possible BIOS options as I know of. > > > >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it > >> would be best to contact Dell directly (even if I'm not sure if and > >> how fast they will respond). > > > > I have asked our people to report this to Dell, but no response yet. > > > >> If the driver would manage to work with only 1 vector, I assume this > >> would also make it work on my configuration, even with possible > >> performance hits. > > > > This is the workaround we are working on at the moment. There's now a > > proof of concept patch but I'm not certain if it will work. I'll post it > > as soon as I can and will provide the link in this thread. > > 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 > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail-ej1-x641.google.com ([2a00:1450:4864:20::641]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kcvj1-000700-U8 for ath11k@lists.infradead.org; Wed, 11 Nov 2020 19:24:13 +0000 Received: by mail-ej1-x641.google.com with SMTP id o23so4272016ejn.11 for ; Wed, 11 Nov 2020 11:24:11 -0800 (PST) MIME-Version: 1.0 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> In-Reply-To: <87imab4slq.fsf@codeaurora.org> From: wi nk Date: Wed, 11 Nov 2020 20:24:00 +0100 Message-ID: Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "ath11k" Errors-To: ath11k-bounces+kvalo=adurom.com@lists.infradead.org To: Kalle Valo Cc: Govind Singh , linux-pci@vger.kernel.org, Stefani Seibold , linux-wireless@vger.kernel.org, Devin Bayer , ath11k@lists.infradead.org, Thomas Krause , Bjorn Helgaas , Thomas Gleixner , Christoph Hellwig , David Woodhouse Kalle, Thanks so much for your and your teams efforts. I've applied the patch, and I'm receiving some errors similar to what you thought might occur: [ 7.802756] ath11k_pci 0000:55:00.0: WARNING: ath11k PCI support is experimental! [ 7.802797] ath11k_pci 0000:55:00.0: BAR 0: assigned [mem 0x8e300000-0x8e3fffff 64bit] [ 7.802815] ath11k_pci 0000:55:00.0: enabling device (0000 -> 0002) [ 7.803291] ath11k_pci 0000:55:00.0: MSI vectors: 1 [ 8.172623] ath11k_pci 0000:55:00.0: Respond mem req failed, result: 1, err: 48 [ 8.172624] ath11k_pci 0000:55:00.0: qmi failed to respond fw mem req:-22 I've reverted the commit you mentioned and am rebuilding now. I'll test in a few minutes. Thanks! On Wed, Nov 11, 2020 at 8:10 PM Kalle Valo wrote: > > Kalle Valo writes: > > > Thomas Krause writes: > > > >> Am 10.11.20 um 09:33 schrieb Kalle Valo: > >>> > >>>> I was told that on Dell XPS 15 (with a working QCA6390 setup) there's a > >>>> separate "Virtualisation" setting in BIOS. See if you have that and try > >>>> enabling it. > >>> I was informed about another setting to test: try disabling "Enable > >>> Secure Boot" in the BIOS. I don't know yet why it would help, but that's > >>> what few people have recommended. > >>> > >>> Please let me know how it goes. > >>> > >> I have two options under "Virtualization" in the BIOS: "Enable Intel > >> Virtualization Technology (VT)" and "VT for Direct I/O". Both were > >> enabled. Secure boot was also turned off. BIOS version is also at the > >> most current version 1.1.1. > > > > This is good to know, thanks for testing. Now we have explored all > > possible BIOS options as I know of. > > > >> Because of the dmesg errors Thomas Gleixner mentioned, I assume it > >> would be best to contact Dell directly (even if I'm not sure if and > >> how fast they will respond). > > > > I have asked our people to report this to Dell, but no response yet. > > > >> If the driver would manage to work with only 1 vector, I assume this > >> would also make it work on my configuration, even with possible > >> performance hits. > > > > This is the workaround we are working on at the moment. There's now a > > proof of concept patch but I'm not certain if it will work. I'll post it > > as soon as I can and will provide the link in this thread. > > 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 > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches -- ath11k mailing list ath11k@lists.infradead.org http://lists.infradead.org/mailman/listinfo/ath11k