From: Leho Kraav <leho@kraav.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
Martin Wilck <Martin.Wilck@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 5.3-rc3: Frozen graphics with kcompactd migrating i915 pages
Date: Tue, 10 Sep 2019 17:20:47 +0300 [thread overview]
Message-ID: <20190910142047.GB3029@papaya> (raw)
In-Reply-To: <156535522344.29541.9312856809559678262@skylake-alporthouse-com>
On Fri, Aug 09, 2019 at 01:53:43PM +0100, Chris Wilson wrote:
> Quoting Martin Wilck (2019-08-09 13:41:42)
> > This happened to me today, running kernel 5.3.0-rc3-1.g571863b-default
> > (5.3-rc3 with just a few patches on top), after starting a KVM virtual
> > machine. The X screen was frozen. Remote login via ssh was still
> > possible, thus I was able to retrieve basic logs.
> >
> > sysrq-w showed two blocked processes (kcompactd0 and KVM). After a
> > minute, the same two processes were still blocked. KVM seems to try to
> > acquire a lock that kcompactd is holding. kcompactd is waiting for IO
> > to complete on pages owned by the i915 driver.
>
> My bad, it's known. We haven't decided on whether to revert the
> unfortunate recursive locking (and so hit another warn elsewhere) or to
> ignore the dirty pages (and so risk losing data across swap).
>
> cb6d7c7dc7ff ("drm/i915/userptr: Acquire the page lock around set_page_dirty()")
> -Chris
Hi Chris. Is this exactly what I'm hitting at
https://bugs.freedesktop.org/show_bug.cgi?id=111500 perhaps?
It reliably breaks the graphics userland, as the machine consistently
freezes at any random moment.
Any workaround options, even if with a performance penalty? Revert
cb6d7c7dc7ff but side effects?
5.3 has useful NVMe power mgmt updates for laptops, I'd like to stick
with the newest if possible.
--
Leho Kraav, senior technology & digital marketing architect
next prev parent reply other threads:[~2019-09-10 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 12:41 5.3-rc3: Frozen graphics with kcompactd migrating i915 pages Martin Wilck
2019-08-09 12:53 ` Chris Wilson
2019-09-10 14:20 ` Leho Kraav [this message]
2019-09-12 11:23 ` Martin Wilck
2019-09-12 11:58 ` leho
2019-09-12 11:59 ` Linus Torvalds
2019-09-12 12:47 ` Chris Wilson
2019-09-12 12:56 ` [PATCH] Revert "drm/i915/userptr: Acquire the page lock around set_page_dirty()" Chris Wilson
2019-09-12 14:39 ` [Intel-gfx] " Tvrtko Ursulin
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=20190910142047.GB3029@papaya \
--to=leho@kraav.com \
--cc=Martin.Wilck@suse.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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).