ath10k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: paulmck@kernel.org, Fabio Estevam <festevam@gmail.com>
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@kernel.org
Subject: Re: NOHZ tick-stop error with ath10k SDIO
Date: Thu, 02 Sep 2021 23:51:15 +0200	[thread overview]
Message-ID: <87czpqbq98.ffs@tglx> (raw)
In-Reply-To: <20210818175604.GX4126399@paulmck-ThinkPad-P17-Gen-1>

Paul,

On Wed, Aug 18 2021 at 10:56, Paul E. McKenney wrote:
> On Wed, Aug 18, 2021 at 02:02:17PM -0300, Fabio Estevam wrote:
>> On Wed, Aug 18, 2021 at 1:29 PM Fabio Estevam <festevam@gmail.com> wrote:
>> > On Wed, Aug 18, 2021 at 12:43 PM Paul E. McKenney <paulmck@kernel.org> wrote:
>> >
>> > > I believe that you need this commit (and possibly some prerequsites):
>> > >
>> > > 47c218dcae65 ("tick/sched: Prevent false positive softirq pending warnings on RT")
>> > >
>> > > Adding Qais on CC for his thoughts.
>> >
>> > Thanks for the suggestion, but I am running 5.13.11, which already
>> > contains this commit.
>> >
>> > Any extra logs I should capture to help us understand the problem?
>> 
>> In case it helps, I followed your suggestion from:
>> https://lkml.org/lkml/2020/12/10/676
>> 
>> With the debug patch and suggested command line, I get the following log:
>> https://pastebin.com/raw/X96zKw7i
>
> 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.

Huch? #02 is TIMER_SOFTIRQ and #08 is NET_TX_SOFTIRQ.

And looking at that ftrace output in the pastebin there is nothing which
raises NET_TX_SOFTIRQ but then the warning claims it is pending.

This does not make any sense at all.

Thanks,

        tglx



_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

  parent reply	other threads:[~2021-09-02 21:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 15:18 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
2021-09-02 21:51         ` Thomas Gleixner [this message]
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=87czpqbq98.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=ath10k@lists.infradead.org \
    --cc=festevam@gmail.com \
    --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=ulf.hansson@linaro.org \
    --subject='Re: NOHZ tick-stop error with ath10k SDIO' \
    /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

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).