From: Vincent Guittot <vincent.guittot@linaro.org>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.6-rc3: WARNING: CPU: 48 PID: 17435 at kernel/sched/fair.c:380 enqueue_task_fair+0x328/0x440
Date: Fri, 28 Feb 2020 17:35:45 +0100 [thread overview]
Message-ID: <20200228163545.GA18662@vingu-book> (raw)
In-Reply-To: <b664f050-72d6-a483-be0a-8504f687f225@de.ibm.com>
Le vendredi 28 févr. 2020 à 16:42:27 (+0100), Christian Borntraeger a écrit :
>
>
> On 28.02.20 16:37, Vincent Guittot wrote:
> > On Fri, 28 Feb 2020 at 16:08, Christian Borntraeger
> > <borntraeger@de.ibm.com> wrote:
> >>
> >> Also happened with 5.4:
> >> Seems that I just happen to have an interesting test workload/system size interaction
> >> on a newly installed system that triggers this.
> >
> > you will probably go back to 5.1 which is the version where we put
> > back the deletion of unused cfs_rq from the list which can trigger the
> > warning:
> > commit 039ae8bcf7a5 : (Fix O(nr_cgroups) in the load balancing path)
> >
> > AFAICT, we haven't changed this since
>
> So you do know what is the problem? If not is there any debug option or
> patch that I could apply to give you more information?
No I don't know what is happening. Your test probably goes through an unexpected path
Would it be difficult for me to reproduce your test env ?
There is an optimization in the code which could generate problem if assumption is not
true. Could you try the patch below ?
---
kernel/sched/fair.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 3c8a379c357e..beb773c23e7d 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -4035,8 +4035,8 @@ enqueue_entity(struct cfs_rq *cfs_rq, struct sched_entity *se, int flags)
__enqueue_entity(cfs_rq, se);
se->on_rq = 1;
+ list_add_leaf_cfs_rq(cfs_rq);
if (cfs_rq->nr_running == 1) {
- list_add_leaf_cfs_rq(cfs_rq);
check_enqueue_throttle(cfs_rq);
}
}
--
2.17.1
>
next prev parent reply other threads:[~2020-02-28 16:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 7:54 5.6-rc3: WARNING: CPU: 48 PID: 17435 at kernel/sched/fair.c:380 enqueue_task_fair+0x328/0x440 Christian Borntraeger
2020-02-28 12:04 ` Christian Borntraeger
2020-02-28 13:32 ` Vincent Guittot
2020-02-28 13:43 ` Christian Borntraeger
2020-02-28 15:08 ` Christian Borntraeger
2020-02-28 15:37 ` Vincent Guittot
2020-02-28 15:42 ` Christian Borntraeger
2020-02-28 16:32 ` Qais Yousef
2020-02-28 16:35 ` Vincent Guittot [this message]
2020-03-02 11:16 ` Christian Borntraeger
2020-03-02 18:17 ` Christian Borntraeger
2020-03-03 7:37 ` Christian Borntraeger
2020-03-03 7:55 ` Vincent Guittot
2020-03-04 15:26 ` Vincent Guittot
2020-03-04 17:42 ` Christian Borntraeger
2020-03-04 17:51 ` Vincent Guittot
2020-03-04 19:19 ` Dietmar Eggemann
2020-03-04 19:38 ` Christian Borntraeger
2020-03-04 19:59 ` Christian Borntraeger
2020-03-05 9:30 ` Vincent Guittot
2020-03-05 11:28 ` Christian Borntraeger
2020-03-05 12:12 ` Dietmar Eggemann
2020-03-05 12:33 ` Vincent Guittot
2020-03-05 12:48 ` Christian Borntraeger
2020-03-05 13:02 ` Vincent Guittot
2020-03-05 13:18 ` Christian Borntraeger
2020-03-05 12:14 ` Vincent Guittot
2020-03-05 11:54 ` Dietmar Eggemann
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=20200228163545.GA18662@vingu-book \
--to=vincent.guittot@linaro.org \
--cc=borntraeger@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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