From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [BUG] stress-ng close causes kernel oops(es) v5.6-rt and v5.4-rt
Date: Fri, 14 Aug 2020 13:41:32 +0200 [thread overview]
Message-ID: <20200814114132.rq7ygkexdqn5aqgg@linutronix.de> (raw)
In-Reply-To: <20200810133639.GA59705@localhost.localdomain>
On 2020-08-10 15:36:39 [+0200], Juri Lelli wrote:
> Hi,
Hi,
> As per subject, the following test
>
> # stress-ng --close 0 --verbose --timeout 60 --metrics-brief
>
> Causes kernel crashes for both v5.6.19-rt11 and v5.4.28-rt19 (splats
> follow). Will try to dig deeper, but wanted to report early as this
> seems to be very easy to reproduce and maybe someone already saw it and
> might have suggestions.
>
kvm:
|stress-ng: info: [2067] successful run completed in 60.03s (1 min, 0.03 secs)
|stress-ng: info: [2067] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s
|stress-ng: info: [2067] (secs) (secs) (secs) (real time) (usr+sys time)
|stress-ng: info: [2067] close 903449 60.02 22.68 182.01 15053.52 4413.74
real HW, no debug:
|stress-ng: info: [50376] successful run completed in 60.01s (1 min, 0.01 secs)
|stress-ng: info: [50376] stressor bogo ops real time usr time sys time bogo ops/s bogo ops/s
|stress-ng: info: [50376] (secs) (secs) (secs) (real time) (usr+sys time)
|stress-ng: info: [50376] close 9937122 60.00 129.59 352.74 165614.20 20602.33
Can you reproduce this in kvm and send me a .config? As of now I can't
reproduce it.
> Juri
Sebastian
prev parent reply other threads:[~2020-08-14 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 13:36 [BUG] stress-ng close causes kernel oops(es) v5.6-rt and v5.4-rt Juri Lelli
2020-08-14 11:41 ` Sebastian Andrzej Siewior [this message]
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=20200814114132.rq7ygkexdqn5aqgg@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=juri.lelli@redhat.com \
--cc=linux-rt-users@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).