LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	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: Mon, 02 Aug 2021 09:18:34 +0200	[thread overview]
Message-ID: <edd2f9fd1489e1ff05bf526a3059a1dbb81107df.camel@gmx.de> (raw)
In-Reply-To: <20210802070218.5js3exubjxvsicx6@linutronix.de>

On Mon, 2021-08-02 at 09:02 +0200, Sebastian Andrzej Siewior wrote:
> On 2021-08-01 17:14:49 [+0200], Mike Galbraith wrote:
> > On Sun, 2021-08-01 at 05:36 +0200, Mike Galbraith wrote:
> > > 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.
> > >
> > > Seems not.  When booting KVM box with nomodeset, there's exactly one
> > > early boot ww_mutex lock/unlock, ancient history at the failure point.
> >
> > As you've probably already surmised given it isn't the ww_mutex bits,
> > it's the wake_q bits.  Apply the below, 5.14-rt ceases to fail.  Take
> > perfectly healthy 5.13-rt, apply those bits, and it instantly begins
> > failing as 5.14-rt had been.
>
> Given what you have replied to the locking thread/
> ww_mutex_lock_interruptible() may I assume that the wake_q bits are fine
> and it is just the ww_mutex?

Nope.  Before I even reverted the wake_q bits, I assembled a tree with
the ww_mutex changes completely removed to be absolutely certain that
they were innocent, and it indeed did retain its lost wakeup woes
despite complete loss of newfangled ww_mutex.  5.13-rt acquired those
same wakeup woes by receiving ONLY the wake_q bits, and 5.14-rt was
cured of those woes by ONLY them being reverted. I'm not seeing the
why, but those bits are either the source or the trigger of 5.14-rt
lost wakeup woes... they're toxic in some way shape fashion or form.

	-Mike


  reply	other threads:[~2021-08-02  7:19 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
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 [this message]
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=edd2f9fd1489e1ff05bf526a3059a1dbb81107df.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 \
    --subject='Re: v5.14-rc3-rt1 losing wakeups?' \
    /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

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).