From: Heiner Kallweit <hkallweit1@gmail.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: "Peter Zijlstra (Intel)" <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problem with commit 31e77c93e432 "sched/fair: Update blocked load when newly idle"
Date: Sat, 24 Mar 2018 13:47:13 +0100 [thread overview]
Message-ID: <c5daea3c-0834-1629-3e38-3db5130eb32f@gmail.com> (raw)
In-Reply-To: <20180324064627.GA10884@linaro.org>
Am 24.03.2018 um 07:46 schrieb Vincent Guittot:
> Hi Heiner,
>
> Le Friday 23 Mar 2018 à 22:28:09 (+0100), Heiner Kallweit a écrit :
>> Recently I started to get the following problems with linux-next:
>>
>> - When working via Putty/SSH on the system the console frequently freezes
>> for few seconds. Sometimes only opening a second console makes the
>> first one react again.
>>
>> - I get "INFO: rcu_sched detected stalls on CPUs/tasks:" warnings as
>> described in [1].
>>
>> Bisecting the issue resulted in:
>>
>> 31e77c93e432dec79c7d90b888bbfc3652592741 is the first bad commit
>> commit 31e77c93e432dec79c7d90b888bbfc3652592741
>> Author: Vincent Guittot <vincent.guittot@linaro.org>
>> Date: Wed Feb 14 16:26:46 2018 +0100
>>
>> sched/fair: Update blocked load when newly idle
>>
>> When NEWLY_IDLE load balance is not triggered, we might need to update the
>> blocked load anyway. We can kick an ilb so an idle CPU will take care of
>> updating blocked load or we can try to update them locally before entering
>> idle. In the latter case, we reuse part of the nohz_idle_balance.
>>
>> After reversing this commit at least the issue with the freezing console
>> is gone. The second one appeared only sporadically, I still have to see
>> whether it pops up again.
>>
>
> Can you check if the change below fix the problem ?
>
Thanks for the quick feedback. The change however didn't fix the probem, I didn't
notice any changed behavior.
> ---
> kernel/sched/fair.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 3582117..672f212 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -9430,6 +9430,9 @@ static bool _nohz_idle_balance(struct rq *this_rq, unsigned int flags,
>
> has_blocked_load |= update_nohz_stats(rq, true);
>
> + if (flags == NOHZ_STATS_KICK)
> + continue;
> +
> /*
> * If time for next balance is due,
> * do the balance.
>
next prev parent reply other threads:[~2018-03-24 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 21:28 Heiner Kallweit
2018-03-24 6:46 ` Vincent Guittot
2018-03-24 12:47 ` Heiner Kallweit [this message]
2018-03-28 10:37 ` Dietmar Eggemann
2018-03-28 14:01 ` Vincent Guittot
2018-03-29 7:41 ` Vincent Guittot
2018-03-29 17:40 ` Heiner Kallweit
2018-03-30 6:50 ` Vincent Guittot
2018-03-30 8:37 ` Heiner Kallweit
2018-04-06 16:03 ` Vincent Guittot
2018-04-06 19:53 ` Heiner Kallweit
2018-04-09 17:33 ` Heiner Kallweit
2018-04-11 17:00 ` Vincent Guittot
2018-04-11 20:35 ` Heiner Kallweit
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=c5daea3c-0834-1629-3e38-3db5130eb32f@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome