From: Fabio Estevam <festevam@gmail.com>
To: "Paul E . McKenney" <paulmck@kernel.org>
Cc: Kalle Valo <kvalo@codeaurora.org>,
ath10k@lists.infradead.org,
linux-mmc <linux-mmc@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Marek Vasut <marex@denx.de>,
qais.yousef@arm.com, Frederic Weisbecker <frederic@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: NOHZ tick-stop error with ath10k SDIO
Date: Thu, 19 Aug 2021 10:24:51 -0300 [thread overview]
Message-ID: <CAOMZO5Ag1uUx4BqS=+ZQwULSrkE=sNMyWgsWvPQ4xY16ac=zsQ@mail.gmail.com> (raw)
In-Reply-To: <20210818175604.GX4126399@paulmck-ThinkPad-P17-Gen-1>
Hi Paul,
On Wed, Aug 18, 2021 at 2:56 PM Paul E. McKenney <paulmck@kernel.org> wrote:
> And it turns out that I am also seeing it in v5.14-rc2, just a lot less
> frequently than earlier. I have seen three instances of handler #02
> (NET_TX_SOFTIRQ?) over the past month or so while you are seeing handler
> #08 (BLOCK_SOFTIRQ?), in case that makes a difference.
>
> Adding Frederic and Thomas on CC, though I believe Frederic is off
> the grid at the moment.
In my case, these errors are very easy to reproduce so if you need me
to collect any debug
info, just let me know.
Thanks!
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2021-08-19 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 15:18 NOHZ tick-stop error with ath10k SDIO Fabio Estevam
2021-08-18 15:43 ` Paul E. McKenney
2021-08-18 16:29 ` Fabio Estevam
2021-08-18 17:02 ` Fabio Estevam
2021-08-18 17:56 ` Paul E. McKenney
2021-08-19 13:24 ` Fabio Estevam [this message]
2021-09-02 21:51 ` Thomas Gleixner
2021-09-02 22:09 ` Paul E. McKenney
2021-09-03 8:07 ` Thomas Gleixner
2021-09-04 21:10 ` Fabio Estevam
2021-09-05 13:00 ` Thomas Gleixner
2021-09-05 13:07 ` Fabio Estevam
2021-09-17 16:32 ` Qais Yousef
2021-09-17 17:09 ` Paul E. McKenney
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='CAOMZO5Ag1uUx4BqS=+ZQwULSrkE=sNMyWgsWvPQ4xY16ac=zsQ@mail.gmail.com' \
--to=festevam@gmail.com \
--cc=ath10k@lists.infradead.org \
--cc=frederic@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-mmc@vger.kernel.org \
--cc=marex@denx.de \
--cc=paulmck@kernel.org \
--cc=qais.yousef@arm.com \
--cc=tglx@linutronix.de \
--cc=ulf.hansson@linaro.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).