From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Jani Nikula <jani.nikula@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: BUG: sleeping function called from invalid context at drivers/gpu/drm/i915/gem/i915_gem_pages.c:526
Date: Mon, 25 Mar 2024 19:30:06 +0200 [thread overview]
Message-ID: <ZgG0niB5wBxkWBkR@intel.com> (raw)
In-Reply-To: <ZgGsVBnpme-syWCG@intel.com>
On Mon, Mar 25, 2024 at 06:54:44PM +0200, Ville Syrjälä wrote:
> On Mon, Mar 25, 2024 at 05:33:42PM +0100, Borislav Petkov wrote:
> > On Tue, Feb 27, 2024 at 12:58:08PM +0200, Jani Nikula wrote:
> > > Let's see what Ville says, but in the end bisection might be the
> > > quickest way to find the regression. Though I understand it can be
> > > tedious for you personally.
> >
> > That still fires with 6.-9-rc1. Does Ville have any suggestions or
> > should I bisect?
>
> Sorry, completely missed this. The culprit is going to be
> commit 1de63528e728 ("drm/i915: Perform vblank evasion around legacy
> cursor updates")
Hmm. Actually should be commit 0225a90981c8 ("drm/i915: Make
cursor plane registers unlocked") already.
Apprently I had CONFIG_DEBUG_ATOMIC_SLEEP=n in my config
for most of my old machines.
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2024-03-25 17:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 10:03 BUG: sleeping function called from invalid context at drivers/gpu/drm/i915/gem/i915_gem_pages.c:526 Borislav Petkov
2024-02-27 10:37 ` Jani Nikula
2024-02-27 10:53 ` Borislav Petkov
2024-02-27 10:58 ` Jani Nikula
2024-02-27 11:13 ` Borislav Petkov
2024-03-25 16:33 ` Borislav Petkov
2024-03-25 16:54 ` Ville Syrjälä
2024-03-25 17:30 ` Ville Syrjälä [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=ZgG0niB5wBxkWBkR@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@gmail.com \
--cc=bp@alien8.de \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=tvrtko.ursulin@linux.intel.com \
/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.