From: Jani Nikula <jani.nikula@linux.intel.com>
To: reconicreferenssse <reconicpreferensse@proton.me>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: Kernel panic in xe_display_flush_cleanup_work (NULL pointer dereference Alder Lake + Arc A370M)
Date: Fri, 15 May 2026 19:20:15 +0300 [thread overview]
Message-ID: <7976babe35c874c4e17a6326a2a1a036049d81dd@intel.com> (raw)
In-Reply-To: <4f9f30384c24683925e88d266b943d2102c442e3@intel.com>
On Fri, 15 May 2026, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> On Wed, 13 May 2026, reconicreferenssse <reconicpreferensse@proton.me> wrote:
>> I am reporting a fatal NULL pointer dereference (address:
>> 00000000000005d8) in the 'xe' driver. This is a critical boot-blocker
>> on hybrid Alder Lake-P + DG2 platforms, causing a Kernel Panic during
>> early KMS initialization (initramfs) before the LUKS password prompt.
>
> ...
>
>> Steps to Reproduce:
>> 1. Boot with: xe.force_probe=46a6,5693 i915.force_probe=!46a6,!5693
>
> The xe driver does not properly support ADL-P or DG2. As you know, since
> you're forcing the probe, and it taints the kernel.
>
> We might have a look if this is generic and unrelated to the platform,
> but otherwise you should use the i915 driver with ADL-P and DG2.
Yeah, I think this one's unrelated to the platform. See [1].
Reporting the i915 specific issues you mentioned would still be
appreciated.
And for anyone else wondering, the mentioned but unreferenced gitlab
issue is likely [2].
BR,
Jani.
[1] https://lore.kernel.org/r/20260515160920.1082842-1-jani.nikula@intel.com
[2] https://gitlab.freedesktop.org/drm/xe/kernel/-/work_items/7904
--
Jani Nikula, Intel
prev parent reply other threads:[~2026-05-15 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 21:35 Kernel panic in xe_display_flush_cleanup_work (NULL pointer dereference Alder Lake + Arc A370M) reconicreferenssse
2026-05-14 14:32 ` Rodrigo Vivi
2026-05-15 8:31 ` Jani Nikula
2026-05-15 16:20 ` Jani Nikula [this message]
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=7976babe35c874c4e17a6326a2a1a036049d81dd@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=reconicpreferensse@proton.me \
--cc=rodrigo.vivi@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.