From: "Iyán Méndez Veiga" <me@iyanmv.com>
To: stable@vger.kernel.org
Cc: regressions@lists.linux.dev, daniele.ceraolospurio@intel.com,
sashal@kernel.org
Subject: [REGRESSION] drm/xe/guc: Lenovo Thinkpad X1 Carbon Gen 12 can't boot with 6.16.9 and Xe driver
Date: Sat, 27 Sep 2025 00:58:10 +0200 [thread overview]
Message-ID: <616f634e-63d2-45cb-a4f9-b34973cc5dfd@iyanmv.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1045 bytes --]
Hello,
After upgrading to 6.16.9 this morning, my laptop can't boot. I cannot
get any logs because the kernel seems to freeze very early, even before
I'm asked for the full disk encryption passphrase.
This is a regression from 6.16.8 to 6.16.9.
I did a git bisect in the stable/linux and this is the commit causing
the issue for me:
97207a4fed5348ff5c5e71a7300db9b638640879 is the first bad commit
commit 97207a4fed5348ff5c5e71a7300db9b638640879 (HEAD)
Author: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Date: Wed Jun 25 13:54:06 2025 -0700
drm/xe/guc: Enable extended CAT error reporting
[ Upstream commit a7ffcea8631af91479cab10aa7fbfd0722f01d9a ]
https://lore.kernel.org/all/20250625205405.1653212-3-daniele.ceraolospurio@intel.com/
How to reproduce:
1. Upgrade to 6.16.9
2. Enable the Xe driver by passing i915.force_probe=!7d55
xe.force_probe=7d55
3. Reboot
Best regards,
Iyán
--
Iyán Méndez Veiga
GPG Key: 204C 461F BA8C 81D1 0327 E647 422E 3694 311E 5AC1
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-09-26 23:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 22:58 Iyán Méndez Veiga [this message]
2025-09-27 12:52 ` [REGRESSION] drm/xe/guc: Lenovo Thinkpad X1 Carbon Gen 12 can't boot with 6.16.9 and Xe driver Thorsten Leemhuis
2025-09-27 14:19 ` Iyán Méndez Veiga
2025-09-27 14:31 ` Thorsten Leemhuis
2025-09-28 11:16 ` Iyán Méndez Veiga
2025-09-28 15:40 ` Sasha Levin
2025-09-30 9:04 ` Daniele Ceraolo Spurio
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=616f634e-63d2-45cb-a4f9-b34973cc5dfd@iyanmv.com \
--to=me@iyanmv.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=regressions@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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