From: "Pali Rohár" <pali@kernel.org>
To: Kalle Valo <kvalo@codeaurora.org>,
ath10k@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: ath10k_pci spams dmesg "failed to send pdev bss chan info request"
Date: Fri, 26 Jun 2020 09:41:19 +0200 [thread overview]
Message-ID: <20200626074119.2aonlyfqb3ve65p3@pali> (raw)
Hello!
During testing 5.8.0-rc2 kernel version with Compex WLE900VX card
(ath10k) I see following error in dmesg which is periodically repeating,
sometimes every second:
ath10k_pci 0000:01:00.0: failed to send pdev bss chan info request
Card has firmware version 10.1 and features wmi-10.x,has-wmi-mgmt-tx,mfp
That error message is located in file ath10k/mac.c in the function
ath10k_mac_update_bss_chan_survey().
I checked that 'ret' variable in that function contains value -95 which
is -EOPNOTSUPP. It seems that ath10k_wmi_pdev_bss_chan_info_request() is
not really supported by firmware 10.1.
That function is used only by ath10k_get_survey() function and
ath10k_get_survey() ignores all errors from the function
ath10k_mac_update_bss_chan_survey(). Which seems wrong as get_survey()
could return -EOPNOTSUPP when it is not supported.
Could we at least skip printing that error message when 'ret' is
-EOPNOTSUPP?
reply other threads:[~2020-06-26 7:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200626074119.2aonlyfqb3ve65p3@pali \
--to=pali@kernel.org \
--cc=ath10k@lists.infradead.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.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