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 67C3FC388F9 for ; Wed, 11 Nov 2020 19:10:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 05B2F206F1 for ; Wed, 11 Nov 2020 19:10:54 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=mg.codeaurora.org header.i=@mg.codeaurora.org header.b="r6UUDV4H" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726101AbgKKTKy (ORCPT ); Wed, 11 Nov 2020 14:10:54 -0500 Received: from m42-4.mailgun.net ([69.72.42.4]:15059 "EHLO m42-4.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726203AbgKKTKx (ORCPT ); Wed, 11 Nov 2020 14:10:53 -0500 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1605121853; h=Content-Type: MIME-Version: Message-ID: In-Reply-To: Date: References: Subject: Cc: To: From: Sender; bh=9ZBr2gYhq/kxEVBkwsrQaZay+8/DYwvbFqCMkGtF49A=; b=r6UUDV4H0e2YYlQNAzJ1gox3yCVlYFdnYYwnoEvSdskNRw9DW1PV9S6UkgU5rDhicuf8o6uG TsZkN4c10pCqnCFkxexgp5nKW7ZxWUUrsSObR1eSXLSQDv9oVzqXq+ucxshy8ZgJHyO+ysvA dTZZ9OPmkwMFNw+QcMjFoSRVF7E= X-Mailgun-Sending-Ip: 69.72.42.4 X-Mailgun-Sid: WyI2YzdiNyIsICJsaW51eC1wY2lAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n02.prod.us-east-1.postgun.com with SMTP id 5fac3738b8c6a84a5c89c4d5 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Wed, 11 Nov 2020 19:10:48 GMT Sender: kvalo=codeaurora.org@mg.codeaurora.org Received: by smtp.codeaurora.org (Postfix, from userid 1001) id CC711C43395; Wed, 11 Nov 2020 19:10:47 +0000 (UTC) Received: from potku.adurom.net (88-114-240-156.elisa-laajakaista.fi [88.114.240.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kvalo) by smtp.codeaurora.org (Postfix) with ESMTPSA id 7891AC433C6; Wed, 11 Nov 2020 19:10:43 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 smtp.codeaurora.org 7891AC433C6 Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: aws-us-west-2-caf-mail-1.web.codeaurora.org; spf=fail smtp.mailfrom=kvalo@codeaurora.org From: Kalle Valo To: Thomas Krause 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 , wink@technolu.st Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 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> Date: Wed, 11 Nov 2020 21:10:41 +0200 In-Reply-To: <87v9ec9rk3.fsf@codeaurora.org> (Kalle Valo's message of "Wed, 11 Nov 2020 11:22:04 +0200") Message-ID: <87imab4slq.fsf@codeaurora.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org 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