From: Stefani Seibold <stefani@seibold.net>
To: ath11k@lists.infradead.org, Kalle Valo <kvalo@codeaurora.org>
Subject: Re: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Fri, 06 Nov 2020 12:57:08 +0100 [thread overview]
Message-ID: <b50d48a67bfb8797a4be0eea64c9514836f847af.camel@seibold.net> (raw)
In-Reply-To: <87wnz0hr9k.fsf@codeaurora.org>
>> i tried the latest ath11k driver using linux 5.10 rc2 on a new dell
>> 9310 XPS 13.
>>
>> The driver will always complain "failed to get 32 MSI vectors, only
-28
>> available".
>>
>> I think the -28 is the error code for ENOSPC return by the
>> pci_alloc_irq_vectors() function.
>>
>Please try enabling Virtualisation and VT-d in BIOS. And also enable
>CONFIG_IRQ_REMAP in kernel config.
Thanks for the advise. I already configured the BIOS and kernel in this
way. I also update the BIOS XPS 13 9310 Bios to 1.1.1, but the
"DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!"
still remains and therefor the
"failed to get 32 MSI vectors, only -28 available"
message.
The really bad thing is that the Killer Wi-Fi 6 AX500-DBS QCA6390 is
solder on the mainboard :-(
- Stefani
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-11-06 11:57 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 [this message]
2020-11-10 8:33 ` Kalle Valo
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=b50d48a67bfb8797a4be0eea64c9514836f847af.camel@seibold.net \
--to=stefani@seibold.net \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
/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.