From: Kalle Valo <kvalo@codeaurora.org>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
"linux-firmware@kernel.org" <linux-firmware@kernel.org>
Subject: Re: [PULL] ath10k firmware 20180219
Date: Mon, 26 Feb 2018 16:58:33 +0200 [thread overview]
Message-ID: <87606ju7ae.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <0e9db63d-41e9-eeb3-00d1-73b20df4bb3f@dd-wrt.com> (Sebastian Gottschall's message of "Thu, 22 Feb 2018 11:59:02 +0100")
Sebastian Gottschall <s.gottschall@dd-wrt.com> writes:
> on 9984 i see these messages with this firmware from time to time
>
> [272972.950788] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [272982.868922] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [335550.123780] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [335550.156332] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [335550.158813] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [335550.193144] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [365157.869540] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
> [365157.902452] ath10k_pci 0000:01:00.0: Unknown eventid: 36925
>
>
> according to the WMI header this maybe a critical internal error
Thanks for the report. We are working on a fix but just ignore the
warning for now.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2018-02-26 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 10:44 [PULL] ath10k firmware 20180219 Kalle Valo
2018-02-22 10:59 ` Sebastian Gottschall
2018-02-26 14:58 ` Kalle Valo [this message]
2018-02-27 9:05 ` Sebastian Gottschall
2018-02-27 13:22 ` Kalle Valo
2018-02-27 13:34 ` Sebastian Gottschall
2018-02-22 11:45 ` Josh Boyer
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=87606ju7ae.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=linux-firmware@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.gottschall@dd-wrt.com \
/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