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:13:42 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/5/22 7:21 PM, Dietmar Eggemann wrote:
> Tried to recreate the issue but no success so far. I used you config
> file, clang-14 and a Xeon CPU E5-2690 v2 (2 sockets 40 CPUs) with 20
> two-level cgoupv1 taskgroups '/X/Y' with 'hackbench (10 groups, 40 fds)
> + idling' running in all '/X/Y/'.
>
> What userspace are you running?
HP Laptop, Intel i7-1165G7, 8 CPUs, with 16 GB of RAM. Ubuntu 21.10. Just for
daily workstation. Compiling kernel, browsing and coding stuff.
> There seemed to be some pressure on your machine when it happened?
Yeah, might be, I don't fully remember the activity at the time it
happened, though.
>> <6>[13420.623334][ C7] perf: interrupt took too long (2530 > 2500),
>> lowering kernel.perf_event_max_sample_rate to 78900
>
> Maybe you could split the SCHED_WARN_ON so we know which signal causes this?
OK, I will apply the diff on top of 5.18-rc1 and will start using it for daily
routine tomorrow morning. Let's see if I can hit this bug again. Will send an
update later...
Thank you.
> 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;
> }
>
> [...]
--
Ammar Faizi
next prev parent reply other threads:[~2022-04-05 13:13 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 [this message]
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
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