From: Mike Galbraith <efault@gmx.de>
To: Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: v5.14-rc3-rt1 losing wakeups?
Date: Sat, 31 Jul 2021 03:03:05 +0200 [thread overview]
Message-ID: <a2cd339c0e440cb5beed788d66a19a636b2e39a1.camel@gmx.de> (raw)
In-Reply-To: <87pmuzsf1p.ffs@tglx>
On Fri, 2021-07-30 at 22:49 +0200, Thomas Gleixner wrote:
> >
> > First symptom is KDE/Plasma's task manager going comatose. Notice soon
>
> KDE/Plasma points at the new fangled rtmutex based ww_mutex from
> Peter.
Yeah, that seems to be most of the delta from 50->62 [now 63] commit
delta, and the 50 turning out to be what I was already running. I'm
staring, but as yet, nothing has poked me in the eye.
> I tried to test the heck out of it...
And futextests, rt-tests etc work fine, just stay away from GUI.
> Which graphics driver is in use on that machine?
The all too often problem child nouveau, but I don't _think_ it's
playing a roll in this, as nomodeset hangs as well. I'll stuff it into
lappy (i915) to double check that.
-Mike
next prev parent reply other threads:[~2021-07-31 1:04 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 ` v5.14-rc3-rt1 losing wakeups? Mike Galbraith
2021-07-30 20:49 ` Thomas Gleixner
2021-07-31 1:03 ` Mike Galbraith [this message]
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=a2cd339c0e440cb5beed788d66a19a636b2e39a1.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=peterz@infradead.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).