From: Martin Kepplinger <martink@posteo.de>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
daniel.vetter@intel.com, Dave Airlie <airlied@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/5] Re: [Intel-gfx] [BUG][REGRESSION] i915 gpu hangs under load
Date: Mon, 10 Apr 2017 12:15:34 +0200 [thread overview]
Message-ID: <3c3dd67ba55d13893c3d264e23710085@posteo.de> (raw)
In-Reply-To: <20170406232347.988-1-aarcange@redhat.com>
Am 07.04.2017 01:23 schrieb Andrea Arcangeli:
> I'm also getting kernel hangs every couple of days. For me it's still
> not fixed here in 4.11-rc5. It's hard to reproduce, the best
> reproducer is to build lineageos 14.1 on host while running LTP in a
> guest to stress the guest VM.
>
> Initially I thought it was related to the fact I upgraded the xf86
> intel driver just a few weeks ago (I deferred any upgrade of the
> userland intel driver since last July because of a regression that
> never got fixed and broke xterm for me). After I found a workaround
> for the userland regression (appended at the end for reference) I
> started getting kernel hangs but they are separate issues as far as I
> can tell.
>
> It's not well tested so beware... (it survived a couple of builds and
> some VM reclaim but that's it).
>
> The first patch 1/5 is the potential fix for the i915 kernel hang. The
> rest are incremental improvements.
>
> And I've no great solution for when the shrinker was invoked with the
> struct_mutex held and and recurse on the lock. I don't think we can
> possibly wait in such case (other than flush work that the second
> patch does) but then practically it shouldn't be a big deal, the big
> RAM eater is unlikely to be i915 when the system is low on memory.
>
FWIW without having insight here, -rc6 seems to be good.
No disturbing gpu hangs under load so far.
prev parent reply other threads:[~2017-04-10 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 8:38 Martin Kepplinger
2017-03-22 10:36 ` [Intel-gfx] " Jani Nikula
2017-04-02 11:50 ` Thorsten Leemhuis
2017-04-02 12:13 ` Martin Kepplinger
2017-04-03 15:09 ` Jani Nikula
2017-04-06 23:23 ` [PATCH 0/5] " Andrea Arcangeli
2017-04-06 23:23 ` [PATCH 1/5] i915: avoid kernel hang caused by synchronize rcu struct_mutex deadlock Andrea Arcangeli
2017-04-07 9:05 ` [Intel-gfx] " Joonas Lahtinen
2017-04-06 23:23 ` [PATCH 2/5] i915: flush gem obj freeing workqueues to add accuracy to the i915 shrinker Andrea Arcangeli
2017-04-07 10:02 ` Chris Wilson
2017-04-07 13:06 ` Andrea Arcangeli
2017-04-07 15:30 ` Chris Wilson
2017-04-07 16:48 ` Andrea Arcangeli
2017-04-10 9:39 ` Chris Wilson
2017-04-06 23:23 ` [PATCH 3/5] i915: initialize the free_list of the fencing atomic_helper Andrea Arcangeli
2017-04-07 10:35 ` Chris Wilson
2017-04-06 23:23 ` [PATCH 4/5] i915: schedule while freeing the lists of gem objects Andrea Arcangeli
2017-04-06 23:23 ` [PATCH 5/5] i915: fence workqueue optimization Andrea Arcangeli
2017-04-07 9:58 ` Chris Wilson
2017-04-07 13:13 ` Andrea Arcangeli
2017-04-10 10:15 ` Martin Kepplinger [this message]
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=3c3dd67ba55d13893c3d264e23710085@posteo.de \
--to=martink@posteo.de \
--cc=aarcange@redhat.com \
--cc=airlied@gmail.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
/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
Powered by JetHome