From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Ben Segall <bsegall@google.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>, Mel Gorman <mgorman@suse.de>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [Linux 5.18-rc1] WARNING: CPU: 1 PID: 0 at kernel/sched/fair.c:3355 update_blocked_averages
Date: Wed, 6 Apr 2022 14:21:19 +0200 [thread overview]
Message-ID: <000457c2-57af-95e3-7dff-2cbd99f0de5f@arm.com> (raw)
In-Reply-To: <675544de-3369-e26e-65ba-3b28fff5c126@gnuweeb.org>
On 05/04/2022 15:13, Ammar Faizi wrote:
> 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.
Can you check that CFS Bandwidth control (CONFIG_CFS_BANDWIDTH=y) is
still not used on Ubuntu desktop 21.10?
It shouldn't but I can't verify since I'm still on 20.04 LTS Desktop:
$ mount | grep "cgroup2\|\bcpu\b"
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
CPU controller is still used in cgroupv1. So cgroupv2 can't use it:
$ cat /sys/fs/cgroup/unified/cgroup.controllers
/* empty */
And there is no cgroupv1 hierarchy under /sys/fs/cgroup/cpu,cpuacct/ .
No cpu.cfs_quota_us files with something other than -1.
So CFS Bandwidth control is not used.
[...]
next prev parent reply other threads:[~2022-04-06 15:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 6:19 Ammar Faizi
2022-04-05 12:21 ` Dietmar Eggemann
2022-04-05 13:13 ` Ammar Faizi
2022-04-06 12:21 ` Dietmar Eggemann [this message]
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 \
--in-reply-to=000457c2-57af-95e3-7dff-2cbd99f0de5f@arm.com \
--to=dietmar.eggemann@arm.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=gwml@vger.gnuweeb.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®