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 10:50:51 +0200 [thread overview]
Message-ID: <9e2492721004fb98b144ec61002b2d525ac2c0d6.camel@gmx.de> (raw)
In-Reply-To: <4fb6dc706d0fdde718943b48b1d564ec12c97f03.camel@gmx.de>
On Sat, 2021-07-31 at 05:33 +0200, Mike Galbraith wrote:
> On Sat, 2021-07-31 at 03:03 +0200, Mike Galbraith wrote:
> > On Fri, 2021-07-30 at 22:49 +0200, Thomas Gleixner wrote:
> > >
> >
> > > 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.
>
> Hm, lappy doesn't seem to want to hang. i915 isn't virgin, it needing
> a couple bandaids, but I doubt my grubby fingerprints matter.
Hours later i915 lappy is still working fine.
The problem is not my nvidia/nouveau desktop box. Taking KVM images
over to lappy on a USB SSD, the same QXL vbox that hangs with desktop
box as host also hangs with lappy as host.. a host that's still running
the very same kernel, the same build in fact (all instances are), just
fine.
-Mike
next prev parent reply other threads:[~2021-07-31 8:51 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 [this message]
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=9e2492721004fb98b144ec61002b2d525ac2c0d6.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 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.