Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: xen-devel <xen-devel@lists.xenproject.org>
Cc: intel-xe@lists.freedesktop.org
Subject: Graphical glitches (not refreshing?) with Linux's xe driver + Xen 4.19
Date: Tue, 10 Feb 2026 19:06:20 +0100	[thread overview]
Message-ID: <aYtznP_tT6xNPwf-@mail-itl> (raw)

[-- Attachment #1: Type: text/plain, Size: 2397 bytes --]

Hi,

Recently I started testing compatibility with Intel Lunar Lake. This is
the first one that uses "xe" instead of "i915" Linux driver for iGPU.
I test it with Qubes OS 4.3, which uses Xen 4.19.4 and PV dom0 running
Linux 6.17.9 in this test.
The result is rather sad:
https://openqa.qubes-os.org/tests/166691#step/simple_gui_apps/30
or
https://openqa.qubes-os.org/tests/166700#step/desktop_linux_manager_config/42

The black windows are mapped from a domU (using grant tables). But if
you watch the video (in the "logs&assets" tab), login window of dom0 is
affected too (background is rendered significantly later than its text
and widgets). 

I didn't found any relevant errors in kernel (or Xen) messages. Just in
case, full dumps:
https://openqa.qubes-os.org/tests/166700/file/desktop_linux_manager_config-journalctl.log
https://openqa.qubes-os.org/tests/166700/file/desktop_linux_manager_config-xl-dmesg.log

Some user reported similar issue with Intel Arc Pro B50, which also uses
"xe" driver:
https://github.com/QubesOS/qubes-issues/issues/10661

I tested also Linux 6.19-rc8, no improvements.

My previous tests of the xe driver on older systems (Meteor Lake, Raptor
Lake) resulted in similar behavior, while i915 works fine there. But there
I needed to use force_probe parameter, and blamed the issue on xe not
officially supporting those platforms. I wanted to compare with i915 on
LNL, but i915 doesn't support that model at all (and if I force it, I
get kernel panic in i915_pci_probe...).

Interestingly, it appears to work just fine on Qubes OS 4.2 (Xen 4.17.6,
same Linux dom0 version). I did not tested with Xen 4.21.

In both cases, our Xen has the patch to use Linux's PAT layout applied.
That's a workaround for
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/7648, which is
fixed now, but apparently similar bug is still present in a few other
drivers (including binary nvidia one...).

The same Linux kernel started without Xen works just fine.

Any ideas?

Having good and a bad version, I can try to bisect this one, but given
it requires rebuilding Xen toolstack each time too (due to bisection
across releases), I'd rather avoid it if possible...

I'm CC-ing also intel-xe list, maybe somebody there have some ideas how
to debug this. 

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2026-02-10 18:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 18:06 Marek Marczykowski-Górecki [this message]
2026-02-12 14:33 ` Graphical glitches (not refreshing?) with Linux's xe driver + Xen 4.19 Rodrigo Vivi
2026-02-12 15:11 ` Roger Pau Monné
2026-02-12 15:32   ` Marek Marczykowski-Górecki
2026-02-12 16:16     ` Roger Pau Monné
2026-02-12 16:22       ` Marek Marczykowski-Górecki
2026-02-12 16:35         ` Roger Pau Monné
2026-02-13  1:23   ` Marek Marczykowski-Górecki
     [not found]     ` <a41a15ca-b26e-482a-9084-fc61645fb24e@gmail.com>
2026-02-24 15:31       ` Marek Marczykowski-Górecki
2026-02-24 15:58     ` Marek Marczykowski-Górecki
2026-03-02 11:19       ` Marek Marczykowski-Górecki

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=aYtznP_tT6xNPwf-@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=xen-devel@lists.xenproject.org \
    /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