From: Dietmar Eggemann <[email protected]>
To: Ammar Faizi <[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: Thu, 14 Apr 2022 11:38:16 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 08/04/2022 08:03, Ammar Faizi wrote:
> On 4/7/22 5:52 PM, Dietmar Eggemann wrote:
>
> [...]
>
>> Looks like 21.10 finally abandoned legacy cgroup v1 and switched to v2
>> completely, which is now mounted under /sys/fs/cgroup .
>>
>> So your /sys/fs/cgroup/cgroup.controllers should contain `cpu`.
>>
>> Can you check if any of the cpu.max files under /sys/fs/cgroup has
>> something else then `max 100000` ?
>
> I only see "max 100000" at the moment. Not sure if it may change when I
> do other activities anyway. If you need more information, I can always
> send it, so feel free to ask.
Looks like you saw the same issue which got fixed here:
https://lkml.kernel.org/r/[email protected]
So nothing to do with CFS BW control. It's triggered by a task with very
low nice value and load_avg=1 during cfs_rq attach.
next prev parent reply other threads:[~2022-04-14 9:38 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 [this message]
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