All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Tvrtko Ursulin <tursulin@ursulin.net>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: ✗ Fi.CI.IGT: failure for drm/edid & drm/i915: vendor and product id logging improvements (rev3)
Date: Fri, 12 Apr 2024 11:06:09 +0300	[thread overview]
Message-ID: <87sezr3szy.fsf@intel.com> (raw)
In-Reply-To: <171286159857.1341683.3160591903841939436@8e613ede5ea5>

On Thu, 11 Apr 2024, Patchwork <patchwork@emeril.freedesktop.org> wrote:
> == Series Details ==
>
> Series: drm/edid & drm/i915: vendor and product id logging improvements (rev3)
> URL   : https://patchwork.freedesktop.org/series/131414/
> State : failure

[snip]

> #### Possible regressions ####
>
>   * igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions:
>     - shard-dg1:          NOTRUN -> [INCOMPLETE][1]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_131414v3/shard-dg1-17/igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions.html
>
>   * igt@kms_plane@pixel-format@pipe-a:
>     - shard-tglu:         [PASS][2] -> [INCOMPLETE][3]
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14552/shard-tglu-8/igt@kms_plane@pixel-format@pipe-a.html
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_131414v3/shard-tglu-3/igt@kms_plane@pixel-format@pipe-a.html
>     - shard-mtlp:         [PASS][4] -> [ABORT][5]
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14552/shard-mtlp-1/igt@kms_plane@pixel-format@pipe-a.html
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_131414v3/shard-mtlp-3/igt@kms_plane@pixel-format@pipe-a.html

I don't see how this could be an issue with this patch, but it looks
serious:

<7> [451.620816] [drm:eb_lookup_vmas [i915]] EINVAL at eb_validate_vma:510
<4> [451.624224] ------------[ cut here ]------------
<4> [451.624309] list_del corruption. prev->next should be ffff88810afbf3d0, but was ffff88810afbb410. (prev=ffff88810afbb410)
<4> [451.624332] WARNING: CPU: 1 PID: 1374 at lib/list_debug.c:62 __list_del_entry_valid_or_report+0xb7/0xe0

etc.

BR,
Jani.

>
>   * igt@kms_sequence@queue-busy@pipe-c-hdmi-a-2:
>     - shard-glk:          [PASS][6] -> [INCOMPLETE][7]
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_14552/shard-glk5/igt@kms_sequence@queue-busy@pipe-c-hdmi-a-2.html
>    [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_131414v3/shard-glk4/igt@kms_sequence@queue-busy@pipe-c-hdmi-a-2.html

-- 
Jani Nikula, Intel

  reply	other threads:[~2024-04-12  8:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09  9:46 [PATCH v2 0/4] drm/edid & drm/i915: vendor and product id logging improvements Jani Nikula
2024-04-09  9:46 ` [PATCH v2 1/4] drm/edid: add drm_edid_get_product_id() Jani Nikula
2024-04-09  9:46 ` [PATCH v2 2/4] drm/edid: add drm_edid_print_product_id() Jani Nikula
2024-04-09  9:46 ` [PATCH v2 3/4] drm/i915/bios: switch to struct drm_edid and struct drm_edid_product_id Jani Nikula
2024-04-09 15:40   ` Ville Syrjälä
2024-04-15 12:54     ` Jani Nikula
2024-04-09  9:46 ` [PATCH v2 4/4] drm/i915/bios: return drm_edid_product_id from get_lvds_pnp_id() Jani Nikula
2024-04-09 14:16 ` ✗ Fi.CI.SPARSE: warning for drm/edid & drm/i915: vendor and product id logging improvements (rev2) Patchwork
2024-04-09 14:28 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-10  7:42 ` ✗ Fi.CI.SPARSE: warning for drm/edid & drm/i915: vendor and product id logging improvements (rev3) Patchwork
2024-04-10  8:01 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-04-10 10:08   ` Jani Nikula
2024-04-11  7:59     ` Illipilli, TejasreeX
2024-04-11  7:58 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-11 18:53 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-12  8:06   ` Jani Nikula [this message]
2024-04-16  1:13     ` Rodrigo Vivi

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=87sezr3szy.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=tursulin@ursulin.net \
    /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.