From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Jakub Prussak" <Jakub.Prussak@synaptics.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: PPD-Penguins <ppdpenguins@synaptics.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Dave Airlie <airlied@redhat.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: Cache coherency issues when reading from intel Xe buffer.
Date: Fri, 14 Nov 2025 12:30:54 +0200 [thread overview]
Message-ID: <8e0c8db54085ad6543f917be310ca557a3180680@intel.com> (raw)
In-Reply-To: <PH0PR03MB6299A7D48D2DD771B06E8882E9CAA@PH0PR03MB6299.namprd03.prod.outlook.com>
On Fri, 14 Nov 2025, Jakub Prussak <Jakub.Prussak@synaptics.com> wrote:
> Once the xe driver was forced the laptop screen stopped working, but the corruptions on the EVDI display stopped appearing. In lspci output there is no driver in use for VGA device. I attached lspci and dmesg output, let me know if anything else is required.
>
Might want to get this fixed before any further debugging, i.e. update
to a newer linux-firmware package.
[ 6.255871] xe 0000:00:02.0: [drm] *ERROR* Tile0: GT0: Unsupported GuC v70.20.0! v70.29.2 or newer is required
This is also getting a bit involved and noisy to debug on the mailing
list, with dmesg attachments and all. Lore is rejecting the messages and
they're not getting archived. I suggest filing a bug over at fdo gitlab
[1] and continuing there.
BR,
Jani.
[1] https://drm.pages.freedesktop.org/intel-docs/how-to-file-i915-bugs.html
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-11-14 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH0PR03MB6299572C46068849DBDD3A88E9C2A@PH0PR03MB6299.namprd03.prod.outlook.com>
2025-11-10 16:48 ` Cache coherency issues when reading from intel Xe buffer Jani Nikula
2025-11-13 12:31 ` Jakub Prussak
2025-11-13 17:20 ` Thomas Hellström
2025-11-14 9:36 ` Jakub Prussak
2025-11-14 10:30 ` Jani Nikula [this message]
2025-11-14 12:11 ` Tvrtko Ursulin
2025-11-21 11:08 ` Jakub Prussak
2025-12-05 13:38 ` Jakub Prussak
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=8e0c8db54085ad6543f917be310ca557a3180680@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=Jakub.Prussak@synaptics.com \
--cc=airlied@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=ppdpenguins@synaptics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox