From: Ben Greear <greearb@candelatech.com>
To: "Tomislav Požega" <pozega.tomislav@gmail.com>, kvalo@codeaurora.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ath10k@lists.infradead.org, davem@davemloft.net,
torvalds@linux-foundation.org, johannes@sipsolutions.net,
linux-wireless@vger.kernel.org
Subject: Re: WARNING at net/mac80211/sta_info.c:1057 (__sta_info_destroy_part2())
Date: Mon, 21 Oct 2019 07:01:00 -0700 [thread overview]
Message-ID: <073b0ffb-187b-659e-0967-23ae44c5c660@candelatech.com> (raw)
In-Reply-To: <1571584320-29816-1-git-send-email-pozega.tomislav@gmail.com>
On 10/20/2019 08:12 AM, Tomislav Požega wrote:
>> -11 is -EAGAIN which would mean that the HTC credits have run out some
>> reason for the WMI command:
>>
>> if (ep->tx_credits < credits) {
>> ath10k_dbg(ar, ATH10K_DBG_HTC,
>> "htc insufficient credits ep %d required %d available %d\n",
>> eid, credits, ep->tx_credits);
>> spin_unlock_bh(&htc->tx_lock);
>> ret = -EAGAIN;
>> goto err_pull;
>> }
>>
>> Credits can run out, for example, if there's a lot of WMI command/event
>> activity and are not returned during the 3s wait, firmware crashed or
>> problems with the PCI bus.
>
> Hi
>
> Can this occur if the target memory is not properly allocated?
I have only seen this on wave-1 cards, and it is usually paired with situations
where the wave-1 stops doing WMI related interrupts properly as best as I can
understand. If I force the firmware to poll instead of waiting for irqs, then
WMI communication will work for a while...I have not implemented that on the
driver side though, so I still see these WMI timeout issues.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2019-10-21 14:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 10:05 WARNING at net/mac80211/sta_info.c:1057 (__sta_info_destroy_part2()) Linus Torvalds
2019-09-11 10:26 ` Johannes Berg
2019-09-11 11:58 ` Linus Torvalds
2019-09-11 12:04 ` Johannes Berg
2019-09-11 13:03 ` Ben Greear
2019-09-11 13:21 ` Linus Torvalds
2019-09-11 13:31 ` Ben Greear
2019-09-11 13:32 ` Kalle Valo
2019-09-11 18:19 ` Kalle Valo
2019-09-11 18:23 ` Johannes Berg
2019-09-11 18:48 ` Kalle Valo
2019-09-11 18:10 ` Kalle Valo
2019-10-20 15:12 ` Tomislav Požega
2019-10-21 14:01 ` Ben Greear [this message]
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=073b0ffb-187b-659e-0967-23ae44c5c660@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=davem@davemloft.net \
--cc=johannes@sipsolutions.net \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pozega.tomislav@gmail.com \
--cc=torvalds@linux-foundation.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 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).