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: Wed, 4 Mar 2020 16:26:15 +0100 [thread overview]
Message-ID: <CAKfTPtD9b6o=B6jkbWNjfAw9e1UjT9Z07vxdsVfikEQdeCtfPw@mail.gmail.com> (raw)
In-Reply-To: <CAKfTPtCX4padfJm8aLrP9+b5KVgp-ff76=teu7MzMZJBYrc-7w@mail.gmail.com>
On Tue, 3 Mar 2020 at 08:55, Vincent Guittot <vincent.guittot@linaro.org> wrote:
>
> On Tue, 3 Mar 2020 at 08:37, Christian Borntraeger
> <borntraeger@de.ibm.com> wrote:
> >
> >
> >
[...]
> > >>> ---
> > >>> 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);
> > >>> }
> > >>> }
> > >>
> > >> Now running for 3 hours. I have not seen the issue yet. I can tell tomorrow if this fixes
> > >> the issue.
> > >
> > >
> > > Still running fine. I can tell for sure tomorrow, but I have the impression that this makes the
> > > WARN_ON go away.
> >
> > So I guess this change "fixed" the issue. If you want me to test additional patches, let me know.
>
> Thanks for the test. For now, I don't have any other patch to test. I
> have to look more deeply how the situation happens.
> I will let you know if I have other patch to test
So I haven't been able to figure out how we reach this situation yet.
In the meantime I'm going to make a clean patch with the fix above.
Is it ok if I add a reported -by and a tested-by you ?
>
> >
next prev parent reply other threads:[~2020-03-04 15:26 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
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 [this message]
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='CAKfTPtD9b6o=B6jkbWNjfAw9e1UjT9Z07vxdsVfikEQdeCtfPw@mail.gmail.com' \
--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;
as well as URLs for NNTP newsgroup(s).