From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <ville.syrjala@linux.intel.com>
Subject: Re: ✗ i915.CI.BAT: failure for drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification, part 2
Date: Wed, 3 Jun 2026 17:24:57 +0300 [thread overview]
Message-ID: <aiA5ORKjPPJlwYcM@ideak-desk.lan> (raw)
In-Reply-To: <05a8062a90d7746e9c4d693601a407b157ce1d22@intel.com>
On Wed, Jun 03, 2026 at 04:29:19PM +0300, Jani Nikula wrote:
> On Tue, 02 Jun 2026, Jani Nikula <jani.nikula@intel.com> wrote:
> > On Tue, 02 Jun 2026, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> >> #### Possible regressions ####
> >>
> >> * igt@i915_selftest@live:
> >> - fi-bsw-n3050: [PASS][1] -> [ABORT][2] +1 other test abort
> >> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18602/fi-bsw-n3050/igt@i915_selftest@live.html
> >> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_167725v1/fi-bsw-n3050/igt@i915_selftest@live.html
> >>
> >> * igt@i915_selftest@live@hangcheck:
> >> - bat-arlh-2: [PASS][3] -> [INCOMPLETE][4]
> >> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_18602/bat-arlh-2/igt@i915_selftest@live@hangcheck.html
> >> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_167725v1/bat-arlh-2/igt@i915_selftest@live@hangcheck.html
> >
> > Imre, Ville, any idea what in this series could cause this? Feels like
> > it could be a real regression, but I can't figure it out. :(
>
> Passed on the next try. I'll optimistically think the first try was a
> fluke. ;)
The Oops in __drm_mm_interval_first() on fi-bsw-n3050 looks like an
actual driver problem, unless it's a random memory corruption due to HW
errors. I couldn't find any previous instance of this Oops in CI runs,
but I also can't see how it would relate to the changes in this
patchset. Since these selftests involve a lot unloading/reloading of the
driver one theory was that it's due to unproper unloading of the driver
after the test preceeding the above igt@i915_selftest@live test
(gem_migrate), but couldn't see any proof for that either and not sure
how such an issue would cause a memory corruption in the reloaded driver
like the above.
> BR,
> Jani.
>
> --
> Jani Nikula, Intel
next prev parent reply other threads:[~2026-06-03 14:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:32 [CI 00/12] drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification, part 2 Jani Nikula
2026-06-02 8:32 ` [CI 01/12] drm/i915/display: add "pm" to intel_display_driver_{suspend, resume}() names Jani Nikula
2026-06-02 8:32 ` [CI 02/12] drm/xe/display: rename xe_display_pm_shutdown*() to xe_display_shutdown*() Jani Nikula
2026-06-02 8:32 ` [CI 03/12] drm/xe/display: relocate the xe_display_shutdown*() functions Jani Nikula
2026-06-02 8:32 ` [CI 04/12] drm/xe/display: relocate the xe_display_pm_runtime_*() functions Jani Nikula
2026-06-02 8:32 ` [CI 05/12] drm/{i915, xe}: move more calls inside intel_display_driver_pm_suspend() Jani Nikula
2026-06-02 8:32 ` [CI 06/12] drm/{i915, xe}: move more calls inside intel_display_driver_pm_resume() Jani Nikula
2026-06-02 8:32 ` [CI 07/12] drm/{i915, xe}: add intel_display_driver_pm_{suspend_late, resume_early}() Jani Nikula
2026-06-02 8:32 ` [CI 08/12] drm/{i915,xe}: add intel_display_driver_shutdown_late() Jani Nikula
2026-06-02 8:32 ` [CI 09/12] drm/i915: add intel_display_driver_shutdown() Jani Nikula
2026-06-02 8:32 ` [CI 10/12] drm/i915/display: deduplicate suspend and shutdown a bit Jani Nikula
2026-06-02 8:32 ` [CI 11/12] drm/xe/display: use intel_display_driver_pm_shutdown() Jani Nikula
2026-06-02 8:32 ` [CI 12/12] drm/{i915, xe}: move more stuff to __intel_display_driver_pm_suspend() Jani Nikula
2026-06-02 10:07 ` ✗ i915.CI.BAT: failure for drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification, part 2 Patchwork
2026-06-02 12:46 ` Jani Nikula
2026-06-03 13:29 ` Jani Nikula
2026-06-03 14:24 ` Imre Deak [this message]
2026-06-03 15:32 ` Jani Nikula
2026-06-03 9:08 ` ✓ i915.CI.BAT: success for drm/{i915, xe}: display (runtime) suspend/resume/shutdown unification, part 2 (rev2) Patchwork
2026-06-04 6:29 ` ✗ i915.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=aiA5ORKjPPJlwYcM@ideak-desk.lan \
--to=imre.deak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@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