From: Kalle Valo <kvalo@codeaurora.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Govind Singh <govinds@codeaurora.org>,
linux-pci@vger.kernel.org, linux-wireless@vger.kernel.org,
Devin Bayer <dev@doubly.so>, Christoph Hellwig <hch@lst.de>,
Thomas Krause <thomaskrause@posteo.de>,
Bjorn Helgaas <helgaas@kernel.org>,
ath11k@lists.infradead.org, David Woodhouse <dwmw@amazon.co.uk>,
Stefani Seibold <stefani@seibold.net>
Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Tue, 10 Nov 2020 10:33:52 +0200 [thread overview]
Message-ID: <87ft5hehlb.fsf@codeaurora.org> (raw)
In-Reply-To: <87wnz0hr9k.fsf@codeaurora.org> (Kalle Valo's message of "Thu, 05 Nov 2020 15:23:03 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Thomas Gleixner <tglx@linutronix.de> writes:
>
>> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I
>>> hope this helps, if there is more I can do to debug it on my side I'm
>>> happy to do so.
>>
>>> [ 0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR
>>> reported at address 0!
>>> BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>>
>>> [ 0.103693] DMAR: Host address width 39
>>> [ 0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>>> [ 0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap
>>> 1c0000c40660462 ecap 69e2ff0505e
>>> [ 0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>>> [ 0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [ 0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>>> [ 0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [ 0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>>> [ 0.103707] DMAR: Parse DMAR table failure.
>>
>> which disables interrupt remapping and therefore the driver gets only
>> one MSI which makes it unhappy.
>>
>> Not that I'm surprised, it's Dell.... Can you check whether they have a
>> BIOS update for that box?
>
> 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.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo@codeaurora.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Govind Singh <govinds@codeaurora.org>,
linux-pci@vger.kernel.org, Stefani Seibold <stefani@seibold.net>,
linux-wireless@vger.kernel.org, Devin Bayer <dev@doubly.so>,
ath11k@lists.infradead.org,
Thomas Krause <thomaskrause@posteo.de>,
Bjorn Helgaas <helgaas@kernel.org>,
Christoph Hellwig <hch@lst.de>,
David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Tue, 10 Nov 2020 10:33:52 +0200 [thread overview]
Message-ID: <87ft5hehlb.fsf@codeaurora.org> (raw)
In-Reply-To: <87wnz0hr9k.fsf@codeaurora.org> (Kalle Valo's message of "Thu, 05 Nov 2020 15:23:03 +0200")
Kalle Valo <kvalo@codeaurora.org> writes:
> Thomas Gleixner <tglx@linutronix.de> writes:
>
>> On Wed, Nov 04 2020 at 14:04, Thomas Krause wrote:
>>> config) but CONFIG_INTEL_IOMMU_DEFAULT_ON needed to be set manually. I
>>> hope this helps, if there is more I can do to debug it on my side I'm
>>> happy to do so.
>>
>>> [ 0.050130] DMAR: [Firmware Bug]: Your BIOS is broken; DMAR
>>> reported at address 0!
>>> BIOS vendor: Dell Inc.; Ver: 1.1.1; Product Version:
>>
>>> [ 0.103693] DMAR: Host address width 39
>>> [ 0.103693] DMAR: DRHD base: 0x000000fed90000 flags: 0x0
>>> [ 0.103697] DMAR: dmar0: reg_base_addr fed90000 ver 4:0 cap
>>> 1c0000c40660462 ecap 69e2ff0505e
>>> [ 0.103698] DMAR: DRHD base: 0x000000fed84000 flags: 0x0
>>> [ 0.103701] DMAR: dmar1: reg_base_addr fed84000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [ 0.103702] DMAR: DRHD base: 0x000000fed86000 flags: 0x0
>>> [ 0.103706] DMAR: dmar2: reg_base_addr fed86000 ver 1:0 cap
>>> d2008c40660462 ecap f050da
>>> [ 0.103707] DMAR: DRHD base: 0x00000000000000 flags: 0x1
>>> [ 0.103707] DMAR: Parse DMAR table failure.
>>
>> which disables interrupt remapping and therefore the driver gets only
>> one MSI which makes it unhappy.
>>
>> Not that I'm surprised, it's Dell.... Can you check whether they have a
>> BIOS update for that box?
>
> 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.
--
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
next prev parent reply other threads:[~2020-11-10 8:34 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 11:01 pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 Thomas Krause
2020-10-19 8:09 ` Kalle Valo
2020-10-20 20:46 ` Thomas Krause
2020-11-02 18:34 ` Kalle Valo
2020-11-02 18:49 ` Kalle Valo
2020-11-02 18:49 ` Kalle Valo
2020-11-02 20:57 ` Bjorn Helgaas
2020-11-02 20:57 ` Bjorn Helgaas
2020-11-03 3:01 ` Carl Huang
2020-11-03 3:01 ` Carl Huang
2020-11-03 6:49 ` Kalle Valo
2020-11-03 6:49 ` Kalle Valo
2020-11-03 16:08 ` Bjorn Helgaas
2020-11-03 16:08 ` Bjorn Helgaas
2020-11-03 21:08 ` Thomas Gleixner
2020-11-03 21:08 ` Thomas Gleixner
2020-11-03 22:42 ` Thomas Gleixner
2020-11-03 22:42 ` Thomas Gleixner
2020-11-09 18:44 ` Kalle Valo
2020-11-09 18:44 ` Kalle Valo
2020-11-04 13:04 ` Thomas Krause
2020-11-04 13:04 ` Thomas Krause
2020-11-04 15:26 ` Thomas Gleixner
2020-11-04 15:26 ` Thomas Gleixner
2020-11-05 13:23 ` Kalle Valo
2020-11-05 13:23 ` Kalle Valo
2020-11-06 11:57 ` Stefani Seibold
2020-11-10 8:33 ` Kalle Valo [this message]
2020-11-10 8:33 ` Kalle Valo
2020-11-11 8:53 ` Thomas Krause
2020-11-11 8:53 ` Thomas Krause
2020-11-11 9:22 ` Kalle Valo
2020-11-11 9:22 ` Kalle Valo
2020-11-11 19:10 ` Kalle Valo
2020-11-11 19:10 ` Kalle Valo
2020-11-11 19:24 ` wi nk
2020-11-11 19:24 ` wi nk
2020-11-11 19:30 ` wi nk
2020-11-11 19:30 ` wi nk
2020-11-11 19:45 ` Kalle Valo
2020-11-11 19:45 ` Kalle Valo
2020-11-11 20:12 ` wi nk
2020-11-11 20:12 ` wi nk
2020-11-11 21:35 ` Stefani Seibold
2020-11-11 21:35 ` Stefani Seibold
2020-11-11 22:02 ` Stefani Seibold
2020-11-11 22:02 ` Stefani Seibold
2020-11-12 0:24 ` wi nk
2020-11-12 0:24 ` wi nk
2020-11-12 1:10 ` wi nk
2020-11-12 1:10 ` wi nk
2020-11-12 1:11 ` wi nk
2020-11-12 1:11 ` wi nk
2020-11-12 2:31 ` wi nk
2020-11-12 2:31 ` wi nk
2020-11-12 6:29 ` Carl Huang
2020-11-12 6:29 ` Carl Huang
2020-11-12 7:05 ` Stefani Seibold
2020-11-12 7:05 ` Stefani Seibold
2020-11-12 7:15 ` Kalle Valo
2020-11-12 7:15 ` Kalle Valo
2020-11-12 7:41 ` wi nk
2020-11-12 7:41 ` wi nk
2020-11-12 8:59 ` Kalle Valo
2020-11-12 8:59 ` Kalle Valo
2020-11-12 15:44 ` wi nk
2020-11-12 15:44 ` wi nk
2020-11-13 9:52 ` wi nk
2020-11-13 9:52 ` wi nk
2020-11-15 13:30 ` Thomas Krause
2020-11-15 13:30 ` Thomas Krause
2020-11-15 19:55 ` wi nk
2020-11-15 19:55 ` wi nk
2020-11-17 15:49 ` wi nk
2020-11-17 15:49 ` wi nk
2020-11-17 20:59 ` Thomas Gleixner
2020-11-17 20:59 ` Thomas Gleixner
2020-11-18 10:22 ` wi nk
2020-11-18 10:22 ` wi nk
2020-11-11 9:39 ` Thomas Gleixner
2020-11-11 9:39 ` Thomas Gleixner
2020-11-06 11:45 ` Devin Bayer
2020-11-06 11:45 ` Devin Bayer
2020-11-09 18:48 ` Kalle Valo
2020-11-09 18:48 ` Kalle Valo
2020-11-03 11:20 ` Devin Bayer
2020-11-03 11:20 ` Devin Bayer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ft5hehlb.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=dev@doubly.so \
--cc=dwmw@amazon.co.uk \
--cc=govinds@codeaurora.org \
--cc=hch@lst.de \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stefani@seibold.net \
--cc=tglx@linutronix.de \
--cc=thomaskrause@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.