From: Kalle Valo <kvalo@codeaurora.org>
To: Sathishkumar Muruganandam <murugana@codeaurora.org>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: ath10k: Suppress "Unknown eventid: 36925" warnings
Date: Thu, 29 Mar 2018 08:53:52 +0000 (UTC) [thread overview]
Message-ID: <20180329085352.0C0D060C55@smtp.codeaurora.org> (raw)
In-Reply-To: <1522049641-19521-1-git-send-email-murugana@codeaurora.org>
Sathishkumar Muruganandam <murugana@codeaurora.org> wrote:
> FW has Smart Logging feature enabled by default for detecting failures
> and processing FATAL_CONDITION_EVENTID (36925 - 0x903D) back to host.
>
> Since ath10k doesn't implement the Smart Logging and FATAL CONDITION
> EVENT processing yet, suppressing the unknown event ID warning by moving
> this under ATH10K_DBG_WMI.
>
> Simulated the same issue by having associated STA powered off when
> ping flood was running from AP backbone. This triggerd STA KICKOUT
> in AP followed by FATAL CONDITION event 36925.
>
> Issue was reproduced and verified in below DUT
> ------------------------------------------------
> AP mode of OpenWRT QCA9984 running 6.0.8 with FW ver 10.4-3.5.3-00053
>
> Signed-off-by: Sathishkumar Muruganandam <murugana@codeaurora.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
606204bb863f ath10k: suppress "Unknown eventid: 36925" warnings
--
https://patchwork.kernel.org/patch/10307269/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2018-03-29 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 7:34 [PATCH] ath10k: Suppress "Unknown eventid: 36925" warnings Sathishkumar Muruganandam
2018-03-26 7:34 ` Sathishkumar Muruganandam
2018-03-29 8:53 ` Kalle Valo
2018-03-29 8:53 ` Kalle Valo [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=20180329085352.0C0D060C55@smtp.codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=murugana@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.