From: Matthew Brost <matthew.brost@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Hugh Dickins <hughd@google.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: fix blank screen booting crashes
Date: Mon, 20 Sep 2021 13:25:57 -0700 [thread overview]
Message-ID: <20210920202557.GA19283@jons-linux-dev-box> (raw)
In-Reply-To: <8c906ac4-c6a3-ee45-970f-07679456fd18@linux.intel.com>
On Mon, Sep 20, 2021 at 08:28:13AM +0100, Tvrtko Ursulin wrote:
>
> On 18/09/2021 00:38, Matthew Brost wrote:
> > From: Hugh Dickins <hughd@google.com>
> >
> > 5.15-rc1 crashes with blank screen when booting up on two ThinkPads
> > using i915. Bisections converge convincingly, but arrive at different
> > and surprising "culprits", none of them the actual culprit.
>
> It is certainly surprising this patch crashed SNB and KBL.
>
> How feasible would it be to make this code just not run when GuC is not
> used? Given the field it adds is called ce->guc_blocked it sounds like a
> natural and preferable thing to do... if possible.
>
I can likely do this in a follow up patch.
> > netconsole (with init_netconsole() hacked to call i915_init() when
> > logging has started, instead of by module_init()) tells the story:
> >
> > kernel BUG at drivers/gpu/drm/i915/i915_sw_fence.c:245!
> > with RSI: ffffffff814d408b pointing to sw_fence_dummy_notify().
> > I've been building with CONFIG_CC_OPTIMIZE_FOR_SIZE=y, and that
> > function needs to be 4-byte aligned.
> >
> > v2:
> > (Jani Nikula)
> > - Change BUG_ON to WARN_ON
>
> However in this case the code would then go on and call into a wrong
> function offset which may be worse than a BUG_ON, no?
>
Yea, I guess that would be bad too.
> >
> > Fixes: 62eaf0ae217d ("drm/i915/guc: Support request cancellation")
> > Signed-off-by: Hugh Dickins <hughd@google.com>
> > Signed-off-by: Matthew Brost <matthew.brost@intel.com>
> > Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/intel_context.c | 1 +
> > drivers/gpu/drm/i915/i915_sw_fence.c | 4 +++-
> > 2 files changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_context.c b/drivers/gpu/drm/i915/gt/intel_context.c
> > index ff637147b1a9..f02c2202da9d 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_context.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_context.c
> > @@ -362,6 +362,7 @@ static int __intel_context_active(struct i915_active *active)
> > return 0;
> > }
> > +__aligned(4) /* Respect the I915_SW_FENCE_MASK */
>
> Hugh suggested __i915_sw_fence_call which I think would be the right thing
> to do.
>
Yep. Will do.
Matt
> Regards,
>
> Tvrtko
>
> > static int sw_fence_dummy_notify(struct i915_sw_fence *sf,
> > enum i915_sw_fence_notify state)
> > {
> > diff --git a/drivers/gpu/drm/i915/i915_sw_fence.c b/drivers/gpu/drm/i915/i915_sw_fence.c
> > index c589a681da77..1217b124c1d0 100644
> > --- a/drivers/gpu/drm/i915/i915_sw_fence.c
> > +++ b/drivers/gpu/drm/i915/i915_sw_fence.c
> > @@ -14,8 +14,10 @@
> > #if IS_ENABLED(CONFIG_DRM_I915_DEBUG)
> > #define I915_SW_FENCE_BUG_ON(expr) BUG_ON(expr)
> > +#define I915_SW_FENCE_WARN_ON(expr) WARN_ON(expr)
> > #else
> > #define I915_SW_FENCE_BUG_ON(expr) BUILD_BUG_ON_INVALID(expr)
> > +#define I915_SW_FENCE_WARN_ON(expr) BUILD_BUG_ON_INVALID(expr)
> > #endif
> > static DEFINE_SPINLOCK(i915_sw_fence_lock);
> > @@ -242,7 +244,7 @@ void __i915_sw_fence_init(struct i915_sw_fence *fence,
> > const char *name,
> > struct lock_class_key *key)
> > {
> > - BUG_ON(!fn || (unsigned long)fn & ~I915_SW_FENCE_MASK);
> > + I915_SW_FENCE_WARN_ON(!fn || (unsigned long)fn & ~I915_SW_FENCE_MASK);
> > __init_waitqueue_head(&fence->wait, name, key);
> > fence->flags = (unsigned long)fn;
> >
next prev parent reply other threads:[~2021-09-20 20:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 23:38 [Intel-gfx] [PATCH] drm/i915: fix blank screen booting crashes Matthew Brost
2021-09-18 1:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: fix blank screen booting crashes (rev2) Patchwork
2021-09-18 2:36 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-09-20 7:28 ` [Intel-gfx] [PATCH] drm/i915: fix blank screen booting crashes Tvrtko Ursulin
2021-09-20 7:38 ` Jani Nikula
2021-09-20 7:42 ` Tvrtko Ursulin
2021-09-20 20:29 ` Matthew Brost
2021-09-20 20:25 ` Matthew Brost [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-22 1:50 Matthew Brost
2021-09-24 12:16 ` Ville Syrjälä
2021-10-04 7:36 ` Jani Nikula
2021-10-15 14:52 ` Tvrtko Ursulin
2021-10-15 15:42 ` John Harrison
2021-10-15 15:55 ` Jani Nikula
2021-09-21 17:43 Matthew Brost
2021-09-21 18:46 ` Lucas De Marchi
2021-09-21 22:55 ` Matthew Brost
2021-09-21 23:29 ` Lucas De Marchi
2021-09-22 1:40 ` Matthew Brost
2021-09-22 21:37 ` Lucas De Marchi
2021-09-17 23:38 Matthew Brost
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=20210920202557.GA19283@jons-linux-dev-box \
--to=matthew.brost@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hughd@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox