rcu.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt.kanzenbach@linutronix.de>
To: Vladimir Oltean <olteanv@gmail.com>,
	linux-rt-users@vger.kernel.org,
	lkml <linux-kernel@vger.kernel.org>,
	rcu@vger.kernel.org
Cc: Colin King <colin.king@canonical.com>
Subject: Re: stress-ng --hrtimers hangs system
Date: Fri, 05 Jun 2020 14:57:06 +0200	[thread overview]
Message-ID: <87wo4lekm5.fsf@kurt> (raw)
In-Reply-To: <4781d250-9a29-cef3-268d-7d83c98bf16a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Hi Vladimir,

On Fri Jun 05 2020, Vladimir Oltean wrote:
> Hi,
>
> I was testing stress-ng on an ARM64 box and I found that it can be killed instantaneously with a --hrtimers 1 test:
> https://github.com/ColinIanKing/stress-ng/blob/master/stress-hrtimers.c
> The console shell locks up immediately after starting the process, and I get this rcu_preempt splat after 21 seconds,
> letting me know that the grace-periods kernel thread could not run:

interesting. Just tested this on an ARM64 box with v5.6-rt and the
stress-ng hrtimer test works fine. No lockups, cyclictest results are
looking good. So maybe this is v5.7 related.

Thanks,
Kurt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2020-06-05 12:57 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 [this message]
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
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=87wo4lekm5.fsf@kurt \
    --to=kurt.kanzenbach@linutronix.de \
    --cc=colin.king@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --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).