From: Luciano Coelho <luciano.coelho@intel.com>
To: Nye Liu <nyet@nyet.org>, Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Intel Linux Wireless <linuxwifi@intel.com>,
Kalle Valo <kvalo@codeaurora.org>,
"David S. Miller" <davem@davemloft.net>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Fix Bug 199967 - change WARN_ON(1) to IWL_ERR()
Date: Sat, 18 Aug 2018 11:41:27 +0300 [thread overview]
Message-ID: <c052cdda16fa0df1b3672f4be9c20df053703ac0.camel@intel.com> (raw)
In-Reply-To: <20180818033555.18110-1-nyet@nyet.org>
On Fri, 2018-08-17 at 20:35 -0700, Nye Liu wrote:
> The TX_STATUS_FAIL_DEST_PS case fills logs with full backtraces, which
> are pretty useless. Just do IWL_ERR() printk.
>
> Signed-off-by: Nye Liu <nyet@nyet.org>
> ---
> drivers/net/wireless/intel/iwlwifi/mvm/tx.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/tx.c b/drivers/net/wireless/intel/iwlwifi/mvm/tx.c
> index cf2591f2ac23..87044953e6b4 100644
> --- a/drivers/net/wireless/intel/iwlwifi/mvm/tx.c
> +++ b/drivers/net/wireless/intel/iwlwifi/mvm/tx.c
> @@ -1407,8 +1407,10 @@ static void iwl_mvm_rx_tx_cmd_single(struct iwl_mvm *mvm,
> /* the FW should have stopped the queue and not
> * return this status
> */
> - WARN_ON(1);
> info->flags |= IEEE80211_TX_STAT_TX_FILTERED;
> + IWL_ERR(mvm, "TX_STATUS_FAIL_DEST_PS: "
> + "tid %d, status %x, flags %x\n", tid, status,
> + info->flags);
> break;
> default:
> break;
I think this error is serious enough and we would like to catch it when
it occurs so we can debug the actual cause.
But I agree that we shouldn't be repeating it millions of times. What
about just changing it to WARN_ON_ONCE() instead?
--
Cheers,
Luca.
next prev parent reply other threads:[~2018-08-18 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180818033555.18110-1-nyet@nyet.org>
2018-08-18 6:10 ` [PATCH] Fix Bug 199967 - change WARN_ON(1) to IWL_ERR() Kalle Valo
2018-08-18 8:41 ` Luciano Coelho [this message]
2018-08-18 16:11 ` Nye Liu
2018-08-18 16:52 ` Joe Perches
2018-08-18 18:41 ` Luciano Coelho
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=c052cdda16fa0df1b3672f4be9c20df053703ac0.camel@intel.com \
--to=luciano.coelho@intel.com \
--cc=davem@davemloft.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=nyet@nyet.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).