From: Kalle Valo <kvalo@codeaurora.org>
To: Thomas Krause <thomaskrause@posteo.de>
Cc: ath11k@lists.infradead.org
Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Mon, 19 Oct 2020 11:09:45 +0300 [thread overview]
Message-ID: <87tuuqhc1i.fsf@codeaurora.org> (raw)
In-Reply-To: <2849fd39-a7a6-8366-7c78-fc9fec4dffa4@posteo.de> (Thomas Krause's message of "Sat, 17 Oct 2020 13:01:46 +0200")
Thomas Krause <thomaskrause@posteo.de> writes:
> some variants of Dell XPS 13 9310 model have a QCA6390 device
Do you happen to know which models exacly have it? I'm trying to find a
reasonably priced laptop with QCA6390 from Finland or EU, no luck yet.
Apparently there was a certain Dell XPS 15 9500 model but it was almost
4k EUR.
> and I was trying to make it work using the ath.git master branch (tag
> ath-202010011934).
>
> Unfortunatly, I get the following error messages when loading the module:
>
>> [ 672.277726] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support
>> is experimental!
>> [ 672.277925] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem
>> 0x8c300000-0x8c3fffff 64bit]
>> [ 672.278020] ath11k_pci 0000:56:00.0: failed to get 32 MSI
>> vectors, only -28 available
>> [ 672.278024] ath11k_pci 0000:56:00.0: failed to enable msi: -28
>> [ 672.278144] ath11k_pci: probe of 0000:56:00.0 failed with error -28
>
> -28 seems to reference ENOSPC, which seems to be related to the
> minimum number of vectors not beeing available.
I had the same problem as well back in the days, for me enabling
CONFIG_IRQ_REMAP helped. If it helps for you also I wonder if we should
mention that in the ath11k warning above :)
--
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-10-19 8:10 UTC|newest]
Thread overview: 46+ 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 [this message]
2020-10-20 20:46 ` Thomas Krause
2020-11-02 18:34 ` Kalle Valo
2020-11-02 18:49 ` Kalle Valo
2020-11-02 20:57 ` Bjorn Helgaas
2020-11-03 3:01 ` Carl Huang
2020-11-03 6:49 ` Kalle Valo
2020-11-03 16:08 ` Bjorn Helgaas
2020-11-03 21:08 ` Thomas Gleixner
2020-11-03 22:42 ` Thomas Gleixner
2020-11-09 18:44 ` Kalle Valo
2020-11-04 13:04 ` Thomas Krause
2020-11-04 15:26 ` Thomas Gleixner
2020-11-05 13:23 ` Kalle Valo
2020-11-06 11:57 ` Stefani Seibold
2020-11-10 8:33 ` Kalle Valo
2020-11-11 8:53 ` Thomas Krause
2020-11-11 9:22 ` Kalle Valo
2020-11-11 19:10 ` Kalle Valo
2020-11-11 19:24 ` wi nk
2020-11-11 19:30 ` wi nk
2020-11-11 19:45 ` Kalle Valo
2020-11-11 20:12 ` wi nk
2020-11-11 21:35 ` Stefani Seibold
2020-11-11 22:02 ` Stefani Seibold
2020-11-12 0:24 ` wi nk
2020-11-12 1:10 ` wi nk
2020-11-12 1:11 ` wi nk
2020-11-12 2:31 ` wi nk
2020-11-12 6:29 ` Carl Huang
2020-11-12 7:05 ` Stefani Seibold
2020-11-12 7:15 ` Kalle Valo
2020-11-12 7:41 ` wi nk
2020-11-12 8:59 ` Kalle Valo
2020-11-12 15:44 ` wi nk
2020-11-13 9:52 ` wi nk
2020-11-15 13:30 ` Thomas Krause
2020-11-15 19:55 ` wi nk
2020-11-17 15:49 ` wi nk
2020-11-17 20:59 ` Thomas Gleixner
2020-11-18 10:22 ` wi nk
2020-11-11 9:39 ` Thomas Gleixner
2020-11-06 11:45 ` Devin Bayer
2020-11-09 18:48 ` Kalle Valo
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=87tuuqhc1i.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox