public inbox for [email protected]
 help / color / mirror / Atom feed
From: Ammar Faizi <[email protected]>
To: Dietmar Eggemann <[email protected]>,
	Linux Kernel Mailing List <[email protected]>
Cc: Ben Segall <[email protected]>,
	Daniel Bristot de Oliveira <[email protected]>,
	GNU/Weeb Mailing List <[email protected]>,
	Ingo Molnar <[email protected]>,
	Juri Lelli <[email protected]>, Mel Gorman <[email protected]>,
	Peter Zijlstra <[email protected]>,
	Steven Rostedt <[email protected]>,
	Vincent Guittot <[email protected]>
Subject: Re: [Linux 5.18-rc1] WARNING: CPU: 1 PID: 0 at kernel/sched/fair.c:3355 update_blocked_averages
Date: Tue, 5 Apr 2022 20:29:08 +0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

On 4/5/22 7:21 PM, Dietmar Eggemann wrote:
> Maybe you could split the SCHED_WARN_ON so we know which signal causes this?
> 
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index d4bd299d67ab..0d45e09e5bfc 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -3350,9 +3350,9 @@ static inline bool cfs_rq_is_decayed(struct cfs_rq
> *cfs_rq)
>           * Make sure that rounding and/or propagation of PELT values never
>           * break this.
>           */
> -       SCHED_WARN_ON(cfs_rq->avg.load_avg ||
> -                     cfs_rq->avg.util_avg ||
> -                     cfs_rq->avg.runnable_avg);
> +       SCHED_WARN_ON(cfs_rq->avg.load_avg);
> +       SCHED_WARN_ON(cfs_rq->avg.util_avg);
> +       SCHED_WARN_ON(cfs_rq->avg.runnable_avg);
> 
>          return true;
>   }

error: corrupt patch at line 6

Trivial enough, fixed it. Compiling now...

ammarfaizi2@integral2:~/work/linux.work$ git log -n1
commit 3123109284176b1532874591f7c81f3837bbdc17 (HEAD -> master, tag: v5.18-rc1, @torvalds/linux/master)
Author: Linus Torvalds <[email protected]>
Date:   Sun Apr 3 14:08:21 2022 -0700

     Linux 5.18-rc1
ammarfaizi2@integral2:~/work/linux.work$ git diff
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index d4bd299d67ab..0d45e09e5bfc 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -3350,9 +3350,9 @@ static inline bool cfs_rq_is_decayed(struct cfs_rq *cfs_rq)
  	 * Make sure that rounding and/or propagation of PELT values never
  	 * break this.
  	 */
-	SCHED_WARN_ON(cfs_rq->avg.load_avg ||
-		      cfs_rq->avg.util_avg ||
-		      cfs_rq->avg.runnable_avg);
+	SCHED_WARN_ON(cfs_rq->avg.load_avg);
+	SCHED_WARN_ON(cfs_rq->avg.util_avg);
+	SCHED_WARN_ON(cfs_rq->avg.runnable_avg);
  
  	return true;
  }
ammarfaizi2@integral2:~/work/linux.work$

-- 
Ammar Faizi

      parent reply	other threads:[~2022-04-05 13:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04  6:19 [Linux 5.18-rc1] WARNING: CPU: 1 PID: 0 at kernel/sched/fair.c:3355 update_blocked_averages Ammar Faizi
2022-04-05 12:21 ` Dietmar Eggemann
2022-04-05 13:13   ` Ammar Faizi
2022-04-06 12:21     ` Dietmar Eggemann
2022-04-06 20:34       ` Ammar Faizi
2022-04-07 10:52         ` Dietmar Eggemann
2022-04-08  6:03           ` Ammar Faizi
2022-04-14  9:38             ` Dietmar Eggemann
2022-04-15 14:43               ` Ammar Faizi
2022-04-05 13:29   ` 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 \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    [email protected] \
    /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