All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
	Daniel Bristot de Oliveira <bristot@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ammar Faizi <ammarfaizi2@gmail.com>
Subject: Re: WARNING: CPU: 0 PID: 12 at kernel/sched/fair.c:3306 update_blocked_averages+0x941/0x9a0
Date: Mon, 2 Aug 2021 19:52:13 +0700	[thread overview]
Message-ID: <9d1680de-39e5-609c-7410-7baabfb079e5@gnuweeb.org> (raw)
In-Reply-To: <7473b5ba-72bf-7836-44a6-42851081a277@arm.com>

On 8/2/21 3:42 PM, Dietmar Eggemann wrote:
> So you're running with:
>
> 9e077b52d86a - sched/pelt: Check that *_avg are null when *_sum are
> (2021-06-17 Vincent Guittot)
>
> but not with:
>
> ceb6ba45dc80 - sched/fair: Sync load_sum with load_avg after dequeue
> (2021-07-02 Vincent Guittot)
>
> The SCHED_WARN_ON you're hitting is harmless and just tells you that the
> PELT load_avg and load_sum part of one of your cfs_rq's is not aligned.
> Has to be load (and not util or runnable) since load is the only one
> still not fixed in f55966571d5e.
>
> This should go away once you applied ceb6ba45dc80.

Alright, I have just moved to 5.14-rc4 and doesn't seem to have this
issue anymore.

Thanks for the response, Dietmar.

  Ammar


      reply	other threads:[~2021-08-02 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 15:21 WARNING: CPU: 0 PID: 12 at kernel/sched/fair.c:3306 update_blocked_averages+0x941/0x9a0 Ammar Faizi
2021-08-02  8:42 ` Dietmar Eggemann
2021-08-02 12:52   ` Ammar Faizi [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=9d1680de-39e5-609c-7410-7baabfb079e5@gnuweeb.org \
    --to=ammarfaizi2@gnuweeb.org \
    --cc=ammarfaizi2@gmail.com \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@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 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.