rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
Cc: linux-rt-users@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>,
	rcu@vger.kernel.org, Colin King <colin.king@canonical.com>
Subject: Re: stress-ng --hrtimers hangs system
Date: Wed, 10 Jun 2020 17:37:22 +0300	[thread overview]
Message-ID: <CA+h21hp8ANbZw63UAy5cDx389j6pSOHUG7t1mR+rbQcrFLROyw@mail.gmail.com> (raw)
In-Reply-To: <87y2ovzcmd.fsf@kurt>

Hi Kurt,

On Wed, 10 Jun 2020 at 08:58, Kurt Kanzenbach
<kurt.kanzenbach@linutronix.de> wrote:
>
> Hi Vladimir,
>
> On Tue Jun 09 2020, Vladimir Oltean wrote:
> > Just out of curiosity, what and how many CPU cores does your ARM64 box
> > have, and what frequency are you running them at?
> > Mine is a dual-core A72 machine running at 1500 MHz.
>
> That particular machine has a dual core Cortex A53 running at 1GHz.
>
> Thanks,
> Kurt

Ok, I just noticed that you said "v5.6*-rt*".
So I re-tested that 5.4 downstream kernel again that hanged before,
just applied the -rt1 patchset on top. And it's actually working fine
now, no hangs, no RCU stalls, no need to reduce sched_rt_runtime_us.
So maybe it's something related to the config?

Thanks,
-Vladimir

  reply	other threads:[~2020-06-10 14:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-05  1:47 stress-ng --hrtimers hangs system Vladimir Oltean
2020-06-05  3:20 ` Paul E. McKenney
2020-06-05 10:12   ` Vladimir Oltean
2020-06-05 12:57 ` Kurt Kanzenbach
2020-06-05 13:19   ` Vladimir Oltean
2020-06-09 16:37     ` Vladimir Oltean
2020-06-10  5:57       ` Kurt Kanzenbach
2020-06-10 14:37         ` Vladimir Oltean [this message]
2020-06-12  0:49         ` [EXT] " Jiafei Pan
2020-06-20  8:08           ` Kurt Kanzenbach
2020-06-22  2:30             ` Jiafei Pan

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=CA+h21hp8ANbZw63UAy5cDx389j6pSOHUG7t1mR+rbQcrFLROyw@mail.gmail.com \
    --to=olteanv@gmail.com \
    --cc=colin.king@canonical.com \
    --cc=kurt.kanzenbach@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rcu@vger.kernel.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).