From: Jani Nikula <jani.nikula@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: maarten.lankhorst@linux.intel.com, ville.syrjala@linux.intel.com
Subject: Re: [PATCH 4/4] drm/i915/display: use fixed 10 second timeout for fence wait
Date: Thu, 27 Aug 2026 15:36:34 +0300 [thread overview]
Message-ID: <d6d85707e57f06d7980bd46a7e36c26a25450ddf@intel.com> (raw)
In-Reply-To: <859cb981-4039-4f0e-801f-c9f8cd630ded@intel.com>
On Fri, 21 Aug 2026, Maarten Lankhorst <maarten.lankhorst@intel.com> wrote:
> Not waiting on fences until they're signaled is an existing issue in
> i915, and was added as a workaround for a deadlock when GPU reset has
> to reset display as well on old platforms. This requires a modeset to
> disable everything, which may hang since it could wait on a fence that
> may only be signaled after gpu reset completes.
Thanks, I've used this verbatim in my v2 commit message. ;)
> Can you test if gpu_reset_clobbers_display and
> force_reset_modeset_test are set, and if not set the timeout to
> infinity on i915 as well?
v2 at [2], fingers crossed.
BR,
Jani.
[1] https://lore.kernel.org/r/cover.1787833879.git.jani.nikula@intel.com
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-08-27 12:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 14:05 [PATCH 0/4] drm/{i915, xe}/display: another stab at i915_fence_timeout() removal Jani Nikula
2026-08-19 14:05 ` [PATCH 1/4] drm/i915/display: use struct intel_atomic_state *state variable naming Jani Nikula
2026-08-19 14:05 ` [PATCH 2/4] drm/i915/display: reduce indent in intel_atomic_commit_fence_wait() Jani Nikula
2026-08-19 14:05 ` [PATCH 3/4] drm/i915/display: debug log about fence wait timeouts and other errors Jani Nikula
2026-08-19 14:05 ` [PATCH 4/4] drm/i915/display: use fixed 10 second timeout for fence wait Jani Nikula
2026-08-21 16:05 ` Maarten Lankhorst
2026-08-27 12:36 ` Jani Nikula [this message]
2026-08-19 14:11 ` ✗ CI.checkpatch: warning for drm/{i915, xe}/display: another stab at i915_fence_timeout() removal Patchwork
2026-08-19 14:12 ` ✓ CI.KUnit: success " Patchwork
2026-08-19 15:09 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-19 17:04 ` ✗ Xe.CI.FULL: failure " Patchwork
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=d6d85707e57f06d7980bd46a7e36c26a25450ddf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=ville.syrjala@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