All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Szymon Acedański" <accek@invisiblethingslab.com>
To: intel-xe@lists.freedesktop.org
Cc: I915-ci-infra@lists.freedesktop.org,
	thomas.hellstrom@linux.intel.com, matthew.brost@intel.com,
	rodrigo.vivi@intel.com
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV (rev3)
Date: Mon, 21 Sep 2026 12:07:27 +0200	[thread overview]
Message-ID: <20260921100728.72370-1-accek@invisiblethingslab.com> (raw)
In-Reply-To: <178998407678.185576.6713809856683852020@61270ab9df2a>

This one also cannot have been caused by this series
(xe-pw-172525v3):

 * This patch cannot affect CI machines, because the only functional
   change is gated behind xen_pv_domain()

The reported issues seem to be tracked here:

 * XE#9331 (https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/9331)
   for DMESG-WARNs
 * XE#7096 (https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/7096)
   for igt@xe_module_load@force-load FAIL and the resulting 304 SKIPs

Could the bug team please document this too? KUnit is green.

Thanks,
Szymon

  reply	other threads:[~2026-09-21 12:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-16 17:30 [PATCH v2] drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV Szymon Acedański
2026-09-17 12:16 ` ✗ LGCI.VerificationFailed: failure for drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV (rev2) Patchwork
2026-09-21  6:34 ` ✓ CI.KUnit: success for drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV (rev3) Patchwork
2026-09-21  7:49 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-09-21  9:30   ` Szymon Acedański
2026-09-21  9:47 ` ✗ Xe.CI.FULL: " Patchwork
2026-09-21 10:07   ` Szymon Acedański [this message]
2026-09-21 13:57 ` [PATCH v2] drm/xe: Limit sg segment size to PAGE_SIZE on Xen PV Thomas Hellström
2026-09-21 14:30   ` Thomas Hellström

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=20260921100728.72370-1-accek@invisiblethingslab.com \
    --to=accek@invisiblethingslab.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.brost@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@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.