From: Mike Galbraith <efault@gmx.de>
To: Clark Williams <williams@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Vlastimil Babka <vbabka@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] v5.14-rc5-rt8
Date: Sat, 14 Aug 2021 07:33:48 +0200 [thread overview]
Message-ID: <522000b97adcfbc581e7e5ed1afc94519b1388b8.camel@gmx.de> (raw)
In-Reply-To: <8c012c35852e98af99a6b6234a3f57ac27cd980a.camel@gmx.de>
On Fri, 2021-08-13 at 12:56 +0200, Mike Galbraith wrote:
> On Thu, 2021-08-12 at 15:18 -0500, Clark Williams wrote:
> >
> > Sebastian, et al,
> >
> > Got the following panic running v5.14-rc5-rt8:
> >
> > ...
>
> > Config is attached.
> >
> > I was running the rteval script that kicks off parallel kernel builds
> > and hackbench runs as loads and runs cyclictest with a thread on each
> > core:
> >
> > $ sudo rteval --duration=10m
>
> It took my box more than 10 minutes to explode, but with all those
> debug options turned on, it did manage to do so in fairly short order.
>
> Off to build a fixed up 5.13-rt...
...and it reproduced. Transplanted 5.12-rt slub seems stable in both
5.1[34]-rt trees FWIW.
-Mike
next prev parent reply other threads:[~2021-08-14 5:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 16:37 [ANNOUNCE] v5.14-rc5-rt8 Sebastian Andrzej Siewior
2021-08-12 20:18 ` Clark Williams
2021-08-12 20:45 ` Vlastimil Babka
2021-08-12 21:24 ` Clark Williams
2021-08-12 21:30 ` Vlastimil Babka
2021-08-12 21:44 ` Clark Williams
2021-08-14 19:08 ` Vlastimil Babka
2021-08-15 3:13 ` Mike Galbraith
2021-08-15 9:01 ` Mike Galbraith
2021-08-15 4:17 ` Mike Galbraith
2021-08-15 9:35 ` Vlastimil Babka
2021-08-15 13:03 ` Mike Galbraith
2021-08-12 21:36 ` Vlastimil Babka
2021-08-12 21:47 ` Clark Williams
2021-08-13 10:56 ` Mike Galbraith
2021-08-14 5:33 ` Mike Galbraith [this message]
2021-08-14 18:28 ` Vlastimil Babka
2021-08-15 1:26 ` Mike Galbraith
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=522000b97adcfbc581e7e5ed1afc94519b1388b8.camel@gmx.de \
--to=efault@gmx.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.