From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Subject: v5.14-rc3-rt1 losing wakeups?
Date: Fri, 30 Jul 2021 17:21:53 +0200 [thread overview]
Message-ID: <2ae27233ab091d09a7d1e971a47144b40dd51fa0.camel@gmx.de> (raw)
In-Reply-To: <20210730110753.jvli6alm63h5lefy@linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Fri, 2021-07-30 at 13:07 +0200, Sebastian Andrzej Siewior wrote:
> Dear RT folks!
>
> I'm pleased to announce the v5.14-rc3-rt1 patch set.
Damn, I was hoping to figure out wth is going on before the 62 patch
version of tglx/rtmutex branch made its way out into the big wide
world, but alas, I was too slow.
I started meeting GUI hangs as soon as I merged the 62 patch series
into my 5.13-rt based master tree. I took tglx/rtmutex (977db8e523f5)
back to 5.13-rt to make sure it wasn't some booboo I had made in the
rolled forward tree, but the hangs followed the backport, and I just
met them in virgin v5.14-rc3-rt1, so unfortunately it wasn't some local
booboo, there's a bug lurking. Maybe a config sensitive one, as what
I'm seeing on my box seems unlikely to escape into the wild otherwise.
First symptom is KDE/Plasma's task manager going comatose. Notice soon
enough with a !lockdep kernel, and I can crashdump, or rather I can
with my 5.13-rt based kernel, a dump from shiny new rt1 can't be loaded
by crash for some reason. The local tree dumps I've looked at haven't
been helpful anyway, box at a glance looks fine. With lockdep enabled,
a failing kernel gets so buggered it isn't even able to crashdump.
config attached. Oh, a lockdep enabled kernel fails sooner, but both
fail here fairly quickly.
-Mike
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 39257 bytes --]
next prev parent reply other threads:[~2021-07-30 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 11:07 [ANNOUNCE] v5.14-rc3-rt1 Sebastian Andrzej Siewior
2021-07-30 15:21 ` Mike Galbraith [this message]
2021-07-30 20:49 ` v5.14-rc3-rt1 losing wakeups? Thomas Gleixner
2021-07-31 1:03 ` Mike Galbraith
2021-07-31 3:33 ` Mike Galbraith
2021-07-31 8:50 ` Mike Galbraith
2021-08-01 3:36 ` Mike Galbraith
2021-08-01 15:14 ` Mike Galbraith
2021-08-02 7:02 ` Sebastian Andrzej Siewior
2021-08-02 7:18 ` Mike Galbraith
2021-08-02 8:25 ` Sebastian Andrzej Siewior
2021-08-02 8:40 ` Mike Galbraith
2021-08-02 9:12 ` Thomas Gleixner
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=2ae27233ab091d09a7d1e971a47144b40dd51fa0.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=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).