From: wi nk <wink@technolu.st>
To: Stefani Seibold <stefani@seibold.net>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Thomas Krause <thomaskrause@posteo.de>,
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>,
Bjorn Helgaas <helgaas@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
ath11k@lists.infradead.org, David Woodhouse <dwmw@amazon.co.uk>
Subject: Re: pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310
Date: Thu, 12 Nov 2020 03:31:57 +0100 [thread overview]
Message-ID: <CAHUdJJWsCo6NJ6qr6kj=SASs+jO+fJFc3HhOO=fyek=OxSQa2Q@mail.gmail.com> (raw)
In-Reply-To: <CAHUdJJUkvcShSXw4mkFUDcEh101xNQbOUc0YEv6-TyLdyTs4Og@mail.gmail.com>
On Thu, Nov 12, 2020 at 2:11 AM wi nk <wink@technolu.st> wrote:
>
> On Thu, Nov 12, 2020 at 2:10 AM wi nk <wink@technolu.st> wrote:
> >
> > I've yet to see any instability after 45 minutes of exercising it, I
> > do see a couple of messages that came out of the driver:
> >
> > [ 8.963389] ath11k_pci 0000:55:00.0: Unknown eventid: 0x16005
> > [ 11.342317] ath11k_pci 0000:55:00.0: Unknown eventid: 0x1d00a
> >
> > then when it associates:
> >
> > [ 16.718895] wlp85s0: send auth to ec:08:6b:27:01:ea (try 1/3)
> > [ 16.722636] wlp85s0: authenticated
> > [ 16.724150] wlp85s0: associate with ec:08:6b:27:01:ea (try 1/3)
> > [ 16.726486] wlp85s0: RX AssocResp from ec:08:6b:27:01:ea
> > (capab=0x411 status=0 aid=8)
> > [ 16.738443] wlp85s0: associated
> > [ 16.764966] IPv6: ADDRCONF(NETDEV_CHANGE): wlp85s0: link becomes ready
> >
> > The adapter is achieving around 500 mbps on my gigabit connection, my
> > 2018 mbp sees around 650, so it's doing pretty well so far.
> >
> > Stefani - when you applied the patch that Kalle shared, which branch
> > did you apply it to? I applied it to ath11k-qca6390-bringup and when
> > I revert 7fef431be9c9 there is a small merge conflict I needed to
> > resolve. I wonder if either the starting branch, or your chosen
> > resolution are related to the instability you see (or I'm just lucky
> > so far! :)).
> >
> > On Thu, Nov 12, 2020 at 1:24 AM wi nk <wink@technolu.st> wrote:
> > >
> > > On Wed, Nov 11, 2020 at 11:02 PM Stefani Seibold <stefani@seibold.net> wrote:
> > > >
> > > > On Wed, 2020-11-11 at 21:10 +0200, Kalle Valo wrote:
> > > > >
> > > > > 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
> > > > >
> > > >
> > > > Applying the patch and revert patch 7fef431be9c9 worked on the first
> > > > glance.
> > > >
> > > > After a couple of minutes the connection get broken. The kernel log
> > > > shows the following error:
> > > >
> > > > ath11k_pci 0000:55:00.0: wmi command 16387 timeout
> > > > ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
> > > > ath11k_pc
> > > > i 0000:55:00.0: failed to enable PMF QOS: (-11
> > > >
> > > > It is also not possible to unload the ath11k_pci, rmmod will hang.
> > > >
> > > >
> > >
> > > I can confirm the same behavior as Stefani so far. After applying the
> > > patch, and reverting commit 7fef431be9c9, I am able to connect to a
> > > network. It hasn't disconnected yet (I'm sending this email via that
> > > connection). I'll report what I find next.
> > >
> > > Thanks again for the help!
>
> Sigh.... sorry for the top post again. I'll now get a real email client.
So the connection remained super stable for a while, so I decided to
tempt fate and suspend the laptop to see what would happen :).
[ 5994.143715] PM: suspend exit
[ 5997.260351] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 5997.260353] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 5997.260356] ath11k_pci 0000:55:00.0: failed to enable dynamic bw: -11
[ 6000.332299] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6000.332303] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6000.332308] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6003.404365] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6003.404368] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6003.404373] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6016.204347] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6016.204351] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6016.204357] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6019.276319] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6019.276323] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6019.276329] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6031.052272] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6031.052275] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6031.052279] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6034.128257] ath11k_pci 0000:55:00.0: wmi command 16387 timeout
[ 6034.128261] ath11k_pci 0000:55:00.0: failed to send WMI_PDEV_SET_PARAM cmd
[ 6034.128265] ath11k_pci 0000:55:00.0: failed to enable PMF QOS: (-11
[ 6039.500241] ath11k_pci 0000:55:00.0: qmi failed set mode request,
mode: 4, err = -110
[ 6039.500244] ath11k_pci 0000:55:00.0: qmi failed to send wlan mode off
I was able to remove the ath11k module using rmmod -f , and then
modprobe ath11k + atk11k_pci and the device was able to reassociate
and bring the connection back up.
next prev parent reply other threads:[~2020-11-12 5:39 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2849fd39-a7a6-8366-7c78-fc9fec4dffa4@posteo.de>
[not found] ` <87tuuqhc1i.fsf@codeaurora.org>
[not found] ` <1ce6f735-21ff-db7e-c8dc-d567761964aa@posteo.de>
2020-11-02 18:49 ` pci_alloc_irq_vectors fails ENOSPC for XPS 13 9310 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
[not found] ` <fa26ac8b-ed48-7ea3-c21b-b133532716b8@posteo.de>
2020-11-04 15:26 ` Thomas Gleixner
2020-11-05 13:23 ` Kalle Valo
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 [this message]
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='CAHUdJJWsCo6NJ6qr6kj=SASs+jO+fJFc3HhOO=fyek=OxSQa2Q@mail.gmail.com' \
--to=wink@technolu.st \
--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=kvalo@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).